Define the business logic and create a user interface.

Script Language Support

Automation scripts are tied to the application it customizes. Therefore, the extent of customization depends on the customized application and availability of its API layer per version. By tying the script to the application Pulse has access to the language interpreter that comes with the application. Pulse supports multiple programming languages. Scripting languages can be registered separately as well (see Applications).

Figure 1.
Before Pulse executes the task, it validates if the application version tied to the script is acceptable.

Figure 2.

Pulse supports a low code approach letting the author reduce the code in a script to contain purely the business logic (the automation itself), leaving creating the user interface, order of execution and version compatibility checks to Pulse.

In case a task requires user input, Pulse provides a capability to describe the UI instead of coding it. Dialogs are created during runtime from a description in the task itself – User Properties. The author defines the variables and synchronizes the data names between the task and the script (see Variables and Dataflow).

Script Editor

Scripts can be edited directly using the Pulse Script Editor dialog which is accessible through the context menu on the tasks and script property fields.
Note: When updating a script, remember to save and export the task to the library if the changes are to be saved and reused for future.

Figure 3.
To open the Pulse Script Editor dialog, complete one of the following options:
  • In the Block Diagram, right-click a task and select Edit Script from the context menu.

    Figure 4.
  • In the Study browser, right-click the Script name value and select Edit Script from the context menu.

    Figure 5.
The Pulse Script Editor dialog is set as default, but it is possible to use a custom script editor. In the Generic tab of the Preferences dialog, select the executable of the script editor of choice.

Figure 6.

Import Pulse Libraries

In the Pulse Script Editor dialog, right-click and select Import Pulse Libraries from the context menu to add Pulse Libraries to the top of the script. These libraries are required to use the Pulse process APIs to control and query data from the Pulse Session.

Figure 7.