There are two versions of the script editor: (1) the full script editor that is the default for scripts created as a project component and (2) the inline script editor that is present in transformations, which can be expanded to the full script editor by clicking the popout icon in the upper right of a script.
The full script editor contains all options covered on this page, while the inline editor offers a pared down version for quick editing.
For more information on types of scripts, see Script Types and Creation.
The full script editor is the default script editor for scripts created as a project component:
To access the full script editor from within the inline version present within transformations, click the popout icon in the upper right of the script:
The full script editor interface will open:
By default, a new script is named "New Script," with a number appended if there are additional scripts with the same name. The script name must be unique for each script within the project, regardless of the scripting language used, and must not contain forward slashes (
/) or colons (
To rename a script from the design canvas, click the name below the script block to bring the name into edit mode, then enter a name:
To rename a script from within the script editor, click into the Script Name text box along the top left and enter a name:
You can add custom notes to a script that serve as documentation or reminders for yourself or project collaborators. To add a note, click the note icon next to the script name:
An editable area will open where you can enter the text of your note. Then click Post to add the note on the script:
Your posted note will be displayed, along with your name and a timestamp. Anyone with edit access to the script can remove notes by clicking the remove icon . To close the note, simply click on another part of the interface.
When one or more notes are present, the note icon color is displayed in orange:
Additional notes can be added using the same method described above.
Upon making changes to a script, the script configuration saves automatically. To manually save the script, press
Command+S on Mac).
The save status is displayed along the top of the script below the script name:
To learn more about auto-save, see Project Permissions, Collaboration, and Saving.
Scripts created within a transformation, either on a target field or on a node, are limited to Jitterbit Script language.
Scripts are opened in edit mode by default. To open the script in test mode, use the toggle in the top right to select Test:
For further details, see Script Testing.
To exit the script and return to the previous screen, click the close icon in the top right.
In Jitterbit Script, scripts must be enclosed within a
<trans> opening tag and
</trans> closing tag, unless using functions that specifically call for code to be placed outside of these tags, such as several Database Functions.
These are the main features of the script area:
Auto-validation: Harmony provides basic syntax checking and highlighting of lines with errors. If the script passes basic syntax validation, a line below the script area will read: "Script is valid." If the script does not pass basic syntax validation, specific error information will be provided here one line at a time. That is, after resolving an error on one line, additional syntax errors to resolve may be reported for subsequent lines.
Auto-completion: As you type, you can display autocomplete suggestions that begin with the entered string by using
Control+Space. When only one suggestion is available, it will be inserted automatically. When more than one suggestion is available, you can navigate through the list using the keyboard arrow keys and press
Tab to insert the suggestion into the script area.
Tabindents the selected lines one tab stop to the right. Similarly,
Shift+Tabmoves out the selected lines one tab-stop to the left. If no text is selected,
Shift+Tabmoves the line left to where the cursor is.
In addition, standard browser features for undo, controlling font size, and searching within the script may be used.
CAUTION: If a script calls other project components that have not yet been deployed, those components must be deployed before you can run the script successfully. This is true even if those components are not added to any operations (that is, if they appear only within the Components tab of the project pane).
Source Objects: This tab is present only for Jitterbit Scripts created within a transformation. Within the script, you can reference source data by the path of the field.
Add a source object to the Jitterbit Script using one of these methods:
For an explanation of the node/field notation, refer to Nodes and Fields.
Functions: This tab provides a list of functions, in the appropriate language, available to use in a script.
For additional documentation, see Functions.
For additional documentation, see Variables.
Plugins: This tab provides a list of plugins that can be run inside the script.
Add a plugin to the Jitterbit Script using one of these methods:
Operations: This tab provides a list of operations from the project that are available to use in the script.
Add an operation to the Jitterbit Script using one of these methods:
For additional documentation, see Operations.
Notifications: This tab provides a list of notifications from the project that are available to use in the script.
Add a notification to the Jitterbit Script using one of these methods:
For additional documentation, see Notifications.
Add another script within the Jitterbit Script using one of these methods:
For additional documentation, see Scripts.
Endpoints: This tab provides a list of endpoints from the project that are available to use in the script.
Depending on the endpoint, you may then use the Functions tab to add functions for which to use the connection or activity reference as the argument. For additional documentation, see Connectors.