core.process_model_execution package handles the execution of
It contains numerous services, handlers and facades to accomplish this task. The most important ones are explained below.
Whenever you want to start a new instance for a
ProcessModel, this is the service you will need.
It contains the entire operative necessary for handling a ProcessModels' execution.
You can start a Process instance by simply calling its
If you want to wait until the Process has finished, call the
startAndAwaitEndEvent method instead.
If you want to wait until a specific EndEvent is reached, call the
This service will retrieve all running ProcessInstances from the
ProcessInstance repository and restart
This service is designed to be run only once, when you first startup the AtlasEngine.
It is not recommended, to use this service after the initial start!
FlowNodeHandler is the base class for all handlers; it provides an
executeInternally method where the logic of the derived handlers is
The base class also offers a private hook named
afterExecute, which is
executed after each
FlowNode instance has finished.
ProcessTokenFacade contains all methods which implements common Tasks for
An example would be to store the current state of a process or exporting metrics.
Each BPMN type has its own handler; these handlers are named after the
respective type they are supposed to handle and are derived from the
FlowNodeHandler base class.
ExecuteProcessService will delegate the execution of each
instance to a matching
For example, a
ScriptTask will be run by the
ServiceTask by the
Mapping each BPMN type to a handler is done by the
The factory maps the various BPMN types to their respective handlers; it also
creates handlers for any
BoundaryEvent that may be attached to the
These additional handlers are attached to their parent handler by decorators.
Assuming we have a
ScriptTask with two
BoundaryEvents attached to it:
In this scenario, three handlers will be created; calling
execute on the
returned handler will produce the following call stack:
The order in which the
BoundaryEvent handlers are chained to the original
handler is also important.
In this case, the
TimerBoundaryEventHandler has to start its timers as fast
ScriptTask encounters an error, the
have the ability to handle it and decide which
FlowNode to execute next.
On the other hand, the
ErrorBoundaryEventHandler would not want to handle an
error that is related to the
The factory is build to prevent such conflicts. It does this, by making sure
that each decorator is run before the actual
FlowNode is executed.
ProcessTokenFacade manages the
ProcessToken for the process that is
currently being run. It allows each FlowNodeInstance to query information from
ProcessToken that is relevant for its specific UseCase.
This guarantees that each
FlowNode instance only gets the information that it
actually needs, instead of the entire
It performs the following tasks:
FlowNode instance result, using the
ProcessTokens together, using
For backwards compatibility:
ProcessToken in the old format, using
This will provide you with a structure that resembles the old
ProcessModelFacade provides access to the elements of a given
ProcessModel. These elements can be
FlowNodes, SequenceFlows or any other
object that is contained within the ProcessModel.
FlowNode instance, for example, can use this Facade to determine the
FlowNode that is to be executed next.
Or a Split-Gateway
can use it to find its correspondingJoin-Gateway`.
SubProcessModelFacade provides access to the elements of a given
It is created, using the parent process'
This allows the
SubProcess to access its parent ProcessModel as well.
SubProcessModelFacade implements the same
This allows for the
SubProcessModelFacade to be be passed through to the
handlers, without them knowing they're executed inside a
Because of this, the
SubProcesssModelFacade can be passed to the individual
handlers, without them knowing that their are executed inside a