PK58990: large activity diagrams display incorrect migrate from 6 to 7.0.0.5

Rational Systems Developer, Version 7.0.5.1
Rational Software Modeler, Version 7.0.5.1
Rational Application Developer for WebSphere Software, Version 7.0.0.6
Rational Software Architect, Version 7.0.0.6

APAR status

• Closed as program error.

Error description

• In Rational Software Architect 7.0.0.5 and 7.0.0.4 when importin
  g in large activity / sequence diagrams from the RSA 6 release t
  hey import incorrectly and squished.
  

Local fix

Problem summary

• The problem consists of 2 parts:
  a. Some labels are not placed at the same location they were
  in version 6.x (on connections, and on some nodes: activity
       edges, transitions, and nodes with views with type
  NameLabel)
      The label position is shifted to the left by half the
  value of the size of the label (the bigger the label, the
  bigger the shift)
  b. Decision nodes always display their name inside of the
  node, which is different from 6.x behavior and
       changes the diagram look specially if the name is long
  (the decision node will be very big)
  

Problem conclusion

• Fixed.
  The solution from problem a. Label position shifting
  * When the user migrates a model from 6.x, the Alerts and
  Actions section of the model editor will display a warning
    informing the user that this model has been migrated from
  6.x and could potentially have differences in label
  locations.
    The user will be given the option to click a button to
  correct the problems in the model. Clicking this button will
  open the
     diagrams in the model, one by one, (the user would have
  been informed of this operation, and asked to confirm or
  cancel
     it), and detect which views need their label position to
  be updated, then shift that label by half its size to the
  right so when it
     shifted by the code post 6.x to the left by half its
  size, this would not be an extra shift from the position it
  should be in. The problem
     is that the assumption in 6.x was that the position
  stored in the file indicated the position of the top left of
  the label, however, after
     6.x, the assumption was that that position indicates the
  position of the center of the label, so placing the label at
  that position
     also required a shift to the left by half the size of the
  label so the center of the label can be at that position.
     We detect labels for particular view types and make the
  adjustment (shifting to the right).
  
  The solution for problem b. Decision node labels display
  inside the node
  * The DecisionNodeEditPart always placed the label inside
  the node. However, nodes in 6.x had a view that contained
  the
     name and the stereotype of the node and that view was
  displayed as a floating label. In later versions, that view
  was ignored
     and labels were placed inside a decision node.
     The solution was to check for UMLLabelEditPart and insert
  its figure in the border item figure container, this will
  allow the label
     to be displayed as floating. So models coming from 6.x
  will display floating labels.
     We added a preference to 7.0.0.6 and later versions for
  the user to choose the decision node label style (in shape
  vs floating).
     We also added a menu group for the user to switch between
  one style and the other.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SW ARCHITECT WI

• Fixed component ID

  5724I7001

Applicable component levels

• R700 PSN

     UP