-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Description
Some activity patterns (based on a sequence of activities) have different courses of action depending on what the outcome/result of the previous activity in the sequence. Supporting different courses of action would be a powerful feature.
Basic Example
On a production / assembly line a part may be inspected (by a human or automated means). If the part that passes may continue to the next stage of the intended production activity. If it fails, it may be sent for analysis to determine why it failed. Each course of action is a different sequence of activities once the pass/fail decision has been made. Information records required on each path can be important.
Drawbacks
This is a broader capability than currently available and may require re-engineering of the Activity Editor (workflow, UI and code base).
Unresolved questions
No response