What is the minimum set of variables and/or inputs needed to keep a user’s selection when a submission loops back to a User Input Task?

What is the minimum set of variables and/or inputs needed to keep a user’s selection when a submission loops back to a User Input Task?

• A. Rule input, activity class parameter, and a process variable
• B. Process variable only
• C. Rule input and a process variable
• D. Activity class parameter and a process variable but no rule input

Answer: (A)

When a User Input Task loops back, you must preserve the user’s choice by storing it in a process variable and ensuring the task’s interface can access that value. The interface gets its inputs through rule inputs, and the activity class parameter wires those inputs into the task’s interface as it renders again. So the combination of a process variable (to persist the selection), a rule input (to expose the value to the interface), and an activity class parameter (to pass that value into the interface when the task is shown) is what lets the previous selection be displayed and subsequently updated on resubmission. Without any one of these, the value wouldn’t reliably survive the loop.

When a User Input Task loops back, you must preserve the user’s choice by storing it in a process variable and ensuring the task’s interface can access that value. The interface gets its inputs through rule inputs, and the activity class parameter wires those inputs into the task’s interface as it renders again. So the combination of a process variable (to persist the selection), a rule input (to expose the value to the interface), and an activity class parameter (to pass that value into the interface when the task is shown) is what lets the previous selection be displayed and subsequently updated on resubmission. Without any one of these, the value wouldn’t reliably survive the loop.