Closed philip-alldredge closed 3 years ago
My understanding based on the standard documentation is that although a classifier may have multiple EMV2 annex sub clauses each with "in modes" statement, they do not impact the EMV2 model elements that this issue covers. The general approach is to treat the model as if the model elements are in the same subclause.
Support for dependent objects will not be added to the graphical editor. Additional design and consideration is needed to determine whether that is really the best way to solve the issue of connection endpoints being missing from the diagram. Automatically adding endpoints for some or all connections would not be consistent with the current behavior and could result in automatic changes to serialized diagrams. There are cases where a user may want to avoid adding such diagram elements. Lastly, it would be a significant change to the diagram update process with a potential performance impact. If/when the problem is solved, it may be better to include it as part of a refinement or rework of the content filter system.
@lwrage given how close we are to the next planned release, we have removed the part about promoting the EMV2 support out of experimental from this issue. This will give us more time to ensure things are reliable. We've moved the latter part to #2450.
Copying and pasting will not be supported for error model elements at this time. How they are represented is not compatible with the current copying and pasting implementation a new issue will be added to the backlog.
This issue has been revised multiple times to more accurately describe the changes being made
References
Examples