Switch

This evaluation will pass if a value from the expression matches one of the values defined in the cases.

Switches have many automation triggers associated with them for each case defined. Actions under the “case” automation trigger execute when the value from the switch matches the value from the case, and actions under the “Default” automation execute when none of the cases match.

Example : Suppose an application has several possible values for a status field and you want to run different actions when the field has the different statues. While these checks could be processed with a series of Compare Two Text Strings actions it would be easier to configure and faster to process when defined as a switch that reads the status field once and runs the comparisons for each status until it finds one.

Use the expression builder to define the value to compare.

Use the expression to define a value that will be compared to the switch value. A description for the case can optionally be defined that will be displayed in the action tree. The order determines what order the cases will be evaluated in. Additional efficiency can be gained by evaluating the more common cases first so the action does not have to process more cases then needed.

Useful as a comment, this description will overwrite the automatically generated description in the Action Manager.

When an action is queued, the subsequent actions continue to process without it. Meanwhile, the queued action and its children process separately. Queue actions that you don't want a user to wait for.