Taskflows

Back Next

Guidelines for using input parameters in taskflows

Use the following guidelines when you use input parameters in a taskflow:

Use the Data Task step to override input parameters. However, in advanced cases, you can override input parameters with an Assignment step.

If you define a field to override the same parameter in both the Assignment step and the Data Task step, the taskflow considers the value assigned in the Data Task step.

If you use a Data Task step to assign values to input or in-out parameters, the assignments must be independent of each other. If you use an Assignment step to assign values to input or in-out parameters, an assignment operation can use the result of a previous assignment operation in the same step.

For example, you have two source objects, SO1 and SO2. You want to override SO1 with the value

Account

and override SO2 with the value

SO1

. Use the Assignment step to override the parameters.

The following image shows the source object

SO2

overridden with the value of

SO1

When you run a taskflow as an API, you can use the connection parameter to pass a connection name or connection ID at run time.

For example, if you want to use the connection name, you must pass the connection name in the connection parameter as shown in the following sample:

"source":{
"Source":{
"object":"abc",
"connection":"FileSourceConnectionName"
}
}

If you want to use the connection ID, you must pass the connection ID in the connection parameter as shown in the following sample:

"source":{
"Source":{
"object":"abc",
"connection":"0100000B000000000004"
}
}

When you configure the Data Task step to override the parameter file connection and parameter file object, you must ensure that both the parameters, that is, source object and source connection are passed either through the parameter file or taskflow. Otherwise, an error occurs.

Guidelines and best practices for using parameters in a taskflow

Download Guide

Watch

Comments

Cloud Data Integration Homepage