You are here: Case management > Process modeling > Flows > Defining the run-time path of an assignment

Defining the run-time path of an assignment

You can define the conditions under which an assignment follows a particular path at run time. By using multiple connectors to capture different business scenarios, you can create flexible assignments.

  1. Add an assignment to a flow in your application.

  2. For each unique path that the assignment can take, hover over the assignment and drag a new connector to another shape in the flow diagram.

  3. Repeat the following steps for each connector that you create:

    1. Double-click the connector to open the Connector properties dialog box.

    2. In the Flow action field, press the Down Arrow key and select a flow action that displays fields to users at run time.

    3. In the Likelihood field, enter an integer between 1 and 100 that represents the probability of the flow action.

      The greater the integer, the more likely it is that the assignment follows the path of this flow action.

    4. Click Submit.

  4. Double-click the assignment to open the Assignment properties dialog box.

  5. In the Advanced section, click Assignment details, and then select the Allow auto-process check box.

  6. Repeat the following steps for each path that the assignment can take:

    1. Click + Add auto-process condition.

    2. In the Perform action field, press the Down Arrow key and select the name of a flow action.

      This list is populated with the flow actions that you provide in step 3.

    3. In the When field, press the Down Arrow key and select a when condition that controls whether the flow action runs.

      At run time, when conditions are evaluated based on the list order that you provide.

    4. Optional: Open the flow action and define a post-processing activity or data transform that runs when the flow action is completed.

  7. Click Submit.

  8. Click Save.

At run time, the assignment follows the first connector that meets the when condition that you define. No flow action is displayed to the user.

If no when condition returns a true value, the assignment follows the connector with the highest likelihood value and displays the corresponding flow action to the user.