MM
Hi All,
during my process design I got lost in the use of Gateways.
My subprocess starts to analyze the input documents from ,"planning R". Here I have 2 ways to go. So I used an event based gateway to decide the condition for each path.
1st path doesn't require additional planning and directly finalize the document incl. cost calculation.
2nd path will point to "planning C". After "planning C" is finished, it comes back into my sub process, validate the doc and based on the result I have 2 possible paths to follow
a) its final and leaves the process
b) it requires a change in "planning R" and loops back into the process "planning R"
The problem I have now, how can I still forward the outcome of my initial "planning R" to the point where it connects with "planning C", in cse there is no additional loop from "planning C" to "planning R" required?.jpg)
Hello Mr. Matthäi,
my 2 cents on this:
At the point in question you should be fine. Since your case is, that Planning C did not change anything, why should the result of Planning R be that Planning C is required (again). They should have documented their comment of not changing anything in the first round. So no gateway or decision is necessary at that point.
I suspect you are thinking in terms of department instead of process: Is Planning R really repeated all over after Planning C has added their requirements? Rather add a step "Adjust for results of Planning C" in the lane of the guys doing Planning R. Then you avoid the loop altogether and you are sure your process will eventually finish.
Omit the steps "Request something". It should be obvious from the process flow whose turn it is to do something next. This could be appropriate if you had a collaboration and Send Message tasks with message flows to some other process.
Style: You probably do not need all the events you drew. BPMN is not EPC. Draw only really relevant events. Decision results at gateways are documented as Condition Expresion on the outgoing connection of the gateway.
