Managing Model Objects › Working with Versions of Functions and Messages › Cautions

Cautions

When you make a version current, all objects that use the previously-current version are affected. Use this feature with care to prevent unexpected results. The following are some points to consider:

• You can determine the impact of making a new version current in advance using CA 2E's impact analysis tools to view the level 001 usages for the existing current version. For example, use selection option 95 on the Display Model Usages panel to simulate a public change.
• If some of the using objects require the original functionality (in other words, if they need to continue using the existing current version), you cannot introduce your changes by making the new version current. Instead:
  1. Copy the new version to create a new model object, not a version.
  2. Edit the action diagrams of the using objects that require the new functionality to see the new copy.
• To implement and test an internal function or message it must be used by an external function. In other words, it must be made current. Before you make it current, be sure to advise other developers so that your changes to the internal object are not inadvertently incorporated into a change to an application program.