ELEMENT |
CONSIDERATIONS |
PROPERTIES |
|---|---|---|
End Event |
•The End Event has no outgoing transitions. •The End Event verifies whether there are any pending Activities (tokens) for each case. If there are no Activities pending, the Process is closed automatically. •The typical use of this shape takes place in business situations in which there are parallel paths and, on one of them there are no more Activities to be carried out, but the Process does not have to be closed altogether. •This element cannot be synchronized with another point of the Process. •The Terminate End Event is an optional shape in diagramming the Process. However, it is advisable to use it in the diagram. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Message End |
•Message End is always a throw shape. That is, to use a Message End, there has to be an Intermediate Message Event, or Start Message that catches the message. •The Message End should be configured to identify the target Process and the target Element. •The shape that catches the message and the Message End should have the exact same name. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Error End |
Indicates that a named Error should be generated. All currently active threads of the Process are terminated. The Error will be caught by a Catch Error Intermediate Event. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Cancel End |
Is used within a Transaction Sub-Process. It indicates that the Transaction should be canceled, and an alternative flow can be performed. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Signal End |
•Signal End is always a throw shape. That is, to use a Signal End, there has to be a Signal Event that catches the message. •A signal is sent to any Process that can receive it, but it does not have a specific source and target. Any catch shape with the same name will be triggered. •The shape that catches the signal and the Signal End should have the exact same name. •The Message End should be configured to identify the target Process and the target Element. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Terminate End |
•When Terminate End is reached in a Process, the Case is closed even if there are pending activities. •The Terminate End event is an optional shape in diagramming the Process. However, it is advisable to use it in the diagram. |
Basic Properties •Display Name: This is the display name of the Event that is shown in the Work Portal. •Name: This is the name of the Event in database. •Description: Displays additional information for the Event. |
Examples
Below there are some scenarios in which you can see End events behavior. The events that are not the terminate end event (e.g Message, Signal, Error, Cancel) only end the path they are following. The case continues until all tokens (active paths) are closed.
End Events different from terminate
Since this type of events do not end the current case, the case stops until Task 4 finishes, closing all active paths. See this example below:
Using the Terminate End Event
In the next example, there are several End events on this process, However, if one case reaches the Terminate End event is, for example after executing Task 5, the case is finished. Other elements of the case are also closed.
Using Sub-processes
It is important to consider that Terminate End events only end the current process flow. When the subprocess' case reaches the Terminate End event, the only case that ends is the case associated with the subprocess. The case related to the parent process is not affected, and thus, does not end. Please, see this example below:
In this example, you can observe that although the Notification sent to supervisor case, which is associated with the subprocess, is ended by the Terminate End event, the Notification sent to HR case is executed regardless of the outcome of the Notification sent to supervisor case.
•In this second example, the case related to the parent process has two cases associated with subprocesses, both cases have Terminate End events. Please, see the example below:
In this previous example we have a case for a Sales call, this case has two other cases related to subprocesses. Although these cases end by the Terminate End event, the parent case related to the process continues its process flow.
Last Updated 3/5/2024 4:12:51 PM