Skip to main content

We are trying to group tasks together so that they can act functionally as one. For example, we might have the tasks "Frame", "Mechanical", and "Paint". We ideally, the process should be conforming if the case flows through any or all of those tasks, and in any order. So if the activity just went through "Frame", or if it went "Mechanical" to "Frame", or from "Frame" to "Mechanical" to "Paint", all should be conforming.

 

In regard to the screenshot, we are getting violations because "04 Paint" is followed by "04 QA Post-Paint".

 

We have tried grouping them in a subprocess, and we have also tried tried grouping them as a series of tasks in parallel connected by parallel gateways. Neither seems to work. Is there a better method for grouping tasks inside of the process model?

 

 

Hello John-Robert Kocian,

thank you for reaching out.

Please be informed that grouping (using groups in BPMN) is the right way from a conceptual point of view. However, n:m (or here 1:n) mappings are not supported, thus, they are not considered in the conformance check.
Should you have any questions, feel free to let us know.

Best Regards,
Blenda
Hello John-Robert Kocian,

thank you for reaching out.

Please be informed that grouping (using groups in BPMN) is the right way from a conceptual point of view. However, n:m (or here 1:n) mappings are not supported, thus, they are not considered in the conformance check.
Should you have any questions, feel free to let us know.

Best Regards,
Blenda

Are there any workarounds that would allow us to proceed in the manner described?

 

Additionally, we have another decision point that should allow ROs to either continue on in the process, or loop back to the start of the process. Since this can also go from one task to one of two additional tasks, is this also not possible?

 

Attached is an image with the two possible paths highlighted in red.Looping Example


Reply