The Script Editor and XSLT Editor

The Script Editor is used to edit scripts in Run Script tasks and the XSLT Editor is used to edit scripts in Open XSLT action tasks. You can open either editor using the Open Editor button from the task's Properties dialog. When you do so, the script currently displayed in the dialog box is pasted to the editor’s scripting box.

Both editors are visually identical and share almost exactly the same commands. They let you import and export scripts, perform common editing, such as search and replace, and feature syntax highlighting and formatting.

You can use the Script Editor to edit scripts written in VBScript, JavaScript (JScript, Enhanced JScript), Perl, and Python.
You can use the XSLT Editor to edit scripts written in XSLT 1.0 and 2.0.

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.

For information on the available editor options, refer to Editor Options.