Process States
An OSM process can be in the following states specified by the standard:
- open.notrunning—Initial state of all transactions. This is the state immediately after the Prepare message was sent and acknowledged but before the Execute message. To move to the open.running state, an explicit ChangeProcessInstanceState message must be sent.
- open.running—State of a transaction being executed (that is, after the Execute message was sent and acknowledged), which may mean that there is an active workflow associated with it. If there is no associated workflow, it moves immediately to the closed.completed state. Otherwise, it will move to one of the closed states on receipt of the report about the workflow execution.
- closed.completed—The transaction was completed, and the target object changed its state accordingly. If a workflow was associated with the operation, the workflow was completed. There is no connection between the outcome of the workflow and this state, only with the state of the target object.
- closed.abnormalCompleted—Flags that the associated workflow has cancelled due to an internal error and that the transaction was successfully rolled back.
- closed.abnormalCompleted.terminated—Flags that the transaction was aborted as requested by the client and that it rolled back successfully.
In the closed states, there is no active associated workflow, and the state of the target was updated accordingly. The state diagram in Figure 1 summarizes the description.