Defining the business logic and creating 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
Script Variables). Figure 3.
