Workflow templates for mediation contracts

System templates

The following properties are common to all templates. They are also optional and, therefore, can be skipped if not needed.

Common properties:

• Error handling The Enable workflow error handling option can be set to ON to use PRIMEUR system workflows to manage errors. Enabling the toggle switch, the Select error handling template drop-down list will appear with 2 templates: one to log all variables and one to notify errors. You can find details about the ehwft_logAllVariables and ehwft_logAllVariables templates in the Error workflow templates section.

• systemEnableLogDebugToFile Set this toggle button to ON to activate logs

Trigger type: On Demand

The On Demand trigger does not require any mandatory variable. The On Demand triggered workflow templates are triggered by a direct API invocation via REST. This API will accept a map of variables that will be passed to the instance as process variables. Any variable explicitly declared on the template to be requested when creating the Contract is added to the set of variables coming from the REST invocation. If a variable name is used when creating the Contract and is used in the map passed via REST as well, this second one wins over the Contract one.

1. SpExec operation

system_onDemand_exec

Goal: This system template performs a remote spExec operation when triggered onDemand.

Variables:

• cluster STENG cluster where the spExec operation is performed.

• executable Executable command to be run on the remote STENG shell.

• arguments Arguments that will be passed to the selected executable command.

2. RemoteLsOnDemand

remoteLsOnDemand

Goal: This system template performs a remote Ls operation when triggered onDemand.

There are no variables apart from Enable workflow error handling and systemEnableLogDebugToFile described above.