Incorrect print pdf in RQM 2.0.1
Hi,
After upgrading RQM to 2.0.1, we are unable to print proper pdf test plan/test cases. There are 2 issues we noticed :-
1) It will print a one liner in customized grid section
2) Or it will print all html style tags in the rich text area as shown below
Table of Contents
1.Test Plan     <br>2.Introduction    <br>    2.1 Project Overview<br>&
Did any one face similar issues? Is there any work around to tackle this issues?
After upgrading RQM to 2.0.1, we are unable to print proper pdf test plan/test cases. There are 2 issues we noticed :-
1) It will print a one liner in customized grid section
2) Or it will print all html style tags in the rich text area as shown below
Table of Contents
1.Test Plan     <br>2.Introduction    <br>    2.1 Project Overview<br>&
Did any one face similar issues? Is there any work around to tackle this issues?
5 answers
Hi,
After upgrading RQM to 2.0.1, we are unable to print proper pdf test plan/test cases. There are 2 issues we noticed :-
1) It will print a one liner in customized grid section
2) Or it will print all html style tags in the rich text area as shown below
Table of Contents
1.Test Plan <br>2.Introduction <br> 2.1 Project Overview<br>&
Did any one face similar issues? Is there any work around to tackle this issues?
I will have to look into #1 a bit further, but I can answer #2 for you.
If you are seeing HTML tags in your PDF output that means that the HTML which is being used to represent that Rich Text section is not valid XML. This can happen for a variety of reasons but generally happens when you copy and paste text from some source that does not use XHTML to represent its rich text. The worst offender by far is MS Word. The web browser is not dependent on XHTML and can generally figure out what the author "meant" and show it, but the PDF generation engine absolutely needs to have valid XHTML to work.
You can attempt to "clean up" this malformed content by pressing the "validate" button on the Rich Text Editor. This will run the content through a series of algorithms and tools we've put in place to try to convert HTML to XHTML. It is not always possible to correctly cleanup content so make sure you review the output from pressing this button before you save the resource.
In prior versions of RQM this was done automatically, we moved to this "validate" button method to give the user the chance to catch and fix any mistakes or algorithms might make.
That being said, there is a bug in 2.0.1 that could still cause you problems even after validating. If the validate button does not solve the problem then you will likely need to upgrade to iFix01 where we have fixed this other bug.
Hi Michael,
Thanks for your immediate response.
I tried using the "Validate" button. As you mentioned it works fine for some sections but not all. I also upgraded to iFix01, but now the issue is different. It prints only the first 2 -3 sections in a test plan. For example I have sections viz summary,description,doc attributes,revision history,table of content etc in my test plan. Even if I validate each and every section, it will only print summary,description and doc attributes. Rest of the section only has a heading, but no data under it.
Waiting for your valuable response.
I will have to look into #1 a bit further, but I can answer #2 for you.
If you are seeing HTML tags in your PDF output that means that the HTML which is being used to represent that Rich Text section is not valid XML. This can happen for a variety of reasons but generally happens when you copy and paste text from some source that does not use XHTML to represent its rich text. The worst offender by far is MS Word. The web browser is not dependent on XHTML and can generally figure out what the author "meant" and show it, but the PDF generation engine absolutely needs to have valid XHTML to work.
You can attempt to "clean up" this malformed content by pressing the "validate" button on the Rich Text Editor. This will run the content through a series of algorithms and tools we've put in place to try to convert HTML to XHTML. It is not always possible to correctly cleanup content so make sure you review the output from pressing this button before you save the resource.
In prior versions of RQM this was done automatically, we moved to this "validate" button method to give the user the chance to catch and fix any mistakes or algorithms might make.
That being said, there is a bug in 2.0.1 that could still cause you problems even after validating. If the validate button does not solve the problem then you will likely need to upgrade to iFix01 where we have fixed this other bug.
Thanks for your immediate response.
I tried using the "Validate" button. As you mentioned it works fine for some sections but not all. I also upgraded to iFix01, but now the issue is different. It prints only the first 2 -3 sections in a test plan. For example I have sections viz summary,description,doc attributes,revision history,table of content etc in my test plan. Even if I validate each and every section, it will only print summary,description and doc attributes. Rest of the section only has a heading, but no data under it.
Waiting for your valuable response.
Hi,
After upgrading RQM to 2.0.1, we are unable to print proper pdf test plan/test cases. There are 2 issues we noticed :-
1) It will print a one liner in customized grid section
2) Or it will print all html style tags in the rich text area as shown below
Table of Contents
1.Test Plan <br>2.Introduction <br> 2.1 Project Overview<br>&
Did any one face similar issues? Is there any work around to tackle this issues?
I will have to look into #1 a bit further, but I can answer #2 for you.
If you are seeing HTML tags in your PDF output that means that the HTML which is being used to represent that Rich Text section is not valid XML. This can happen for a variety of reasons but generally happens when you copy and paste text from some source that does not use XHTML to represent its rich text. The worst offender by far is MS Word. The web browser is not dependent on XHTML and can generally figure out what the author "meant" and show it, but the PDF generation engine absolutely needs to have valid XHTML to work.
You can attempt to "clean up" this malformed content by pressing the "validate" button on the Rich Text Editor. This will run the content through a series of algorithms and tools we've put in place to try to convert HTML to XHTML. It is not always possible to correctly cleanup content so make sure you review the output from pressing this button before you save the resource.
In prior versions of RQM this was done automatically, we moved to this "validate" button method to give the user the chance to catch and fix any mistakes or algorithms might make.
That being said, there is a bug in 2.0.1 that could still cause you problems even after validating. If the validate button does not solve the problem then you will likely need to upgrade to iFix01 where we have fixed this other bug.
Hi,
Is this issues fixed??
Thanks for raising this issue. Might be a new bug, I'll have someone investigate immediately.
It looks like if you do not add any rows to the custom grid then the grid is not rendered and instead the JSON string used to hold the data is printed to the PDF. If you add a single row to the custom grid it will render correctly.
I've opened 30277 to address this issue. You can follow its progress here.
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/30277