| Property | Required | Description |
|---|---|---|
| ID | Required |
A unique identifier for the start event. This value is system-generated and cannot be changed. For example: StartEvent_1w29b3h. |
| Name | Optional |
The label displayed on the process diagram. Tip: Use a clear, business-focused name that describes what starts
the process.
For example: HRProcess_Start. |
| Documentation | Optional | A free-text description explaining the purpose of the start event. Use this field to capture business context for other users. |
| Asynchronous Continuation | Optional |
When a start event is configured with asynchronous continuation, the process instance is created immediately, but the execution does not continue in the same request or thread. Instead, the process is paused at the start event and resumed later by a background job. This creates a breakpoint in execution and separates process instantiation from further processing. It helps avoid long-running synchronous operations and improves reliability by ensuring that the initial process state is saved before execution continues. |
| Redirect after submission | Optional |
If the event was started manually, you can decide what happens after the starting page is submitted, using the Redirect after submission drop-down menu. |
| Customize start form | Optional |
You can use the Customize start form checkbox to adjust the following options:
|
| Form name | Optional |
An optional form can be used to begin a process. The form must exist within the same project as the process definition to be selected. Select a form from the drop-down list. When a form is selected, an additional No login required checkbox is displayed. Check it to allow forms to be filled and submitted anonymously, without authentication. |
| Mapping type | Required |
The mapping type sets how data is passed between the start event and the process. There are five options for sending this data. |