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 2022x Refresh1 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 |
|---|---|---|
| 2022x Refresh1 | Yes |
Important
Features required but missing in an earlier tool version (for example, 2022x) are memorized by the cross-version compatibility checking mechanism. This process will continue with each Refresh release (i.e., 2022x Refresh2 might have features that are missing in both 2022x Refresh1 and 2022x).