Operation actions in Jitterbit Integration Studio

Introduction

Each operation can be configured with actions to take on success or failure of the operation, including running another operation or sending an email notification. The result is linked operations or notifications that are kicked off when conditions are met. An operation being kicked off based on operation actions is said to be downstream of an upstream operation before it.

Access operation actions

The Settings option for operations is accessible from these locations:

• The project pane's Workflows tab (see Component actions menu in Project pane Workflows tab).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).
• The design canvas (see Component actions menu in Design canvas).

Once the operation settings screen is open, select the Actions tab:

Configure operation actions

Each option available within the Actions tab of the operation settings is described below.

• Condition: Use the first dropdown to select the condition that should trigger the action. These conditions can be set:

  • On Success: The action is triggered when the operation is successful.

    Tip

    You can force a success trigger even if the operation failed. This setting is available under the operation settings Options tab and may be useful for setting up later parts of the project without requiring success of a dependent operation (see Operation options).

  • On Fail: The action is triggered when the operation fails.

  • On SOAP Fault: The action is triggered when a SOAP fault occurs. A SOAP fault is an error resulting from incorrect message format, header processing, or incompatibility. This condition is applicable only for operations using SOAP activities or Salesforce-based activities (using the Salesforce, Salesforce Service Cloud, or ServiceMax connectors).

• Action: Use the second dropdown to select the action to perform, limited to a maximum of one of each action type for each condition. These actions can be configured:

  • Run Operation: Kicks off the operation selected in the next dropdown, and can be used to link or chain together operations to run subsequently.

    • Operation: When Run Operation is selected, the third dropdown lists available operations within the project, including any operations that are included in other workflows within the project that have not already been associated with an action.

  • Send Email Notification: Sends an email notification selected in the next dropdown.

    • Email Notification: When Send Email Notification is selected, the third dropdown lists available email notifications configured within the project that have not already been associated with an action.
    • Create New Email Notification: When Send Email Notification is selected, a link is available to configure a new email notification. Documentation on configuration is available under Email notifications.

• Add Action: To add the action to the operation, make sure all three dropdowns have selections and then click Add Action. The action is then displayed in the table below.

• Remove Action: To remove an action from an operation, click the remove icon next to the parameter within the table. The action is removed from the table.

Display of links on the design canvas

When you add operation actions, you can visually see the links between elements with connected lines on the design canvas. For details, see the section on Lines in Design canvas.