Passing properties from one task integration to another task in the same workflow instance

This topic shows how to pass properties from one task integration to another task in the same workflow instance.

You can export task properties from one task integration to reuse them as variables in a successive task in the same workflow instance. The variables are resolved locally on the agent at run time. To add a task property within a successor task, use the following syntax:
${jobs.<job_name>.<property_name>}
where
<job_name>
is the name value or alias name value of the task from which you are exporting the property values
<property_name>
is the property that you are referring to. The <property_name> value is case insensitive.
Only the following task integrations can pass properties to other successor tasks:
IBM Sterling Connect:Direct tasks
Properties for IBM Sterling Connect:Direct tasks shows the list of properties that you can pass from one IBM Sterling Connect:Direct task to another and indicates the mapping between the Extra information properties of the task and the properties that you can use.
File transfer tasks
Properties for file transfer tasks shows the list of properties that you can pass from one file transfer task to another and indicates the mapping between the Extra information properties of the task and the properties that you can use.

Since you can use wildcards to specify a partial name condition, you can transfer more than one file within the same task, and you have one full set of properties for each transferred file.

JSR 352 Java Batch tasks
Properties for JSR 352 Java Batch tasks shows the list of properties that you can pass from one JSR 352 Java Batch task to another and indicates the mapping between the Extra information properties of the task and the properties that you can use.
Database tasks
Properties for database tasks shows the list of properties that you can pass from one database task to another and indicates the mapping between the Extra information properties of the task and the properties that you can use.

Properties for IBM Sterling Connect:Direct tasks

Table 1. Properties for IBM Sterling Connect:Direct tasks
IBM Sterling Connect:Direct properties that can be passed in another task definition IBM Sterling Connect:Direct job Extra Information properties 
${jobs.<job_name>.PrimaryNodeAddress}
 
Primary Node Address
 
${jobs.<job_name>.PrimaryNodeUserID}
 
Primary Node User
 
${jobs.<job_name>.SecondaryNodeName}
 
Secondary Node Name
 
${jobs.<job_name>.SecondaryNodeUserID}
 
Secondary Node User
 
${jobs.<job_name>.ProcessName}
 
Process Name
 
${jobs.<job_name>.DestinationDisposition}
 
Destination Disposition
 
${jobs.<job_name>.ProcessFileName}
 
Process File Name
 
${jobs.<job_name>.ProcessFileLocation}
 
Process File Location
 
${jobs.<job_name>.CompressType}
 
Compression Type
 
${jobs.<job_name>.CheckPointRestart}
 
Check Point Restart
 
${jobs.<job_name>.ActionSelected}
 
Action Selected
 
${jobs.<job_name>.SourceFilePath}
 
Source File Path
 
${jobs.<job_name>.DestinationFilePath}
 
Destination File Path
 
${jobs.<job_name>.ProcessNumber}
 
Process Number

Properties for file transfer tasks

Table 2. Properties for file transfer tasks
For the file number counter, the properties that can be passed in another job definition (a set of properties for each transferred file) For the file number counter, the job Extra Information properties (a set of properties for each transferred file) 
${jobs.<job_name>.File.counter.LocalFile}
 
File.counter.LocalFile
 
${jobs.<job_name>.File.counter.LocalUser}
 
File.counter.LocalUser
 
${jobs.<job_name>.File.counter.Protocol}
 
File.counter.Protocol
 
${jobs.<job_name>.File.counter.RemoteFile}
 
File.counter.RemoteFile
 
${jobs.<job_name>.File.counter.RemoteUser}
 
File.counter.RemoteUser
 
${jobs.<job_name>.File.counter.Size}
 
File.counter.Size
 
${jobs.<job_name>.File.counter.
    TotalTransferTime}
 
File.counter.TotalTransferTime
 
${jobs.<job_name>.NumberOfTransferredFiles}
 
Number of transferred files

Only one value for each task.

Properties for JSR 352 Java Batch jobs

Table 3. Properties for JSR 352 Java Batch tasks
JSR 352 Java Batch task properties that can be passed to another task Label 
${jobs.<job_name>.ExitStatus}
 
Job Exit Status
 
${jobs.<job_name>.JobInstanceId}
 
Job Instance Id
 
${jobs.<job_name>.executionId}
 
Job Execution Id
 
${jobs.<job_name>.JobName}
 
Job Name
 
${jobs.<job_name>.JobBatchStatus}
 
Job Batch Status
 
${jobs.<job_name>.self}
 
Self
 
${jobs.<job_name>.joblogs}
 
Job Logs
 
${jobs.<job_name>.Jobexecution}
 
Job Execution
The following variables are exported for each step of the task: 
${jobs.<job_name>.<STEP_NAME>.Name}
 
Step Name
 
${jobs.<job_name>.<STEP_NAME>.BatchStatus}
 
Step Batch Status

Properties for database tasks

Table 4. Properties for database tasks
Database task properties that can be passed to another job Label 
${jobs.<job_name>.NumberOfRows}
 
Number of rows
 
${jobs.<job_name>.PPS_PROPERTY_NAME}
 
The name of the procedure expressed
 
${jobs.<job_name>.PPS_PROPERTY_VALUE}
 
The value of the procedure expressed