Where does a payroll flow task derive its parameter value when binding to the flow task parameter?

• A. Derives the value from a SQL Bind
• B. Derives the value from the context of the current flow instance
• C. Derives the value from the output of the previous task
• D. Derives a specific value to the parameter as entered by the user

Answer: (C)

In a payroll flow, data is handed from one task to the next by binding a parameter to the output of the previous task. This setup makes the subsequent step receive exactly what the prior step produced, creating a seamless data handoff through the flow. Binding to the output of the previous task ensures dynamic propagation of results, which is the intended mechanism for flowing values along the sequence. Binding to a SQL bind pulls in data from a query variable rather than the task’s result, using the current flow context or a user-entered value would not reflect the immediate predecessor’s result or would force static input, respectively. Therefore, the parameter value should derive from the previous task’s output to preserve the flow’s automatic data transfer.