on 02-16-2015 9:18 AM
The one with the dots won't terminate you subprocess the other one will. Those are so called "critical" and "non critical" boundary events.
Regards,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Tobias. That's understood.
But why appears the same subprocess in two different ways?
Normally I define the boundary event based on the escalation end event, right?
For this subprocess it looks like that:
In my opinion the subprocess should be aleways displayed with the red dots as the "Terminating" checkbox is not ticked. Is that correct?
But why is it not the case for all instances of the subprocess?
Thanks in advance!
Best regards,
Thorsten.
If this is the exact same event form the exact same subprocess, then it looks like a bug to me. I just checked it for one of our WFs and there is every escalation event with dots even if they are terminating. Seems like there is a viewing bug since the WF works as expected. So I do not care so much about that, if you do, you could try open a product error on help.sap.com and see what happens .
Regards,
Tobias
Hi Thorsten,
if it is red than it means there is an error in the model detected, maybe the throwing event not matching the boundary event anymore or a type mismatch.
You should be able to see more details when looking into the problems/error log view or even by hovering over the boundary event.
I would also assume that you can not build this model anymore. My guess is that you modeled the boundary event, then changed the escalation type in the subprocess from non-critical to critical but did not update the boundary event at the catching process.
The dotted vs. solid line differentiates if is a non-critical or critical boundary event (defined by the escalation).
Best regards
Volker
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.