Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Exclude packages during integration

Exclude packages during integration

This article explains how to exclude packages when publishing requirements from Optimal Trace to QADirector.


I am unable to exclude packages when publishing requirements from Optimal Trace to QADirector. Is it possible to do this?


Yes, it is possible to exclude packages during Optimal Trace to QADirector integration. These are the instructions:
  1. In the left pane tree view, select the package to exclude.
  2. Select the Custom Props. tab, and then click the Show Custom Properties button. The Package Custom Properties dialog box appears.
  3. Click the Add a New Custom Property button and add the custom property ExcludeSynch.
  4. Set the value of ExcludeSynch to 1.
  5. Click OK to dismiss the dialog box, and then perform a publish or synchronization with QADirector. During the transfer of data, the excluded package and all of its children are excluded.
Note: Packages that are excluded after the initial publish to QADirector are ignored in subsequent synchronizations. Results are not sent back to Optimal Trace.

This article was created for Optimal Trace version 5.2

Old KB# 14812


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:18
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.