Can the semantic checks for BPMN models be configured, to remove rules where we do NOT want to enforce compliance with the BPMN standard?
I am asking because: my process release is being blocked by the Semantic check; which is looking for requirements that contradict our modeling conventions. The contradiction relates to the connection across BPMN models. In our architecture, we use VACD models to define the higher-level end-to-end flow; and we want to represent that complete end-to-end flow in the BPMN models. Since there is no process link object available (for linking/navigating from one BPMN model to the next in the end-to-end flow), we created a "process interface" or process connector symbol/object, similar to that used in EPC models; and we must use an intermediate event after/before the process connectors. In some cases, we do have flows that do begin with a Start Event, and end with an End Event, since there is nothing before or after those steps. But this conflicts with the BPMN Semantic check; which requires that any model with a start event must have an end event; any model with an end event must have a start event. We tried to work around this by using Intermediate events in place of start and/or end events as needed; but the semantic check demands at least one incoming and one outgoing connection on all Intermediate events.
Note, we are not using these models for automation; they are for human beings to read and understand. So we need a modeling convention that is readable and understandable for normal human beings (meaning: NOT ARIS or BPMN experts).
So, we would like to simply remove this rule, so we can release or models; but I am told there is no way to do that.
How can we configure the BPMN semantic check rules, to remove the rules that conflict with our modeling conventions?
thanks in advance!
