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. Currently, the cross-version compatibility checking mechanism tracks feature usages of 2024x Refresh 1 and later Refresh versions that result in triggering Missing features detected notification in earlier 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 |
|---|---|---|
| Security Connectivity (Operational) Table | 2024x Refresh1 | Yes |
| Security Role-based Connectivity (Operational) Table | 2024x Refresh1 | Yes |
| Conjugated Operational, Service, Resource, and Resource Service Interfaces | 2024x Refresh1 | Yes |
| 2024x Refresh1 | Yes | |
| 2024x Refresh1 | Yes | |
| Context column to show the context of the element realizing the exchange in Role-based connectivity tables | 2024x Refresh1 | Yes |
Strategic Actual Strategic Phase Taxonomy Table changes:
| 2024x Refresh2 | Yes |
| When the scope is set in the relation map, the owner of the created elements will now be the same as the diagram owner. | 2024x Refresh2 | Yes |
Important
Features required, but missing, in an earlier tool version (for example, 2024x) are memorized by the cross-version compatibility checking mechanism. This process will continue with each Refresh release (i.e., Refresh 2 might have features that are missing in both Refresh 1 and 2024x).