Parameter mapping for decision

OR (||) Parameter mapping in decision

The cases defined within a decision activity have different output string expressions and the actual output is decided during runtime. As you are not aware of the case that gets selected beforehand, use a OR (||) operator as a delimiter between the output of the cases. The OR (||) operator returns a single first non-nil value. The non-selected parameters always have a nil value and are not considered for further processing.

For example, there is a decision activity that has two cases:

• The output of the first case is templates.template4ce5b4be.user
• The output of the second case is templates.template105c1603.user

The OR (||) operator expression for this example is as follows:

${templates.template4ce5b4be.output.user || templates.template105c1603.output.user}

If the first case is selected during runtime, then templates.template4ce5b4be.user is used for further processing in the workflow as it is the first non-nil value. The templates.template105c1603.user has a nil value and is not considered.

If an activity parameter is from inside a decision block and the decision block is not selected, then the parameter (output or input parameter) evaluates to an empty value.

If an activity parameter is from a selected decision block having an empty-value string, then the next parameter having a value string is considered.

If you use interpolation in the error flow around a non executed decision from the primary flow, the resultant value is an empty string.