Navigate the transformation interface in Jitterbit Integration Studio

• View all mapping lines: Shows or hides the lines that connect source fields to target fields. When you hover over or select fields, the mapping lines still appear and work the same way. This setting controls only whether all mapping lines are always visible.
• View mapped source fields: Shows or hides mapped source object names in the target field.
• View node lines: Shows or hides the vertical lines that display the structure of source and target schemas. These lines help you see the relationship between parent and child elements.
• View cardinality: Shows or hides the cardinality keys next to field names that indicate field requirements. Cardinality is hidden by default.
• View field type: Shows or hides the data type for each field. Data types appear next to field names and indicate what kind of data the field contains.

This option is available only when the transformation has both a source schema and target schema specified.

Remove loop node removes the loop node definition. This action is available only on nodes that have a manually defined loop node.

Remove loop node and mappings removes the loop node definition due to mappings that are direct leaf children associated with the loop node, and removes those mappings.

Any other mappings within child loop nodes beneath the parent loop node are preserved, and the node retains its loop node definition if at least one grandchild is mapped.

This action is available only on nodes that have a loop node defined (either manually or by automatic generation).

Remove all mappings beneath this node removes all mappings on fields contained within the node, as well as all mappings on fields contained within child nodes of that node.

Using this action on a root node removes all mappings in a transformation. On selecting this action, a message asks you to confirm that you want to remove mappings.

Remove all invalid mappings removes all invalid mappings on fields contained within the node, as well as all invalid mappings on fields contained within child nodes of that node.

For more information about invalid mappings, see Transformation mapping validity.

Expand all nodes beneath this node expands all child nodes beneath the parent node.

(By default, nodes are expanded up to 8 levels deep for schemas with 750 or fewer nodes and up to 5 levels deep for schemas with more than 750 nodes.)

Duplicate node duplicates the node and its fields, as well as any child nodes and their fields. Mappings are not duplicated.

This action is available on root nodes in flat schemas and on nodes whose cardinality indicates that elements can occur more than once. The node must not already be a duplicate of another node.

For display purposes at design time only, the name of the duplicate node is appended with a hash (#) and an incremented number. For example, when you duplicate a node named transaction, the first duplicate of the node is displayed as transaction#1. If you then duplicate the transaction node again, the second duplicate is displayed as transaction#2. During runtime, the original node name is used for both the original node and duplicate nodes. For example, the nodes displayed as transaction, transaction#1, and transaction#2 are each processed with the original node name transaction. Duplicate nodes cannot be renamed.

Whether a duplicate node is reflected in other locations throughout the project depends on how the schema was defined:

• Defined in an Activity: If the schema in which the node is duplicated is defined in an activity, then the duplicate node is reflected in the activity's schema. If the activity's schema later undergoes any changes as a result of a changed activity configuration or a schema refresh from the endpoint, the retention of duplicate nodes depends on if the original node that was duplicated still exists:
  • If the original node exists, any previously duplicated nodes are retained.
  • If the original node no longer exists, all nodes created as duplicates of that node are removed.
• Defined in a Transformation: If the schema in which the node is duplicated is defined in a transformation, then the duplicate node is not reflected in the activity's schema, as the activity's schema is not part of the transformation.

Remove duplicated node removes the duplicate node and its fields, as well as any duplicate child nodes and their fields.

This action is available only on nodes that were created using Duplicate node.

Rename duplicated node enables you to rename a duplicated target node. The new name is for display purposes during design time only. At runtime, the original duplicated node name (the node name appended with a hash (#) and an incremented number) is used.

This action is available only on nodes that were created using Duplicate node.

Add condition to node is used to conditionally apply a mapping to the fields contained within a node.

This action is available only on nodes that do not already have a condition applied.

On selecting this action, an editable script area opens for you to create the condition. For details about creating the condition, see Conditional logic.

Edit condition opens an editable script area

This action is available only on nodes that already have a condition applied. For more details, see Conditional logic.

Remove condition removes the condition.

This action is available only on nodes that already have a condition applied.

For activities with user-defined schemas, you can edit the configuration to clear or swap out the file you selected to use for the schema. For other activities, you can edit the query, change the object selection, or other such configuration.

When you edit a schema that was created from a sample file in a transformation, the configuration screen for a custom flat schema or custom hierarchical schema opens for you to add or edit fields and/or nodes as required. Schemas provided by an adjacent activity are not editable.

On opening a schema that is referenced by multiple components, a dialog displays a list of any components that reference the schema and will be affected by any changes:

This action also regenerates the schema in other locations throughout the project where the same schema is referenced, such as in an adjacent activity. For more information, see Schema regeneration.

• Source Schema: Removal of a source schema may result in invalid mappings. For more information, see Transformation mapping validity.
• Target Schema: Removal of a target schema removes all mappings.

Within a transformation script, you can reference source data by inserting a field's reference path, or you can reference source data nodes by inserting a node's reference path.

To add a field or node reference path to a transformation script (Jitterbit Script only), use one of these methods:

• Drag the object from the palette to the script to insert the object's reference path.
• Double-click the object in the palette to insert the object's reference path at your cursor's location within the script.
• Manually enter the reference path to the source object.

To add the function syntax to a script (Jitterbit Script or JavaScript), use one of these methods:

• Drag the function from the palette to the script to insert the function syntax.
• Double-click the function in the palette to insert the function syntax at your cursor's location within the script. On inserting the function syntax, the first function argument becomes highlighted and your cursor is moved to the end of the argument.
• Begin typing the function name and then press Control+Space to display a list of autocomplete suggestions. Select a function to insert the function syntax.
• Manually enter the function syntax.

To add the variable syntax to a script (Jitterbit Script or JavaScript), use one of these methods:

• Drag the variable from the palette to the script to insert the variable syntax.
• Double-click the variable in the palette to insert the variable syntax at your cursor's location within the script.
• Begin typing the variable name and then press Control+Space to display a list of autocomplete suggestions. Select a variable to insert the variable syntax.
• Manually enter the variable syntax.

To add a plugin reference path to a script (Jitterbit Script only), use one of these methods:

• Drag the plugin from the palette to the script to insert both the RunPlugin function and the plugin reference.
• Double-click the plugin in the palette to insert the plugin reference at your cursor's location within the script.
• Begin typing the plugin name and then press Control+Space to display a list of autocomplete suggestions. Select a plugin to insert the plugin reference.
• Manually enter the plugin reference.

To add an operation reference path to a script (Jitterbit Script only), use one of these methods:

• Drag the operation from the palette to the script to insert both the RunOperation function and the operation reference.
• Double-click the operation in the palette to insert the operation reference at your cursor's location within the script.
• Begin typing the operation name and then press Control+Space to display a list of autocomplete suggestions. Select an operation to insert the operation reference.
• Manually enter the operation reference.

To add a notification reference path to a script (Jitterbit Script only), use one of these methods:

• Drag the notification from the palette to the script to insert both the SendEmailMessage function and the notification reference.
• Double-click the notification in the palette to insert the notification reference at your cursor's location within the script.
• Begin typing the notification name and then press Control+Space to display a list of autocomplete suggestions. Select a notification to insert the notification reference.
• Manually enter the notification reference.

To add a script reference path to a script (Jitterbit Script only), use one of these methods:

• Drag the script from the palette to the script to insert both the RunScript function and the script reference.
• Double-click the script in the palette to insert the script reference at your cursor's location within the script.
• Begin typing the script name and then press Control+Space to display a list of autocomplete suggestions. Select a script to insert the script reference.
• Manually enter the script reference.

To add a connection or activity reference path to a script (Jitterbit Script or JavaScript), use one of these methods:

• Drag the connection or activity from the palette to the script to insert the appropriate reference.
• Double-click the connection or activity in the palette to insert the appropriate reference at your cursor's location within the script.
• Begin typing the connection or activity name and then press Control+Space to display a list of autocomplete suggestions. Select a connection or activity to insert the appropriate reference.
• Manually enter the connection or activity reference.

For additional details, see Endpoints in Jitterbit Script or Endpoints in JavaScript.