Start Events
Start events define where a Process or Sub Process starts.
The process engine supports different types of start events:
The engine requires at least one start event to instantiate a process. There can be a maximum of one blank or timer start event per process definition. There can be multiple message or signal start events.
Asynchronous Instantiation
A start event may be declared as asynchronous with cadenzaflow:asyncBefore="true"
<startEvent id="startEvent" cadenzaflow:asyncBefore="true" />
This will ensure that the process engine creates a process instance when the process is instantiated, but the execution of the initial activities is not done synchronously. Instead, a job is created and asynchronously processed by the job executor. See the Asynchronous Continuations section of the User Guide for some background information.
CadenzaFlow Extensions
Attributes | cadenzaflow:asyncBefore, cadenzaflow:asyncAfter, cadenzaflow:exclusive, cadenzaflow:formHandlerClass, cadenzaflow:formKey, cadenzaflow:formRef, cadenzaflow:formRefBinding, cadenzaflow:formRefVersion, cadenzaflow:initiator, cadenzaflow:jobPriority |
---|---|
Extension Elements | cadenzaflow:failedJobRetryTimeCycle, cadenzaflow:formData, cadenzaflow:formProperty, |
Constraints |
The cadenzaflow:exclusive attribute is only evaluated if the attribute
cadenzaflow:asyncBefore or cadenzaflow:asyncAfter is set to true
|
The attributes cadenzaflow:asyncBefore and cadenzaflow:initiator are only available for start events of a Process
|
|
Only one cadenzaflow:formData extension element is allowed
|
|
The attributes cadenzaflow:formHandlerClass and cadenzaflow:formKey
are only available for the intital start event of a Process
|