Skip to content

Modeler_audit_rules_R1250

Jump to bottom
Antonin Abhervé edited this page Sep 3, 2020 · 1 revision

R1250

Summary

If a ForkJoinNode has an ObjectFlow in its incoming edges, it must have an ObjectFlow in its outgoing edges and vice versa. The same applies for ControlFlows.

Details

UML constraint:

  • The edges coming into and going out of a fork node must be either all ObjectFlows or all ControlFlows.

  • If a join node has an incoming ObjectFlow, it must have an outgoing ObjectFlow, otherwise, it must have an outgoing ControlFlow.

All information entering a ForkJoinNode cannot be lost and all information going out of a ForkJoinNode cannot be created.

Tips

When you get an R1250 warning on a ForkJoinNode, check the consistency of flows going in and out of the ForkJoinNode.

Clone this wiki locally