If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Trigger Workflow

Initiates invocation of the specified workflow. If synchronous=false, the task quits immediately after triggering (it does not wait until the invoked workflow is finished); otherwise, the task waits until the invoked workflow is finished. In the synchronous mode, the task result is equal to the invoked workflow result.

Properties

Name Type Description Expression support

Name	Type	Description	Expression support
Workflow Id	mandatory	ID of the workflow to run. Workflow ID specification depends on the workflow execution context: In the server context, use the `<sourceId>:<workflowName>.ewf` notation, for example, `WF02:02_03b_Executor.ewf`. The `sourceId` prefix is defined in Workflow Component. Outside the server (from IDE or via `runewf.[bat\|sh]`), you can use two mutually exclusive notations: `<sourceId>:<workflowName>.ewf`: In this case, the `<sourceId>:` prefix is ignored and the specified workflow from the current folder is run. This is useful when you want to develop and test workflows locally in the IDE and deploy them to the server later on. `<path>/<workflowName>.ewf`, for example, `../02_Run_Plans/02_03b_Executor.ewf`. The `path` is optional and is relative to the current workflow.	semi-expression
Synchronous	optional	Invocation type. Default value: `false`.	none
Parameters	optional	Set of parameters to pass to the workflow as global variable values.	none

Workflow Id

mandatory

ID of the workflow to run. Workflow ID specification depends on the workflow execution context:

In the server context, use the <sourceId>:<workflowName>.ewf notation, for example, WF02:02_03b_Executor.ewf. The sourceId prefix is defined in Workflow Component.
Outside the server (from IDE or via runewf.[bat|sh]), you can use two mutually exclusive notations:
- <sourceId>:<workflowName>.ewf: In this case, the <sourceId>: prefix is ignored and the specified workflow from the current folder is run. This is useful when you want to develop and test workflows locally in the IDE and deploy them to the server later on.
- <path>/<workflowName>.ewf, for example, ../02_Run_Plans/02_03b_Executor.ewf. The path is optional and is relative to the current workflow.

semi-expression

Synchronous

optional

Invocation type. Default value: false.

none

Parameters

optional

Set of parameters to pass to the workflow as global variable values.

none

Parameters properties

Name	Type	Description	Expression support
Name	mandatory	Name of the parameter.	semi-expression
Expression	mandatory	Expression evaluating the value of the parameter.	expression

Name

Type

Description

Expression support

Name

mandatory

Name of the parameter.

semi-expression

Expression

mandatory

Expression evaluating the value of the parameter.

expression

Predefined variables

TRIGGERED_WF_ID: If the workflow was successfully triggered, this variable contains the ID of the triggered workflow instance.

Sample

<executable class="com.ataccama.adt.task.exec.EwfTriggerWorkflowTask">
    <workflowId>simple-params.ewf</workflowId>
  <synchronous>false</synchronous>
    <parameters>
        <parameter name="command1" expression="'sometext'"/>
        <parameter name="command2" expression="1" />
    </parameters>
</executable>

Was this page useful?