APAR status
Closed as Permanent restriction.
Error description
In IBM Rational Software Architect (RSA), if you delete a lifeline from a (canonical) sequence diagram, that lifeline's property will not get deleted from the model itself. The following steps reproduce the problem: 1. Create a UML project and model 2. Add two classes 3. Add a sequence diagram 4. Drag the two classes onto the sequence diagram. Take note that two attributes (or properties) are created under the collaboration. 5. Delete one of the lifelines from the sequence diagram, either by pressing the 'DELETE' key or selecting 'Delete from Model' from the context menu 6. Save the changes Expected Result: Because sequence diagrams are canonical, any changes to the diagram should be reflected in the model. The lifeline's corresponding attribute therefore gets deleted from the model. Actual Result: The lifeline's corresponding attribute remains in the model. Workaround: Delete the lifeline's attribute within the Project Explorer.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Multiple attributes can be added under Collaboration in Project Explorer and we can make a lifeline reference an attribute as its represented property.
Problem conclusion
Deleting a lifeline should not delete the attribute as that attribute would have been referred by other lifelines and they will lose the represented property. There is no way to differentiate whether a property was created while creating the lifeline or whether it was created manually by the user in the Project Explorer.
Temporary fix
Comments
APAR Information
APAR number
PI15238
Reported component name
RATL SW ARCHITE
Reported component ID
5725A3000
Reported release
900
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-04
Closed date
2014-06-23
Last modified date
2014-06-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 September 2020