The cross-version compatibility checking mechanism is implemented triggered 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.
Image Removed
Note
title
Important
Features required, but missing, in an earlier tool version (in this case 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 the following feature usages of 19.0 SP1 that result in triggering notifications in the 19.0 version:
When opening a project with tool version 19.0, the usage of these features makes the diagram read-only. Additionally, you will be warned of possible consequences if you edit the diagram:
Image Removed
This mechanism prevents unexpected changes after opening a project with version 19.0 SP1
. The mechanism tracks feature usages of 19.0 SP2, 19.0 SP3, and later service pack (SP) 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.
If you are working with features that can cause inconsistencies after save/commit (see the table above), the following warning message indicating possible consequences if you proceed will be shown.
Image Added
Compatibility of profiles
While the tool is backward compatible, we highly recommend for every user working on a particular project to use the same version of the tool. For example, if you use an older version of the tool and open a project created with a later version, a balloon notification pops up:
Image Added
To avoid this:
Make sure that every user working on the same project uses the same version of the tool.
Do not migrate profiles unless every user working on the same project is informed and ready for migration.