- Created by Annegret Bernhardt, last modified on Jan 05, 2024
With BPMN, processes are started by start events. A process must have at least one start event, but it may also have multiple start events. During process start, a process instance is created.
Process instances are kept in the persistent state database: The instances are created on process start and deleted on process end. Refer to xUML Service State Machines for further information.
A process start is modeled by start events:
The Designer offers you several start events to choose from: Available Start Events. | |
You can trigger the POST operation of a start event via the Angular application if your service contains at least one user task with an assigned form. | |
After deployment, you can see all start events in the instance list of the generated Angular application and you can trigger them here. Click icon to display all start events and select the one you want to use. Go to Deploying a Service for further information. | |
A start event can only be created via the elements toolbar.
|
Available start events are:
BPMN Element | Usage | Details |
---|---|---|
| ||
| ||
|
Start Event
The plain start event creates a process instance by a POST call (without parameters). Go to the event's reference page Start Event for all details. | |
You can create the execution model (On Event) for a start event:
|
Message Start Event
"Message" is not restricted to emails or calls: Every action that represents or contains information for a recipient is a message.
The message start event creates a process instance by a POST call (with parameters):
Go to the event's reference page Message Start Event for all details. | |
The execution model (On Event) for a message start event is created by default to process the message parameter. | |
| |
| |
| |
Deleting the execution model would only make sense in very special cases, e.g. if you do not need the parameter anymore but do not want to change the interface of the service. If you don't need the message parameter, use a plain start event instead. |
Timer Start Event
The timer start event creates process instances based on time patterns (scheduler) or time cycles (timer). It is useful if you want to execute regularly recurring tasks. Go to the event's reference page Timer Start Event for all details. | |
You cannot trigger the timer/scheduler from outside the service, it does not have a REST interface. | |
Go to Bridge User Guide > xUML Service Settings for details about the management of service settings. | |
You can create the execution model (On Event) for a timer start event:
|
BPMN_Start_Event_Example