Properties of a decision
The properties of a decision belong to the following categories.
You can select decisions that the current activity can depend for completion.
- Completion required
If selected, sets the activity as a dependent. The activity can only complete once the decision rule is met.
- Only when active
If selected, uses the dependent only when the path is active.
Use this tab to configure the event to fire, milestone to achieve, and state to change, when the decision becomes available.
- Fire event
The event that will execute when the decision node becomes available.
- Set milestone
The milestone to achieve when the decision node becomes available.
A state to use as the default state when the decision becomes pending.Associating states with a decision especially helps if the decision becomes pending for a second time.
- State origins
The state to use depending on the origin of the activity. For example, Decision 1.
If no origin-specific state is defined for the decision, the default state is used when the decision becomes pending.
You can associate single or multiple states with a decision depending on the path of the decision.
You can select a different or the same state as another origin or the default state.
If you specify optional states, first specify the default state for the activity. Otherwise. a message appears.
You can associate actions with a state to take place when an event becomes pending, depending on the path.
Use this tab to configure the general properties for a decision.
Brief description for the decision.
The color of the decision node.
To change the color of the Decision node, click the color palette to open, select the color, and click Apply.