Skip to Content

Invoke Operation (Beta) tool in Jitterbit Integration Studio

Introduction

The Invoke Operation (Beta) tool is a project component that is used as a step in an operation to run a specified operation that exists in the current project. It can be used as an operation step anywhere a script can be used as an operation step.

Note

To provide feedback on this beta feature, contact the Jitterbit Product Team.

Info

The RunOperation, RaiseError, and CancelOperationChain functions provide the underlying functionality for this tool.

Create an Invoke Operation instance

A new instance of an Invoke Operation (Beta) tool can be created from these locations:

An existing Invoke Operation (Beta) tool can be edited from these locations:

Configure an Invoke Operation tool

The Invoke Operation (Beta) configuration screen includes these fields and actions:

invoke operation configuration

  • Operation: Use the menu to select an operation in the current project.

  • Run type: Select whether downstream operations run synchronously or asynchronously:

    • Synchronously: When selected, the invoked operation and any downstream operations chained to it will run sequentially. The agent group will wait for the invoked operation chain to finish before processing the next steps in the stream that invoked it.

    • Asynchronously: When selected, the invoked operation and any downstream operations chained to it will run simultaneously. The agent group will continue processing the steps in the current stream while independently processing the invoked operation chain. There is no guarantee which operation or chain will complete first.

  • Error handling: These error handling options are enabled when Synchronous is selected as the Run type:

    • Raise error if operation fails: When selected and the invoked operation fails, the initiating operation (that the Invoke Operation (Beta) tool is within) will fail and stop processing. Processing will continue for any On Fail operation actions configured on the initiating operation.

      A fatal error is written to the initiating operation's log messages, which can be viewed from the operation logs or the Messages tab of the Runtime Operations page:

      Fatal Error <message> This error was raised by a call to the RaiseError function.
      
    • Cancel operation chain if operation fails: When selected and the invoked operation fails, the initiating operation (that the Invoke Operation (Beta) tool is within) will continue processing. Processing will stop on the completion of that operation and not continue for any On Fail or On Success operation actions configured on the initiating operation.

    Important

    If both error handling options are enabled, an error is raised for the initiating operation and no further processing will occur in either the initiating operation or operations chained by configured On Fail actions.

  • Save Changes: After making changes to a new or existing configuration, click to save and close the configuration.

  • Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

Once configured, the Invoke Operation (Beta) instance is named the same as the name of the operation it is calling.

Note

Operations linked by the Invoke Operation (Beta) tool do not have a visual operation reference or line on the design canvas.

Actions

The actions bar for an Invoke Operation (Beta) tool has these actions:

invoke operation

Icon Description
Go to invoked Operation navigates to the workflow where the specified operation resides. The operation is displayed with a blue border outlining the operation.
Edit opens the configuration screen.
Cut places a copy of the component on your clipboard and deletes the original component from the project (see Component reuse).
Copy places a copy of the component on your clipboard (see Component reuse).
Remove removes the component as an operation step from the operation.