Device Monitoring Studio's scripting module exposes programming interfaces for a number of application internal objects. The current implementation exposes interfaces for the following objects:
Various API functions and events have been updated to use typed arrays.
Better performance
Scripting system has increased performance.
Scripting support in version 7.13 has changed significantly. This section lists all changes and also marks breaking changes:
Scripting language support (breaking change)
Only JavaScript is supported. Support for other scripting languages (like VBScript) has been discontinued.
Naming convention (breaking change)
New method naming scheme: camelCase.
New event system (breaking change)
Device Monitoring Studio does not use Automation-compatible event system anymore. Instead, user script may directly bind JavaScript functions as event handlers. This simplifies event binding and consuming.
Simplification of many methods (breaking change)
Many MODBUS and Serial Terminal methods were simplified. For example, methods that took a variable number of arguments now receive a single JavaScript array argument.
Updated Scripting Site object (breaking change)
Several methods of Scripting Site object have been updated and a few new ones added.
New built-in object: Monitoring
New monitoring object provides methods to create, configure and manage monitoring sessions.
(Optional) support for TypeScript
User scripts may now be written in TypeScript (superset of JavaScript) for better syntax and strong type-checking. If supported by user operating system, user scripts are always checked against a TypeScript interface definition providing better error reporting and syntax checking. TypeScript compiles to plain JavaScript which is then executed.
Scripting in User Interface
Scripting Tool Window has been removed in Device Monitoring Studio 7.13. Now user scripts are opened in their own client windows inside application frame.