/
Setting Up Rejections

Setting Up Rejections

Rejections are mapped via Gateways. The type of gateway (parallel, exclusive) is not important. On both, the Repeat Gateway option can be activated and linked to conditions. Gateways (and gates) have the special feature that they have a defined beginning and a defined end, and the elements they contain are subordinate in the hierarchy.

Drag'n'Drop is ideal for moving any objects, but this is only supported by the Object Overview. Since the object overview can only display hierarchies in a simplified form, only the initial objects are displayed.

When a new gateway is inserted, a start and end are created directly. The start is directly connected to the end. It is not possible to create a gateway and define the position of the start and end separately. If a gateway is created subsequently, it is always necessary to move other objects accordingly.

During process design, the process is often built sequentially until a point is reached where the process jumps back. There are two ways to create a rejection:

  • A new gateway is created where the return jump is to take place. In this case, both the beginning and the end of the gateway are located after the object where the return jump is to take place. The gateway start must therefore be moved.

  • A new gateway is created where the return jump is to take place. In this case, both the beginning and the end of the gateway are located before the object where the return jump is to take place. The end of the gateway must therefore be moved.

Since it is not possible to move the start and end of the gateway independently, the only solution is to move the other objects. From a purely visual point of view, this is easier to achieve with the latter variant, since the beginning is already placed correctly and the sequence of all objects is still correct and understandable at all times when the subsequent objects are moved individually.

The procedure is shown in the following example process.-

The goal is a rejection after phase 3 before phase 2 as shown below.

To achieve this, a gate way is first created at the point where the return jump should land, i.e. between phase 1 and phase 2.

Now the gateway end must be placed behind phase 3. Since this is not possible directly, in the reverse case phase 2 and phase 3 must be placed before the end (and thus in the only gate). Since this is not possible in the process graphic, this must be done in the object overview. -

It is recommended to move the objects in sequential order, i.e. first phase 2 and then phase 3. After moving phase 2 into the gate, the following state presents itself.

-

By shifting phase 3, the goal has been achieved.

-



© ProNovia AG | Imprint | Data Protection