Flow Parameters for Task Iterations

Task parameters submit the information required for the task submissions to complete successfully.

Task iteration flows have two sets of parameters:
  • Parameters for Submit Another Task
  • Parameters for the repeat submission task that's submitted multiple times
Use any of these options as input values for the repeat submission task:
  • Task parameters from the flow parameters defined while creating the flow
  • Return parameters from the repeat formula
Use any of these options as flow parameter values:
  • If the task parameter name, exposed in the UI at the flow-level, matches the Base Flow Parameter Name, then the values are used directly.
  • If the task parameter names don't match the Base Flow Parameter Name, the application uses a fast formula function to pass the flow parameter values as the task parameters. This formula function is built into the repeat formula.
    For example, assume that you have defined the flow parameter as 'Effective Date', and the corresponding Base Flow Parameter Name is 'EFFECTIVE DATE'. The application uses formula function GET_FLOW_PARAM_VALUE () and stores the return value of this formula function in the task parameter 'EFFECTIVE DATE'. The formula function is:
    • *EFFECTIVE DATE=GET_FLOW_PARAM_VALUE ('Effective Date')
Provide the correct parameter basis when you define the task parameters.
  • Some of the static parameters like the Effective Date or the Start Date can have a parameter basis value of 'Bind to Flow'.
  • The dynamic parameters like the Payroll Statutory Unit ID are derived from the database tables. Hence you can have a parameter basis value of 'Bind to Flow Task' or 'Context Binding'.
  • If you have defined specific names for the flow task parameters, you must ensure that the same names are used in the repeat formula.

Alternately, use the return parameters from the repeat formula as the task parameters. In this case the input parameters for the repeat formula are only the Base Task Name and the Repeat Counter. While calling the formula, the application uses these two parameters to get the context of the job submission. You create the Repeat formula to return input values for the submission task.

The formula output Repeat Flow decides if another job submission is required.

For example, for the Archive End-of-Year Payroll Results process the following parameters are defined as static parameters:
  • Effective Date
  • Start Date
  • Tax Year Date
  • Repeat Counter

    The Repeat Counter is a static variable and is maintained by the application. During the iteration process this parameter increments by '1' after every submission.

In this example, these are the dynamic parameters for each submission:
  • Payroll Statutory Unit ID
  • Repeat Flow

However, you can also define the Tax Year as a dynamic parameter, so that you can generate the report for various years.