Known issues

Edit online

Review the issues with workarounds and limitations at the time of 7.0.3 release. For updates on these issues, see interim fix readme file documents or IBM® Engineering Lifecycle Management documentation.

Table 1. Workarounds
Defect ID	Description
80389	Simplified linking (drag or copy and paste) from Rhapsody® Model Manager to DOORS® Next is not supported when the Rhapsody Model Manager Project Area is configured with a source control management(SCM) Deliver precondition that requires all change sets to be associated with a work item First occurrence: 7.0.3 Problem: Simplified linking (drag or copy and paste) from Rhapsody Model Manager to DOORS Next is not supported when the Rhapsody Model Manager Project Area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item. Workaround: If this precondition is set, use simplified linking (drag or copy and paste) from DOORS Next to Rhapsody Model Manager, or use the legacy actions of creating the OSLC link from within Rhapsody Model Manager. In these workarounds, the Create Link dialog offers the ability to select a work item, which is required if the Rhapsody Model Manager Project Area is configured with an SCM Deliver precondition that requires all change sets to be associated with a work item.
63897	The v server and client require a locale setting for non-English support First occurrence: 6.0.6 Problem: Rhapsody elements for non-English labels display incorrectly in the Rhapsody Model Manager web interface, unless the correct locale is set on the client machine. Workaround: Manually set the locale on the client machine.
80459	When you are upgrading to RMM7.0.3, rebuild the full-text search indexes to search for architecture elements First occurrence: 7.0.3 Problem: In Rhapsody Model Manager 7.0.3, the user is allowed to search for architecture elements in the OSLC link creation dialog and the quick search menu. If you are upgrading to Rhapsody Model Manager 7.0.3, the full-text search indexes must be rebuilt so that the search results include the architecture elements that were created before Rhapsody Model Manager 7.0.3. Workaround: To rebuild the full-text search indexes after you upgrade to Rhapsody Model Manager 7.0.3, run the repotools-ccm -rebuildTextIndices command before starting the server. The reindexing might be a lengthy process and can take many hours for a large database. If an application is clustered, the reindexing procedure (by using repotools) must be performed on each node in the cluster. For more information, see Searching for model elements.
72564	Tables and matrix views in Rhapsody Model Manager do not display out-of-sync indications First occurrence: 7.0 Problem: Unlike diagram views, table and matrix views in Rhapsody Model Manager do not include out-of-sync indications. Workaround: To ensure that the information displayed accurately represents the current model data, follow the instructions in this document.
64640	The Associate Change Request action in Rhapsody requires a repository connection First occurrence: 6.0.6 Problem: If you want to associate a change request with a Rhapsody Model Manager change set that is in the Rhapsody client, you must already have defined a Change and Configuration Management (CCM) repository connection in the Engineering Workflow Management Eclipse client. Otherwise, you get the following error: Error while associating a work item to a change-set containing files: L:\Demo Sandbox\Model\Model_rpy; Pkg.sbsx Failed to associate work-item https://server:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/10 to change-set Repository connection was not found for work item that is identified by the following URL: https://server:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/10 Workaround: You need to create a new repository connection from the Engineering Workflow Management Eclipse client to the server that manages the work items: Open the Engineering Workflow Management Eclipse client. Create a new Jazz Repository Connection. Specify the URI path to https://<;`server`>:<`port`>/ccm/
64658	The Create Streams action for global configurations does not work for Rhapsody Model Manager snapshots First occurrence: 6.0.5 Problem: If you include a Rhapsody Model Manager snapshot in a global configuration and you run the Create Streams operation from the Rhapsody Model Manager snapshot, you might get the following error message: CM provider does not support stream creation. Workaround: Manually remove the old stream and add the new stream.
62565	The file path for the Rhapsody client on Windows is limited to 256 characters First occurrence: 6.0.5 Problem: It's not possible to open and save a Rhapsody model to a path that is longer than 256 characters. Workaround: Use a short path to the EWM sandbox folder to avoid reaching 256 characters.
62581	You cannot associate a change request when you delete an OSLC link from DOORS Next or DOORS First occurrence: 6.0.5 Problem: When you create an OSLC link from DOORS Next or DOORS to Rhapsody Model Manager, you can associate a change request to track corresponding modifications. However, when you try to delete an existing OSLC link from DOORS Next or DOORS, you don't have this ability. This happens because these applications do not provide a dialog box where you can select a change request. If the Require Work Items and Comments precondition is selected on the server side for a project area, deleting the link fails with an error message. Workaround: This workaround is available starting in 6.0.5 interim fix 001: From DOORS Next go to Rhapsody Model Manager by clicking the OSLC link that you want to delete. In Rhapsody Model Manager, delete the existing OSLC link, and then you can select a change request to associate with the change set.

Table 2. Limitations
Defect ID	Description
72593	In Offline mode in Rhapsody, you cannot delete, rename, or move saved units First occurrence: 7.0 Problem: While you can make changes to a model and save the changes in Offline mode in Rhapsody, you cannot delete, rename, or move saved units.
80387	The following limitations exist when you are generating reports for Rhapsody Model Manager in Report Builder First occurrence: 7.0.3 Problems: Link validity data that is entered for Rhapsody Model Manager OSLC links before 7.0.3 is available for reporting in Report Builder. Data that is entered or modified in 7.0.3 is available. The reports in the Report Builder will not include results that contain Rhapsody Model Manager Architecture Elements that are in a component that is owned by a user or a team area that has 'Team Private' visibility. When you are generating reports in Report Builder for architecture elements from a project area that is not enabled for configuration management, ensure that all components in the Default OSLC Context belong to the same project area. This means a component from one project area that is not enabled for configuration management must not be used in another project area. This restriction ensures that each architecture element in the project area that is not enabled for configuration management has only a single version in the report. External links that is, Non-OSLC links or links to arbitrary URLs on Architecture Elements are not available for reporting in Report Builder. Use the Name or Label attribute in Report Builder to extract the Name or Label information instead of the Title attribute.
70107	Link validity status is displayed only in projects that are enabled for configuration management First occurrence: 6.0.6.1 Problem: In Rhapsody Model Manager, link validity status is displayed only in projects that are enabled for full configuration management (for use with global configurations) on the Configuration Management page of application administration.
69865	Rhapsody client for Rhapsody Model Manager does not display link validity information First occurrence: 6.0.5 Problem: In Rhapsody, link validity status is not shown for OSLC links between model elements and artifacts in other applications.
62563	Rhapsody Model Manager can only reference model data on a single server First occurrence: 6.0.5 Problem: You cannot have elements from different servers in the same model, either by reference or as external units.
62556	Rhapsody Model Manager components cannot be owned by specific users First occurrence: 6.0.5 Problem: Any of these three roles can own an Engineering Workflow Management component: Project area Team area User In contrast, Rhapsody Model Manager supports only the first two roles, project or team areas. Specific users cannot own a component.
69165	Rhapsody Model Manager does not integrate with Rhapsody Gateway First occurrence: 6.0.5 Problem: You cannot use Rhapsody Gateway for models that are stored on the Rhapsody Model Manager server. To manage traceability for requirements, use the Remote Artifacts OSLC integration with DOORS.
62561	Rhapsody Model Manager is not supported in a Rhapsody platform integration with Eclipse First occurrence: 6.0.5 Problem: You cannot use the Rhapsody platform integration with Eclipse as a client for the Rhapsody Model Manager server. Use the stand-alone version of Rhapsody that is not integrated with the Eclipse platform.
69167	Rhapsody Model Manager is not supported by Rhapsody in a Citrix environment First occurrence: 6.0.5 Problem: You cannot use Rhapsody Model Manager if Rhapsody is running in a Citrix environment.
62558	Rhapsody Model Manager is not supported by Rhapsody client on a Linux operating system First occurrence: 6.0.5 Problem: You cannot use Rhapsody on a Linux operating system as a client for the Rhapsody Model Manager server. You must use Rhapsody on a Windows operating system as a client for the Rhapsody Model Manager server.
73463	Rhapsody Model Manager does not support export and import of EWM source-control management components First occurrence: 6.0.5 Problem: For Rhapsody Model Manager projects, you cannot use the repository tool commands that are provided by EWM for exporting and importing components.
80388	Role-based permissions cannot be used to customize who can update the 'Link validity' status from within Rhapsody Model Manager First occurrence: 6.0.6.1 Problem: The ability to update link validity status from within Rhapsody Model Manager does not use role-based permissions. All users that have access to the architecture element and OSLC link in the Rhapsody Model Manager web UI can update the link validity status.
61956	Some Engineering Workflow Management (EWM) options must be turned off when you use Rhapsody Model Manager First occurrence: 6.0.5 Problem: When you use Rhapsody Model Manager, you must turn off the following source control options in your Engineering Workflow Management client: Auto-check-in local changes: To locate this option, click Window > Preferences > Team > Java Source Control > Check-in policies. Allow modeling tools (For example, UML) to participate in file content merging during Accept. To locate this option, click Window > Preferences > Team > Java Source Control > Model Enablement.
72592	Tags that are defined for a tag and stereotypes that are applied to a tag are not displayed on the Properties page of the tag in Rhapsody Model Manager First occurrence: 7.0 Problem: While stereotypes applied to an element and tags of an element are displayed on the Properties page of the element in Rhapsody Model Manager, tags defined for a tag and stereotypes applied to a tag are not displayed on the Properties page of the tag.