Compatibility between different versions of IBM Rhapsody

Answer

Although this is technically possible, it is not a recommended workflow and can lead to problems with the model if the users are not extremely careful. Therefore, users , when designing a model, should be working with the same product version to ensure that they have the same tool and mode behavior.

Let's further the explanation with an example of users having Rhapsody version 8.1.1 and another user having Rhapsody 8.2.0.

In terms of upgrading, you will need to open the 8.1.1 model in Rhapsody 8.2 and perform a save. After you perform a save in Rhapsody 8.2, the model is saved in a Rhapsody 8.2 format. There should be no differences in the behavior of the upgraded model; unless specifically specified by development. When saved, you will no longer to be able to open this model in an earlier version of Rhapsody.

To share a model between Rhapsody version 8.2 and Rhapsody version 8.1.1 would be a two-step process.
Models that are in Rhapsody 8.2 can be saved to earlier versions; specifically, 8.1.5 and 8.1.3. This is done by selecting "File -> Save as..." and then selecting the Rhapsody version to save a copy of the model to.

Once you select "File -> Save as..." you then need to select the "Save as type" and choose the version to save it to.

A possible consequence of saving a model to an earlier version is that any new feature that was added to Rhapsody version 8.2 might not be available when you save it to an earlier version. So, if we created a new chart type or element type in Rhapsody version 8.2, those elements will not be available when you save the model backwards.

And again, if you are looking to get to Rhapsody version 8.1.1 you must then open the Rhapsody 8.1.3 model you just created and perform the "File -> Save as..." actions again to save the model as version 8.1.1.

Here you can see the problems and amount of work that would be introduced if you try to model with differing versions of Rhapsody.