Decision Checks

Decision name and code uniqueness

Decision names and codes must be unique in the namespace.

Manual correction: Modify the duplicate name/code

Automatic correction: Appends a number to the duplicate name/code

Invalid decision

A decision represents a conditional branch when a unique flow is split into several output flows, or it represents a merge when several input flows are merged into a unique output flow. That is why a decision must have more than one input flow or more than one output flow.

Manual correction: Add any missing flows on the decision

Automatic correction: None

Event condition coherence

All conditions on outgoing flows must be of the same type. Condition types can be a Boolean expression or an event. A flow defined from a decision object to a receive activity is considered as an event that corresponds to the reception of a message.

Manual correction: Assign the same conditions to all outgoing flows

Automatic correction: None