State Changes of Process and Activity Instances
This chapter describes possible state changes for activity and process
instances for service calls depending on the preconditions.
Possible State Changes for the AdministrationService
The following methods of the
AdministrationService might change
the state of process instances and activity instances:
abortProcessInstance()
For method abortProcessInstance() the following state changes are
possible:
- process state before:
- active
- interrupted
- halted
- state after:
- aborted for the root process, all sub-processes and activities that
are not yet completed
forceCompletion()
Possible states for forceCompletion() are:
- non-interactive activity state before:
- application
- suspended
- hibernated
- interrupted
- state after:
forceSuspendToDefaultPerformer()
Possible states for forceSuspendToDefaultPerformer() are:
- activity state before:
- application
- suspended
- hibernated
- process state before:
- activity state after:
- process state after:
startProcess()
Possible states for startProcess(): are:
Possible State Changes for the WorkflowService
The following methods of the
WorkflowService might change
the state of process instances and activity instances:
activate()
For method activate() the following state changes are
possible:
- activity state before:
- suspended
- hibernated
- application
- process state before:
- activity state after:
- application
- hibernated for activities with application that provide asynchronous
receive functionality
- process state after:
complete()
Possible states for complete() are:
- activity state before:
- process state before:
- activity state after:
- process state after:
- completed if all activities are completed, otherwise state does not change
suspend()
Possible states for suspend() are:
- activity state before:
- process state before:
- activity state after:
- process state after:
abortActivityInstance()
Possible states for abortActivityInstance() are:
- activity state before:
- suspended
- application
- interrupted
- hibernated
- halted
- process state before:
- state after:
- if abort scope is root hierarchy:
- aborted for specified activity, its root process, all contained
sub-processes and activities that are not yet completed
- if abort scope is sub hierarchy:
- aborted for specified activity, including contained subprocesses
and activities, if activity instance is a subprocess
- completed if the last activity of the process is aborted and is not a
subprocess.
startProcess()
Possible states for startProcess() are:
abortProcessInstance()
Possible states for abortProcessInstance() are:
- process state before:
- active
- interrupted
- halted
- state after:
- abort scope is root hierarchy:
- aborted for the state of root process, all sub-processes and activities
that are not yet completed
- abort scope is sub hierarchy:
- aborted for the state of the sub-process, all its subprocesses and
activities that are not yet completed