Conditionality Based on an Action's Checklist

When using conditionality in your Case flows, you can use a number of types of system data as part of your condition, for example standard system work item fields and custom data fields.

We have now added the ability to use the results of individual checklist items, both global and local, in your conditions, letting you choose alternate routes depending on how a check has gone.

Watch this video to see how that can be done, or read below for more specifics and details:

Clicking on the dropdown will reveal the Actions that have checklists to choose from. They will be displayed in the order in which the Actions appear in the flow. Clicking on an Action will show the checks that you can choose to base your condition on, displayed in order in which they appear on the checklist.

You can only use the 'Equals' and 'Not Equals' conditions for conditions based on the results of a check in an Action's checklist, just as you would short text data fields.

The values you can create conditions for against a checklist item are "Yes", "No", and "NA" for Not Applicable. Be aware that these values are case sensitive and should be entered in the value field exactly as above within double quotes.

As standard, make sure to create an 'else' branch, to handle the flow when you're conditions are not met. At runtime, if the condition is not met, the system will execute the 'else' branch.

If you're using the advanced option to build a more complex expression, checklist items can also be incorporated here - once you've picked them from the dropdown list they'll be added into your expression with a unique identifying GUID.

Note that you can only use checks from Actions in a previous step in your conditional expressions and you cannot use check from ad-hoc Actions.

Once you're happy with your condition settings, click 'validate' to ensure they'll work at runtime, then 'OK' to apply the condition to the Case flow.

Last updated