Decision

A Decision is a branch point: a diamond-shaped step whose job is to send each entity down one of several paths. By default it takes no time and holds nothing, so entities pass straight through and split according to the rules on its outgoing connectors.

Setting the branches

A Decision does not carry the branching rules itself; you set them on its outgoing connectors, exactly as on any step. Draw a connector to each destination, then choose how entities divide:

• By percentage to send a share down each path.
• By condition to route on a rule, such as an attribute value, with the first matching path winning.

Any of the routing types work here. The diamond simply marks the spot on the diagram where the flow splits.

When to use one

Reach for a Decision when you want the branch point to read clearly on the diagram. Functionally it is the same as adding percentage or conditional routes to a normal activity’s outputs, but the diamond keeps a busy model easy to follow. If you need the branch to take time or hold a resource, give the Decision a processing time like any other activity.