Remote Workflow

Trigger a workflow on a remote Node and wait for termination. Once the request has been posted, the standard WebApi is used to wait for the end of remote workflow instance, and to retrieve errors, messages, transfers and context.

Used with iterator or folder_scan, you can easily create and execute distributed workflows, where each one will work with its own data set.

Workflow and version
Select workflow and version to launch.

Execution node
Select on which node this workflow will be executed. You can select an existing node or select ‘Auto select’ to let the system decides for you. It will select the oldest launched node.

Parameters
A list of keys/values sent as global context to remote workflow. Contrary to embedded workflow, remote workflow will not benefit of global and parent caller context, i.e. each unknown variable used in the remote workflow has to be set as parameter.

Check status delay
Specify at which frequency to verify remote workflow status, until its state changes to ended or aborted.

Auto distributed stuff

This diagram illustrates simultaneous executions on 4 distinct auto selected agents. As each iteration provides distinct loop_index/key/value/file_path, you are able to send it as parameter to remote workflow, allowing it to work with its own data set.

Explicit distributed stuff

This diagram illustrates simultaneous executions on 3 selected agents.

Note the use of ‘Iterate for each link’ in Folder Scan: It allows remote tasks to receive unique loop_index/key/value/file_path.