| Both sides previous revision Previous revision Next revision | Previous revision |
| en:rule:business_exception_error [2024-01-11 23:59] – [Error event depicts business exceptions] Anatoly Belaychuk | en:rule:business_exception_error [2024-08-24 15:50] (current) – [Error event may be used to model business exceptions] Anatoly Belaychuk |
|---|
| ====== Error event depicts business exceptions ====== | ====== Error event may be used to model business exceptions ====== |
| |
| {{tag>event event_error attached_event end_event subprocess}} | {{tag>event error_event attached_event end_event subprocess}} |
| |
| End the normal (or deisrable) end of a process by the none event and the business exception (or unwanted end) by the error event. Use the attached event at the above level of the model. | End the normal (or deisrable) end of a process by the none event and the business exception (or unwanted end) by the error event. Use the attached event at the above level of the model. |
| ===== Notes ===== | ===== Notes ===== |
| |
| - Technically, attached event can be omitted - in this case error event would stop the current subprocess, the subprocesses above and the top-level process. Yet if modelled this way, the significant aspects of the process behavior would be hidden so the good practice is to always depict the attached error event. | * Technically, attached event can be omitted - in this case error event would stop the current subprocess, the subprocesses above and the top-level process. Yet if modelled this way, the significant aspects of the process behavior would be hidden so the good practice is to always depict the attached error event. |
| - If the attached event is named then it'd catch only the end error event with the same name. This way each end event can be processed separately. If the attached event is unnamed it'd catch all end error events. | * If the attached event is named then it'd catch only the end error event with the same name. This way each end event can be processed separately. If the attached event is unnamed it'd catch all end error events. |
| ===== See also ===== | ===== See also ===== |
| |
| Использование события-ошибки - альтернатива более простой технике [[ru:rule:check_subprocess_results | проверки результата на выходе из подпроцесса]]. К плюсу этого способа можно отнести то, что диаграмма получается более компактной, к минусу - то, что в палитру добавляется еще один элемент. | * Error event is the alternative to more simple technique of [[en:rule:check_subprocess_results | checking the suprocess results on exit]]. It's advantage is more compact diagram. |
| ===== Author(s) ===== | ===== Author(s) ===== |
| |
| --- //[[user:bell|Anatoly Belaychuk]] 2024-01-11 23:30// | --- //[[user:bell|Anatoly Belaychuk]] 2024-01-11 23:30// |
