Page History

Module

Configuration 

Image AddedConfiguration UI

→ Solution / Alarms / Items - tags and conditions to generate alarm. Include AlarmGroup for Ack/Log settings and AlarmArea for hierarchy.

→ Solution / Alarms / Groups - Collection of AlarmItems sharing properties such as AckRequired and LogEvents.

→ Solution / Alarms / Areas - Hierarchical grouping of AlarmGroups for better organization.

→ Solution / Alarms / Audit Trail - Logs events on Operation actions, and on selected system events.

Key Concepts and Terms

The Scripts Module manages and executes user-defined scripts for automation and process control. 

ScriptTask

Defines code that executes in reaction to an event (trigger) or periodically at specified intervals.

ScriptClass

A library of functions and methods that can be used in Script Tasks, Expressions, or from the Code Behind on graphical Displays.

ScriptExpression

One line of code in response to an event, when the entire script isn't necessary.

Script References

External DLLs included for a script or display code compilation.

Understanding the Scripts Module

Module Highlights

• Built-in Code Editor: Our code editor supports C#, VB.NET, JavaScript, and Python languages.

• Server and Client Domains: Create scripts that execute on the server for global reach or on the client side for local reach.

• Events and Scheduling: Tasks and expressions can be triggered by date, time, condition, calendar, tag change, or interval. Execution is distributed among processes, each running in its own application domain, isolated from the real-time database, ensuring maximum system security and performance.

• Object Orientation and Solution Object: All solution objects, including tags, datasets, alarms, devices, and communication statuses, are immediately accessible via IntelliSense as native .NET objects. No temporary tags or function calls are required. With a single command, move data from tags to .NET objects and external data tables.

• Configure Your Python Interpreter: The Scripts Module delivers exceptional scripting capabilities across various programming languages with seamless integration of Python. You can configure any version of the Python interpreter for each project.

Configuration Workflow

Working with the Scripts Module

Runtime Execution

The key concept to be aware of regarding the execution of the tasks and expressions defined in the Script Module is that they execute on the server computer.

Only the CodeBehind of the displays is executed on each client computer. The script classes can be consumed by both server and client stations.

Current solutions are prioritizing user interfaces that are portable, meaning the exact same drawing and display configuration can run as a WPF Windows Rich Client or as a web HTML5 page inside a browser. If you intend to run the graphical interface only on WPF Windows and not on web pages, it is possible to enable this in Solution / Settings to allow tasks and expressions to run on the client side.

For complex solutions or very large solutions, it's useful to get a deeper understanding of the Module execution process. Read more at Module Script ExecutionEngine (Reference) if that is your case.

Script

Namesace

The Namespace Script is the entry point for all objects related to the Scripts module.

The Script.Class object lists all configured tables and its runtime properties. The Script.Task object lists all configured database connections and their runtime properties.

Examples:

→ Read more about Objects and Namespaces.

Anchor
BestPractices BestPractices

Troubleshooting

Best Practices and Recommendations

• Code Formatting:  Use the 'Format' feature of the editor for more readability.
• Naming Convention: Use a coherent and descriptive naming convention for tasks.
• Task Domain: Select the appropriate domain for each task, considering whether the task is more suitable for client-side or server-side execution. Remember, Client-Side Tasks only applicable to RichClients
• Reusable Code: Use reusable code by creating classes that encapsulate functionalities for use in various parts of the project.
• Library Management: Manage libraries and external components effectively to avoid conflicts and compatibility issues.
• Code Consistency: Maintain code consistency by following best practices and coding conventions.
• Build Before Deployment: Always perform a build operation before deploying a project in a production environment to ensure all scripts are correct and up to date.

Troubleshooting and Common Issues

The Scripts module may encounter some issues in its operation. Here are some common issues and their troubleshooting:

• Build Errors and Warnings: Make sure to check the 'BuildStatus' and 'BuildErrors' tabs to identify and address errors and warnings that arise during the build.
• Code Language: If you change the code language in the code editor, confirm that the code has been correctly converted to the selected language.
• Build Order: Ensure that the build order of the classes is set up correctly to avoid circular dependencies or initialization issues.
• Domain Selection: Ensure that the domain is selected correctly (Client or Server) based on the needs of your project.
• Reference Issues: Make sure that all external references are configured correctly and that there are no compatibility issues or conflicts in the Code Editor.
• Code Formatting:  Use the 'Format' feature of the editor for more readability.
• Incremental Compilation Issues: Monitor the incremental compilation process to identify and resolve potential issues that may arise.
• Debugger Setup: Ensure that the debugger setup is correct to allow effective code debugging.
• Breakpoints and Watch Variables: Use breakpoints and watch variables effectively to identify and resolve issues.

In this section: