To handle cases The cross-version compatibility checking mechanism is implemented when a project with new feature usage usages is loaded with an older version of the modeling tool(that does not have exactly the same feature) the cross-version compatibility checking mechanism was implemented. The essence of this mechanism is to track whenever an opened project is attempted to be saved/committed . When you attempt to save or commit an opened project with a tool version that has is missing features. In such cases, a message is shown that warns of possible consequences, this mechanism will track the missing features and show a warning message indicating possible consequences if you proceed.
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 mechanismand this . This process will follow 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 for the following feature usages of 19.0 SP1 that results 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. Beside this, user is Additionally, you will be warned of possible consequences if such diagram will be editedyou edit the diagram:
This mechanism prevents from unexpected changes after opening such a project with version 19.0 SP1version.
