Find Answers

Filter Search Results
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML RM QC10 SyncEngine did not transfer link form RM to QC10
RM QC10 SyncEngine did not transfer link form RM to QC10
CMS-XML RM QC10 sync Links between Req and Test must transfer without data edit.
RM QC10 sync Links between Req and Test must transfer without data edit.
CMS-XML Link Transfer Rules corrected in baselines and snapshots
Link Transfer Rules corrected in baselines and snapshots
CMS-XML The links on Proposed items are not transferred if the relationship is circular.
The links on Proposed items are not transferred if the relationship is circular.
CMS-XML The link transfer to child fails when an object in a proposed state is linked to an object in the current state
The link transfer to child fails when an object in a proposed state is linked to an object in the current state
CMS-XML Link 'transfer to child' fails when linking proposed to current - ORA-01422: exact fetch returns more than requested
Link ' transfer to child' fails when linking proposed to current - ORA-01422: exact fetch returns more than requested
CMS-XML DIM RM: Embedded or attached objects are not migrated
In the ReqIF transfer an embedded or attached file, for example a PDF or an excel file is imported as an image.
CMS-XML Dim RM 2009 R2: Relationship report returns questionable data
Below are the steps to recreate this problem: - 1) Set the default option for link constraints (' transfer to child' for both primary and secondary links); 2) Link two requirements;
CMS-XML DIM RM: Link cardinality rules violation
Cardinality constraint: 1:n (i.e. a BR can only be linked with one single Rel) Transfer Link to child (both checkboxes ticked) (i.e. link will be transferred to child of BR as well as to child of Rel when replaced) Scenario:
CMS-XML Incorrect version or requirement displayed in collection when child version is deleted
If you create a new version of a requirement using Replace and then delete that new version, you may still see the new (deleted) version of the requirement as part of the collection. This can happen if you selected " Transfer to parent on deletion of child" as one of the parameters when you created the collection.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs