PI77324: POPULATING A FLOWCHART FROM AN OPERATION HAS STATE CHART ELEMENTS INSTEAD OF FLOW CHART ELEMENTS.

IBM Rational Rhapsody 8.2.1

APAR status

• Closed as program error.

Error description

• Using Rhapsody in C 8.1.4 It is observed that when populating a
  Flowchart for an operation, the generated diagram looks like a
  flow chart but has in fact state chart elements.
  
  Instead of control flows, transitions are generated.
  Instead of merge nodes, connectors are generated.
  Instead of decision nodes,  conditions are generated.
  
  Therefore in some cases the diagram can not be modified.
  Specifically the "Populate flowchart" feature is not adding the
  correctly stereotyped elements to the flowchart it is creating.
  
  Steps to reproduce:
  In the attached model, there is a class with 2 operations; one
  called CanBeChanged() and one called CanNotBeChanged().
  
  In the flowchart of CanNotBeChanged(), added a comment showing
  what I would like to change. I can not connect the action with
  the connector, Rhapsody says that this is no legal.
  
  In the CanBechanged i marked in green the new elements i added
  and a red line marks the original activity flow. Both diagrams
  where generated from the code in the implementation of the
  operations.
  
  In the flow chart of CanBeChanged, when selecting Activity Flow,
  what is actually drawn is a Transition (from state chart) but in
  the flow chart of CanNotBeChanged Activity flows are drawn.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Rhapsody                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 1. flowchart create by  populating a Flowchart use the wrong *
  * ( state chart) elements:                                     *
  * Instead of merge nodes, connectors are generated.            *
  * Instead of decision nodes,  conditions are generated.        *
  * Instead of activity finals, termination state are generated. *
  *                                                              *
  * 2. it is not possible to add flow between some elements  in  *
  * flowchart                                                    *
  * like from  merge node to decision node                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• problem fixed
  

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

  TLOGIC RHAPSODY

• Fixed component ID

  5724V74RP

Applicable component levels

• R814 PSN

     UP