You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Once you have modeled your business process on the diagram pane, you can add execution parts to this process to bring it to life. The execution pane is the place where you make your model executable.

You need to perform two steps to implement executional parts to your model:

  1. Provide all necessary data types and operations for the implementation of your process. These types and operations reside in the Service panel of the BPMN editor.
    • You can use the Base Types that are provided with the Designer.
    • You can create other necessary types yourself in the Implementation section.
      Refer to Modeling Data Mapping for further information.
    • You can import a library that provides additional types and operations.
      Refer to Designer Administration > Libraries for further information.
  2. In the second step, select data types and operations from the Service panel, and add them to your process at the right places.
    • How this is done will be explained in this chapter.

The Execution Pane

The execution pane is displayed below the diagram pane. It is shown as soon as you click on one of the BPMN elements:

Execution Pane Contents

The content of the execution pane depends on the BPMN element. For some elements the execution model must be created manually when you want to add execution:

INITIAL Execution Pane ViewPane ContentBPMN Elements

  1. Add Execution Model Button

  1. Add Execution Model Button - disabled

For the following elements you cannot create execution models:

Execution Pane View With Execution Model ADDEDPane ContentBPMN Elements

  1. Operations Flow
  2. Persisted
  3. On Event Tab
  4. Local

  1. Operations Flow
  2. Persisted
  3. On Exit Tab
  4. Local

For some elements the content is already added during initial creation:

INITIAL Execution Pane ViewsPane ContentBPMN Elements

  1. Operations Flow
  2. Message
  3. Persisted
  4. On Event Tab
  5. Local




  1. Operations Flow
  2. Message
  3. Persisted
  4. On Exit Tab
  5. Local

  1. Operations Flow
  2. Persisted
  3. On Exit Tab
  4. Local

  1. Operations Flow
  2. Persisted (Read Only)
  3. Decision Tab
  4. Return
  5. Local

Initially, a user task is created with execution model On Exit but you can add execution model Get Data manually:

Execution Pane View for GET DATAPane ContentBPMN Elements

  1. Operations Flow
  2. Persisted (Read Only)
  3. Get Data Tab
  4. Return
  5. Local

Section

Description

Operations Flow

Every execution pane contains an empty operations flow with start and end node.

Persisted

Variables created in section Persisted are usable in all executions of the BPMN model.

Local

Variables created in section Local are only available for use within the current execution.

MessageSection Message is shown for all BPMN elements that need to process an incoming message. As per default, the incoming message has type any . To gain access to the data used in your process, you have to apply the correct type from a customized library.
ReturnFor outgoing relations of Exclusive Gateways Section Return is displayed, containing the unchangeable variable return of type boolean.
Section Return is also displayed in the Get Data tab of User Tasks, containing the variable return of type any. If a form is assigned to the user task, variable return is of the form's type.
Execution Tabs

You can add and delete the execution model of a BPMN element. For each execution model a corresponding tab is displayed at the bottom of the execution pane. The tab name indicates the time of the execution. Possible tabs are:

  • On Event: The model is executed when the event occurs.
  • On Exit: The model is executed after completion of the task/event.
  • Decision: The model is executed when the process reached the gateway.
  • Get Data: The model is executed when BPMN is waiting in a user task and returns the default values for the form.

On this Page:
Related Pages:

  • No labels