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.
Image Added
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 that result in triggering notifications in the 19.0 version:
Excerpt Include
MD190SP3:Forward compatibility
MD190SP3:Forward compatibility
nopanel
true
Image Added
Diagramming features
Forward compatibility tracks the following diagramming features introduced in 19.0 SP1:
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 Added
This mechanism prevents unexpected changes after opening a project with version 19.0 SP1.
Status
colour
Green
title
Available from 19.0 SP1
As from modeling tool version 19.0 with service pack releases we introduce new features, the forward compatibility are required for tool compatibility with a later version of itself in the future. The forward compatibility allows to ensure that project data would not be lost when opened with a different tool version.
Note
If a user wants to edit diagram, we highly recommend to do it with a version in which feature is supported. Otherwise, the possible data loss when opened with a newer tool version.
Forward compatibility allows to maintain the same diagram view after saving a project with previous modeling tool versions. This implies that user can work on the same project with different versions only if a modeling tool unsupported features are used. For this, the diagrams are made read-only after opening with the previous version of modeling tool if a view is not supported. This mechanism is used for the following features:
After opening the project, which is saved in 19.0 SP1 or newer, using 19.0 version of modeling tool, the diagram shall be made read-only if at least one of the following statements are true:
If at least one symbol shown on diagram has Suspend Auto Resizing of Shape symbolproperty value set to true;
If at least one symbol shown on diagram has Suspend Auto Displaying of Label symbol property value set to true;
If diagram symbol properties Suspend Auto Resizing of Shapes or Suspend Auto Displaying of Labels value is set to true.
Diagrams where vertical labels are used: If a user wants to edit this diagram, we highly recommend to do it with a version in which feature is supported. Otherwise, the possible data loss when opened with a newer tool version.
To handle cases when a project with new feature usage is loaded with older version of the modeling tool the cross-version compatibility was implemented. Before project commit/save, the message can be shown about possible data loss or project inconsistency when opened with a newer tool version. These question messages were added in the 19.0 SP1. So, the user will see these messages only by using a later version than the 19.0 SP1.
This cross-version compatibility is implemented for the following features:
