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

Why does CaliberRM produce incorrect requirement XML?

Why does CaliberRM produce incorrect requirement XML?

Problem:

Why does CaliberRM produce incorrect requirement XML?

Resolution:


  • Product Name: CaliberRM
  • Product Version: All
  • Platform/OS Version: All


The requirement XML produced by CaliberRM can contain erroneous XML characters. For example the characters "

The "

The "&" character will generate an error because the parser interprets it as the start of an character entity

This is usually due to the HTML requirement description in CaliberRM, UDA values containing illegal XML characters or any other CaliberRM field containing illegal XML characters i.e. requirement name. This can be resolved by:

  1. Removing the HTML description between the XML tags. This can be achieved by simple string manipulation. Attached to this article is sample Visual Basic code, "Remove_Description_All.txt" which shows how to remove the from description any text between the tags "" and "" .

  2. Replacing the HTML description with the plain text of the description using the CaliberRM SDK. This can be achieved by using the simple string manipulation and the HTMLHelper class from the CaliberRM SDK to convert the HTML description to plain text. Attached to this article is a sample Visual Basic code (Remove_Description.txt)

  3. Parse the text between UDA tags removing illegal XML characters. This can be achieved by simple string manipulation. All illegal XML characters would need to be removed between the XML tags i.e. " ", " "

Related documents:

Remove_Description.txt

Remove_Description_all.txt








Old KB# 16534

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