The cross-version compatibility checking mechanism is implemented when a project with new feature usages is loaded with an older version of the modeling tool. When you attempt to save or commit an opened project with a tool version that is missing features, this mechanism will track the missing features and show a warning message indicating possible consequences if you proceed.
Important
Features required, but missing, in an earlier tool version (for example 19.0) are memorized by the cross-version compatibility checking mechanism. This process will continue with each SP release (i.e., SP2 might have features that are missing in both SP1 and 19.0 GA).
Currently, the cross-version compatibility checking mechanism tracks feature usages of 19.0 SP1 and 19.0 SP2 versions that result in triggering a Missing features detected notification in earlier versions. The following table shows tracked features, the version they appear in, and whether the project can be committed/saved without any consequences.
Error rendering macro 'excerpt-include'
No link could be created for 'MD190SP3:Forward compatibility'.
Diagramming features
Forward compatibility tracks the following diagramming features introduced in 19.0 SP1:
When opening a project with tool version 19.0 (or 19.0 SP1 when the project was created with modeling tool 19.0 SP2 version), the usage of these features makes the diagram read-only. Additionally, you will be warned of possible consequences if you edit the diagram:
This mechanism prevents unexpected changes after opening a project with version 19.0 SP1.