Default configuration behavior preferences

• Use default configuration: Check to use default input and output tasks when you create a new process. If this group is not selected, each new process you will add will begin and end with unknown tasks.

  • Default input task: Select an input task to use as the default input task when you add a new process. Click the Configure button located to the right of this box to set the properties of the selected input task.

  • Default output task: Select an output task to use as the default output task when you add a new process. Click the Configure button located to the right of this box to set the properties of the selected output task.

  • Default output task for conditions/branches: Select an output task to use as the default output task when you add a new branch or condition. Click the Configure button located to the right of this box to set the properties of the selected output task.

• Open the current configuration on startup: When this option is selected the Workflow Configuration tool automatically starts with the configuration that was last sent to the server. Otherwise no configuration will be opened at the start.

• Enable Undo/Redo functionality: Select this option to enable or disable the Undo functionality. Disabling the Undo/Redo functionality frees up a lot of memory and may thus speed up your system. The maximum number of steps performed is set in the box below.

• Auto Save every: Select to enable the Auto Save functionality. The auto save delay is set in the box below (in minutes).

• Enable printer information validation when opening a Watch configuration file: If one of the processes in the configuration file contains a Print using a Windows printer driver plugin, the printer information (printer name, driver size and version) will be checked and the update process will be performed as required.

• Default scripting language: Specify which scripting language the Run Script plugin expects by default. This preference is saved in the registry, not in a configuration file.

  Note:

  • The JScript engine is Microsoft’s JScript 5.8, which is the equivalent of JavaScript 1.5 (ECMA-262 3rd edition + ECMA-327 (ES-CP) + JSON).

    Enhanced JScript allows the use of more recent JavaScript syntax. Many methods - basic methods like Date.now(), String.trim(), btoa()/atob() and more advanced methods like Array.forEach() - are added to the JScript engine via the polyfill.js library.

    Object methods (such as valueOf and toString) cannot be used in a JSON string in Workflow scripts. This is due to Microsoft’s implementation of the JScript library used in Workflow.

  • While JavaScript and VBScript are natively available on Windows operating systems, Python and Perl require third-party tools to be functional.
    For Perl, ActivePerl can be installed and for Python ActivePython can be installed.3.
    These links are provided for convenience only, and Upland Objectif Lune does not offer support for their use.

  • To work with Python in Workflow, the Python engine needs to be installed and registered. For instructions see Installing the Python engine.