APAR status
Closed as program error.
Error description
When a new Requirement is added into Rhapsody and stereotyped ??fromDOORSxx? then Gateway adds that Requirement into the appro priate DOORS Module. However structure is ignored. The user can create structured requirements in Rhapsody and export them to DOORS. Th en after a sync they find all of their requirements as a flat list in the root package. In order to have them structured they are forced to ope n DOORS and manually recreate the structure there and then resync.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Hierarchy ignored with Rhapsody authored requirements
Problem conclusion
Fixed in 7.6
Temporary fix
Comments
APAR Information
APAR number
PM17389
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
752
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-28
Closed date
2010-12-18
Last modified date
2010-12-18
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
R752 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
18 December 2010