Use of Local Actions
Actions are used for picture-independent background tasks, such as printing daily reports,
monitoring
tags or performing calculations. An action is started by the trigger configured for it.
In order for an action to be executed, Global Script Runtime must be included in the startup
list.
In contrast to global actions, local actions can be assigned to a single computer. It is thus for
example possible to ensure that a report is only printed on the server.
See also
How to Protect an Action Against Unauthorized Access (Page 809)
Triggers (Page 811)
How To Create and Edit Actions (Page 802)
How to Add Global Script Runtime to a Project's Startup List (Page 771)
2.7 Characteristics of Global Actions
Characteristics of Global Actions
Global actions ...
● can be created by yourself
● can be edited by you
● can be password-protected against modification and viewing by unauthorized persons
● have at least one trigger to start them
● are executed on all project computers in a client-server project
● are assigned file name extension "*.pas"
Global Actions are saved in the "\Pas" subdirectory of the WinCC project.
Use of Global Actions
Actions are used for background tasks, such as printing daily reports, monitoring tags or
performing calculations. An action is started by the trigger configured for it. In order for an
action to be executed, Global Script Runtime must be included in the startup list.
ANSI-C for Creating Functions and Actions
2.7 Characteristics of Global Actions
MDM - WinCC: Scripting (VBS, ANSI-C, VBA)
770
System Manual, 11/2008,