Setting the Event Type

Set whether an event is a start, intermediate, end or boundary event.

Manually Setting the Event Type

Context

In Innovator, the event's type is normally recognized automatically based on the position of the incoming sequence or message flows. However, there are certain circumstances where the event type needs to be manually set:

Event Type Criteria for Automatic Recognition
Start event Only outgoing sequence flows
Incoming or outgoing intermediate event Both incoming and outgoing sequence flows: direction can be automatically recognized based on message flows. If this is not the case, it needs to be set manually.
End event Only incoming sequence flows
Interrupting or non-interrupting embedded subprocess start event

In event-based subprocess, only outgoing sequence flows

Is automatically created as an interrupting event; can be manually set to non-interrupting

Interrupting or non-interrupting boundary event

Placed on an activity's boundary.

Is automatically created as an interrupting event; can be manually set to non-interrupting

Note

You can normally leave the Innovator determines Type property set. This enables Innovator to adapt the event type if this is required due to further modeling. This does not influence being about to manually change the type.

How to proceed

  1. Select the event.

  2. Select the event type you want from the drop-down list in Properties and confirm with [Enter] or [Tab].

    The type is set and the icon is shown in the diagram accordingly.

Changing an Event into a Boundary Event

Prerequisites

  • The event you want to change has no incoming sequence flow.
  • The event can have any type. The Innovator determines Type property is activated.
  • The assigned event definition cannot have the Cancel or Terminate type.

How to proceed

  1. Select the event you want to change.

  2. Drag the event with the left mouse button to the boundary of the task/activity you want.

    Task/activity is highlighted.

  3. Release the left mouse button.

    The event is linked with the task/activity and shown as a boundary event.

Changing an Event into a Subprocess Start Event

Prerequisites

  • The event you want to change has no linked sequence flows.
  • The event can have any type. The Innovator determines Type property is activated.
  • The assigned event definition cannot have the Cancel or Terminate type.
  • The subprocess has the is triggered by an event property set.

How to proceed

  1. Select the event you want to change.

  2. Drag the event into the subprocess with the left mouse button pressed.

    The subprocess is highlighted.

  3. Release the left mouse button.

    The event is inserted in the subprocess.

  4. If necessary, change the event's type to start event or continue modeling from the event so that it is automatically changed into a start event.

Changing an Interrupting Event into a Non-Interrupting Event or Vice Versa

Prerequisites

  • The event you want to change is a boundary event or a subprocess start event.
  • The assigned event definition cannot have the Error or Compensation type (these are always interrupting).

How to proceed

  1. Select the event you want to change.

  2. Deactivate or activate the check box for the is interrupting property in Properties.

    The event is shown as non-interrupting or interrupting, depending on whether you checked or unchecked the box.