PI20488: Closing a sub-process BPMN diagram automatically closes the main BPMN diagram

Rational Software Architect 9.1.1
Rational Software Architect for WebSphere Software 9.1.1
Rational Software Architect for WebSphere Software 9.1.2
Rational Software Architect 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 2 (9.1.2.2) for 9.1.2
Rational Software Architect Fix Pack 3 (9.1.2.3) for 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.3) for 9.1.2

APAR status

• Closed as program error.

Error description

• In IBM Rational Software Architect (RSA), after closing a BPMN
  subprocess diagram that was initially opened from a call
  activity on the main diagram, the main diagram also gets closed
  automatically without prompting the user to choose whether to
  keep it open.
  
  The following steps recreate the scenario:
  
  1. Create two BPMN models and make sure the second BPMN model is
  closed
  
  2. Add a call activity to the first model
  
  3. Go to the call activity's Properties ? General ? Called
  Element
  
  4. Browse to the second BPMN model and click OK
  
  5. Save the changes
  
  RESULT: A ' + ' sign appears on the call activity which
  indicates a link to the second model/diagram, as expected
  
  6. Double-click on the call activity
  
  RESULT: The second model (diagram) opens, as expected.
  
  7. Close the second model
  
  RESULT: A 'Close: The following diagrams contain views or
  elements that depend on information from the resource(s) being
  closed: [Name of second model/diagram] The dependent diagrams
  will be closed.' information message appears.
  
  8 Click either OK or the ' X ' button at the top right-hand
  corner of the dialog box
  
  Actual Result: Both models (diagrams) are now closed.
  
  Expected Result: You have the option of returning to the first
  diagram to make changes to the first diagram.
  
  Workaround:
  Open the second model from the Project Explorer, instead of from
  the call activity in the first model/diagram, and make sure to
  never select the call activity in the first model/diagram.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a diagram, on which other diagrams were dependent on,
  was closed, all the dependent diagrams were closed without
  giving user any choice.
  

Problem conclusion

• When a diagram, on which other diagrams were dependent on,
  was closed, all the dependent diagrams were closed without
  giving user any choice. This has been fixed and now users
  will be prompted to choose whether dependent diagrams should
  also be closed or not.
  

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

• R900 PSN

     UP