The cross-version compatibility checking mechanism is triggered when a project with new feature usages is loaded with an older version of the modeling tool. The mechanism tracks feature usages of 19.0 SP1,19.0 SP2, and 19.0 SP3 versions that result in the appearance of a Missing features detected notification in earlier modeling tool versions. The following table shows tracked features, the version they appear in, and whether the project can be committed/saved without any consequences.
| Feature name | Version | Secure to commit/save |
|---|---|---|
| 19.0 SP1 | No | |
| 19.0 SP1 | No | |
| 19.0 SP1 | No | |
| 19.0 SP2 | Yes | |
| Contextual relationships in the dependency matrix | 19.0 SP3 | Yes |
| Displaying classifiers on internal structure and behavior diagrams | 19.0 SP3 | Yes |
| Custom hierarchy in tables | 19.0 SP3 | Yes |
| Lock-free Model Editing | 19.0 SP3 | No |
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).
If you are working with features that can cause inconsistencies after save/commit (see the table above), the cross-version compatibility checking mechanism will track the missing features and show a warning message indicating possible consequences if you proceed.
Diagramming features
Forward compatibility tracks the following diagramming features introduced in 19.0 SP1:
When opening a project with a tool version 19.0 (or 19.0 SP1 when the project was created with 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 a version 19.0 SP1.