Home > Process Modeling and Simulation Concepts > Transaction Flow > Transaction Flow Constraints
A transaction ordinarily moves as far along the process as it can, but it can be held up if it has work to do or must wait for a resource or another constraint to continue.
A transaction is finished when one of these conditions is met:
A transaction is completed (reaches an endpoint). A transaction moves until it reaches an activity that does not have any outgoing connector lines, or if the lines leaving the activity are ‘Auxiliary’ or ‘No transaction flow’ lines. If a transaction has flowed to a subprocess, it returns to its original process (unless it was a Concurrent Subprocess) until it reaches an endpoint.
Simulation time runs out. Any transactions left in the middle of the process flow are stopped and do not count as completed transactions. However, a transaction stopped in this manner is still counted as part of the statistical calculations for any activity or resource that processed it before the simulation time ran out.
A transaction is manually discarded. This behavior is specified for an activity on the Properties dialog box - Task page - On Completion tab. Statistics for any activity or resource that processed manually discarded transactions includes these transactions.
Related Topics