![how to look from an error on bizagi modeler how to look from an error on bizagi modeler](https://images.sftcdn.net/images/t_app-cover-l,f_auto/p/4a36ed3a-9b24-11e6-ba35-00163ec9f5fa/271818000/bizagi-modeler-screenshot.jpg)
![how to look from an error on bizagi modeler how to look from an error on bizagi modeler](https://help.bizagi.com/process-modeler/es/longlasting6.jpg)
The process is terminated when it reaches the ‘terminate’ end event. This is partially true, but the devil is hidden in the detail!įor example, the interpretation of the process presented on Figure 13 is the following: The process first performs Task 1 and then continues in both directions (parallel split), while Task 3 is performed several times on different data sets (Task 3 uses the multiple-instances marker ‘|||’). Modelers commonly over-use ‘terminate’ end events instead of using simple end events, the reason being that they perceive a ‘terminate’ end event as a stronger finish for a process. If a process actually starts by different triggers or ends at different states, the names of the corresponding process events should be unique. A similar situation appears if a modeler does not name multiple start and end events. Since there are actually two different starts of a process and two different end states of the process, the respective events should be named uniquely (as presented in Figure 10), or someone could misinterpret the process model as having only one start event and one end event, which is wrong. However, a detailed analysis of the process semantics shows that the naming of the process’s events is wrong. The process in Figure 9 includes two start and two end events.