How to Configure a Parameter Set in a Taskflow

Back Next

Parameter scope

When you define values for the same parameter in multiple sections in a parameter set, the parameter with the smallest scope takes precedence over parameters with a larger scope.

In this case, the taskflow gives precedence to parameter values in the following order:

Value defined in the Subtaskflow step section.

Values defined in a taskflow section.

Values defined in the #USE_SECTIONS section.

Values defined in a global section.

If you define a parameter in a Subtaskflow step section and in a taskflow section, and the taskflow uses the Subtaskflow step, the taskflow uses the parameter value defined in the Subtaskflow step section.

For example, consider a taskflow that contains a Subtaskflow step named Subtaskflow step1 as shown in the following image:

The image shows a taskflow that contains a Subtaskflow step.

You define the following parameter values in a parameter set:

#USE_SECTIONS
$$input=employee_table
[GLOBAL]
$$location=USA
$$department=R&D
[Default].[Folder1].[TaskflowA]
$$input=Leads_table
$$department=HR 
$$designation=Manager
[Default].[Folder1].[TaskflowA].[Subtaskflow step1]
$$input=Associates_table
$$department=Finance

TaskflowA contains Subtaskflow step1.

When you run TaskflowA, TaskflowA uses the following parameter values:

Parameter	Section	Value
$$input	[Default].[Folder1].[TaskflowA]	Leads_table
$$department	[Default].[Folder1].[TaskflowA]	HR
$$location	[GLOBAL]	USA

When you run Subtaskflow step1, the taskflow uses the following parameter values:

Parameter	Section	Value
$$input	[Default].[Folder1].[TaskflowA].[Subtaskflow step1]	Associates_table
$$department	[Default].[Folder1].[TaskflowA].[Subtaskflow step1]	Finance
$$location	[GLOBAL]	USA
$$designation	[Default].[Folder1].[TaskflowA]	Manager