Versions Compared

Old Version 2

changes.mady.by.user Annegret Bernhardt

Saved on

compared with

New Version 3

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WDESIGNER and version 23.1

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.

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameinstance_persistent_state
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_excerpts

A process start is modeled by start events:

  • Start events will generate a POST operation to the API of the generated service.
  • This operation can be used to start an instance of the process within the service.

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.

Tip

Go to 2023-04-26_17-02-38_Deploying and Starting the Deploying a Service for further information.

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNamecreation_of_start_events
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_excerpts

Anchor
available_start_events
available_start_events

Available start events are:

BPMN ElementUsageDetails

  • Plain start event.
  • Use this event to start the process.

  • Start event with data.
  • Use the message start event if you need to provide data into the process at start.

  • Start event with timer and scheduler options, use the options depending on your use case:
    • Timer: Start the process after a specified duration (e.g. all 5 minutes).
    • Scheduler: Start the process at a specific time (e.g. Mo-Fr at 8 a.m.).

Start Event

The plain start event creates a process instance by a POST call (without parameters).

Tip

Go to the event's reference page Start Event for all details.

You can create the execution model (On Event) for a start event:

  • The model will be executed when the start event occurs.
  • You can use this start event's execution model for preparations that need to be executed at the beginning of a process instance.

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):

  • The body of the POST call contains the defined message parameter.
Tip

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.

  • You need to define the type of the incoming message (replace any by a dedicated type).

  • You need to at least persist the message parameter if you want to access this information later on in the process.

  • You can add more executional parts.

  • You can also remove the execution model. In this case, the message parameter is dropped.
Info

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.

Tip

Go to the event's reference page Timer Start Event for all details.

Info

You cannot trigger the timer/scheduler from outside the service, it does not have a REST interface.

  • In the model, you define the default of the timer/scheduler. If service requirements change, you don't have to change the model: You can change the timer/scheduler settings in the service settings in the Integration application (Bridge).
Tip

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:

  • The model will be executed when the start event occurs.

Otp
Floatingfalse
maxHLevel2

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameBPMN_Start_Event_Example
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_examples

Rp