Note these restrictions for the match by element ID function
in the product.
- IBM® Rational® Rhapsody® DiffMerge will
neither detect renamed nor suppressed propagated renamed differences
when the renamed object is out of the comparison scope. (For information
about suppressing propagated renamed differences, see Examining only major structure differences.)
For example:
- When comparing sequence diagrams, the base classes
for a classifier role are displayed as "single" nodes though it is
the same class with modified name, but this class is not within this
comparison, as shown in the following figure:
- When comparing packages, a class stereotype difference
is not suppressed though it is the same stereotype having different
names. This situation might be because the stereotype belongs to a
package named, for example, Terms, that is out of the scope of this
comparison.
- When doing a merge of units containing renamed
elements, in some cases, Rational Rhapsody DiffMerge does
not properly update merged attributes values. This situation happens
with the following attributes:
- DependsOn in generalizations and
dependencies when the related class is renamed.
- Stereotype in all model elements
when the stereotype is renamed.
- Type when the type is renamed,
and in all model elements when type is applicable, including: methods
and operation return types; arguments, variables, and attributes types;
template instance parameter types, and basic types of a typedef type.