59.3.9.70 Remote Workflow Action (web services)

Action Description
Remote Workflow Action (web services server) allows to manage remotely, from a local site, T-workflows of assets stored on a remote location. This action is useful when a local site has federated assets (imported from an external site) as it allows them to manage said assets directly on their remote systems (source sites).

The remote execution (e.g. attach and start, abort, reset) of a given T-workflow for an asset is performed by Etere Web Services, which receives a request for the execution of the T-workflow in the remote site's web service.

Note
For detailed information on the remote management of T-workflows using Web Services, please refer to the "Remote Web Service Management" section of the Federated Management chapter.

Action Parameters
To create an action of this type, the following fields must be compiled:

Parameters
Name - Insert a short descriptive name for the action.

Installation site - Select the external installation on which the T-workflow will be executed.

Select Remote workflow - Indicate the T-workflow that will be launched on the remote site.

NB: Here will be listed only T-workflows enabled for the web services user (set in the Sites section), displaying for each T-workflow a prefix related to its belonging site (e.g. "MyTv Miami - Copy hires on ftp3").

NB: The T-workflow set here must correspond to the installation site developed before; otherwise, unwanted results may be obtained.

Select Action Type - Choose the exact action to be performed; available actions are listed and explained below:

Attach and start workflow instance - The selected remote T-workflow will be called and immediately started; the action will return an output based on its result ('started', 'not started', 'asset not exist').

Abort workflow instance - The selected remote T-workflow will be aborted, and the action will return an output depending on the result of the operation (i.e., 'aborted', 'not aborted', 'asset not exists').

Reset workflow instance - The selected remote T-workflow will be reset, and the action will return an output depending on the result of the operation (i.e., 'reset', 'not reset', 'asset not exist').

Workflow instance status - The action will return an output based on the current status of the selected remote T-workflow (i.e., 'request error', 'asset does not exist', 'not started', 'active', 'completed', 'aborted', 'faulted').

Workflow instance running check - The action will return an output (i.e., 'running', 'not running', 'asset does not exist', 'request error') depending on the related status of the selected remote T-workflow.

Workflow instance ended check - The action will return an output (i.e., 'ended', 'not ended', 'asset does not exist', 'request error')  based on the related status of the selected remote T-workflow.

How to Use It
Once created to be used, the action for triggering a remote T-workflow (e.g. put a video file on a shared location) needs to be included in a local T-workflow under the T-Workflow designer, then attached and launched for the desired asset(s):
workflow_actions_remote