Moving requirements from one type to another using SDK

Moving requirements from one type to another using SDK

The attached sample code does the following:

1. Create a requirement named "Moved From DAVE" if it does not already exist. This will store the moved requirements

2. Move requirement "New Requirement - DAVE298" and its children to requirement "Moved From DAVE" within requirement type "Fred"

NB: When you create a requirement through the SDK and you require to find it using the requirement tree, you will need to refresh the tree.

Please see the following Knowledge Base Article for issues after adding a new requirement. This will help if the requirement cannot be found in the requirement tree: http://community.microfocus.com/borland/define/caliber_-_requirements_management/w/knowledge_base/7315/after-adding-a-new-requirement-programmatically-why-can-the-requirement-not-be-found-in-the-requirement-tree

Old KB# 15785

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:25
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.