Renaming an instance

You can rename a selected instance while you can see the impact of its renaming. The new name is automatically propagated to all the design files where the instance is used. For Data Elements, Segments, Data Structures, or Macros, the new name is also propagated to all its usages in the Macro code or the specific code of Programs, Screens, and client/server entities. Besides, for Segments, Data Structures, and Macros, the new name is also propagated to the metadata files of the generated Programs, Screens, and client-server entities.

About this task

You must use the renaming feature on a complete workspace and check that the renaming is consistent. Renaming instances in the local workspace must not cause any inconsistencies in the stream on the server.

It is recommended to create a snapshot or a baseline of the components in Rational Team Concert™ before you rename.

Procedure

  1. Right-click an instance in the Design Explorer view and select Refactor > Rename.
  2. Enter the new name in the wizard that opens.
    Notes:

    In the Pacbase facet, the first two characters of a Segment cannot be renamed if the Segment is used. It prevents inconsistencies.

    When a Data Structure is renamed, the Segments that belong to the same project are also renamed. You must then rename the Data Structure in each project where it is duplicated.

  3. You can start the renaming directly or you can choose to see its impacts first.
    • Click Finish to start the renaming without seeing its impacts.
    • Click Next to see the impact of the renaming. The following two tabs are then displayed:
      • The Renames tab lists all the design files that will be renamed. For example, in the Pacbase facet, it lists all the Segments that will be renamed after the renaming of a Data Structure in the same project.
      • The Changes tab lists all the files that will be impacted by the renaming. It lists all the design files where the instance is called in the lower hierarchy of the projects in the design build path.
      Click Finish to start the renaming.

Results

To ensure the consistency, the instance is renamed in all the impacted design files. These files are the instances whose names are based on this instance name (Segments of a renamed Data Structure for example) or the instances that call the renamed instance in their design.

Moreover, if the renamed instance is a Data Element, Segment, Data Structure, or Macro that is called in the code of a Macro or in the specific code of a Program, Screen, or client/server entity, it is also renamed in these usages. The impacted Programs, Screens, and client/server entities are marked to be regenerated in the Generation Manager view but are not automatically regenerated after the view is refreshed.


Feedback