Versions Compared

Old Version 2

changes.mady.by.user Annegret Bernhardt

Saved on

compared with

New Version Current

changes.mady.by.user Annegret Bernhardt

Saved on

Key

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

With BPMN, processes end with end events. A process must have at least one end event, but it may also have multiple end events. An end event closes the process instance and deletes the related persistent state object from the database.

Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameinstance_persistent_state
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_excerpts

A process end is modeled by end events.

Process instances are kept in the persistent state database and they are deleted at process end:

  • When the end state of the BPMN is reached, the meta state Done of the root machine is reached.
  • The instance is deleted from the Done state after the holdTime expires.
  • The default holdTime is 60 seconds (PT60S). You can change the value in the service settings in the integration application (Bridge).

One BPMN element is available to model process ends:

BPMN ElementUsageDetails

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

End Event

The end event indicates that the process is completed.

Tip

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

A BPMN model may also have multiple end events.

You can create the execution model (On Event) for an end event:

  • The model will be executed when the end event is reached.

You can add execution for an end event for example...

  • ... to perform some clean-up tasks at the end of the process instance.
  • ... to send out notifications.
otp
Panel
titleOn this Page:
Table of Contents

Floatingfalse
maxHLevel2
Multiexcerpt include
SpaceWithExcerptINTERNAL
MultiExcerptNameBPMN_End_Event_Example
DisableCachingtrue
PageWithExcerptINTERNAL:_designer_examples

rp
Panel
titleRelated Pages: