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. The cross-version compatibility checking The mechanism tracks feature usages of 19.0 SP2and , 19.0 SP3, and later service pack (SP) versions that trigger 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.
Features required, but missing, in an earlier tool version (for example 19.0 SP1) 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 are mentioned in the table above with status that it can cause inconsistencies after save/commit , this mechanism will track the missing features and show a (see the table above), the following warning message indicating possible consequences if you proceed . 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 Removedwill 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.
