Comments (8)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 mdurward commented Permalink

Thanks for the instructions on how to enable rich text formatting. Most of the formatting works great - italics, bold, different sizes, and line breaks. I'm having issues with some of the reports where I am using the View HTML Source icon in long descriptions. The best example is ordered lists that I have created in Job Plan Task long descriptions for printing on paper work orders using the ol tag. <div>&nbsp;</div> ol type="A" start="3" li List Item 1 /li <br /> li List Item 2 /li <br /> /ol <div>&nbsp;</div> ( I left off the tags because your blog is trying to process them) The preceeding code should give a list that looks like the following: <div>&nbsp;</div> C. List Item 1 <br /> D. List Item 2 <div>&nbsp;</div> When I press the VIew HTML code icon to go back to the rich text window, the list displays correctly. <div>&nbsp;</div> I'm using a PM to generate a work order. With the selected work order displayed in the Work Order tracking application, I Select Value Run Reports, select my custom report, and Submit. The report displays the ordered list correctly again in the BIRT Report Viewer tab. However, when I press the Print Report icon and Select PDF, the work order prints with the list displayed as follows: <div>&nbsp;</div> 1. List Item 1 <br /> 2. List Item 2 <div>&nbsp;</div> It appears that when the report is rendered as PDF, it ignores the ol type and start tags. Because of where it doesn't work, it appears that BIRT is not sending the correct tags to PDF or that the version of Adobe that BIRT is using doesn't support these tags. <div>&nbsp;</div> Any suggestions? Thanks! <br />

2 SASHULL commented Permalink

We like the capabilities of rich text format, but on upgrade to base Maximo 75 it doesn't convert existing long description entries into rich text format. The rich text viewer seems to be able to handle this capability, but the BIRT reports do not (by changing the dynamic text type to HTML the rich text displays correctly, but the plain text is bunched together (no line spacing)). If we go the other route and make it plain text, the long description displays old records fine but new records show the HTML tags. It looked like there was a step involved in TSRM 7.2 that upgraded existing records but it doesn't seem to exist in 7.5. Any ideas if this was a missed step in development or if there's a workaround to this?

3 PamDenny commented Permalink

To mdurward... <div>&nbsp;</div> Hi. We have researched your issue, and have received similar results ourselves. Additionally, we have found that this issue has been reported on the bugzilla community at the url below. <div>&nbsp;</div> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285640 <div>&nbsp;</div> We are currently investigating if it will be fixed in a future release. In the meanwhile, please cast your vote for this bug so its priority can be highlighted. Thank you.

4 Shannon Sutton commented Permalink

Steve: Did you find a fix for your issue below? <div>&nbsp;</div> On upgrade to base Maximo 75 it doesn't convert existing long description entries into rich text format. The rich text viewer seems to be able to handle this capability, but the BIRT reports do not (by changing the dynamic text type to HTML the rich text displays correctly, but the plain text is bunched together (no line spacing)). If we go the other route and make it plain text, the long description displays old records fine but new records show the HTML tags. It looked like there was a step involved in TSRM 7.2 that upgraded existing records but it doesn't seem to exist in 7.5. Any ideas if this was a missed step in development or if there's a workaround to this? <br />

5 maxmadman commented Permalink

Here is the workaround I used. <br /> In my fetch I add a row <div>&nbsp;</div> row["html"] = row["poltext"].search(""); <br /> (well between the double quotes, search("") I have /font within brackets, it is removed when I post here) <div>&nbsp;</div> I add the output column "html" , type integer. <br /> In the section I print the long description I have two rows, one for the RTF and another for HTML. <br /> I make them visible or hidden based on what the value of the html column is as well as adding an expression to the data binding of the control. <br /> for RTF; <br /> if (row["html"]==-1) { <br /> dataSetRow["poltext"]; <br /> } <div>&nbsp;</div> for HTML <br /> if (row["html"]&gt;0;) { <br /> dataSetRow["poltext"]; <br /> } <div>&nbsp;</div> The hidden\visiblity attributes use the same syntax etc. <br /> row["html"]&gt;0; <div>&nbsp;</div> I am sure there are other ways, but this seemed simple enough. <br /> -Wes

6 LatifPatel commented Permalink

Hey thank you so much .It is help me lots. It solve my issue.

7 John Singer commented Permalink

How do you get QBR reports to render the RTF text? <div>&nbsp;</div> Also, the dynamic text field works fine in BIRT for rendering the RTF to a pdf report output, but if you output to Excel it creates a new row in the spreadsheet for every line in the text field and also merges/splits cells. This makes the spreadsheet useless for sorting/filtering which is what the majority of our users do. Is there a solution that will keep all the text in one cell of the spreadsheet.

8 sunk818 commented Permalink

In response to comment #4. In Maximo 6.2, the long description saved carriage returns (CRLF, or 0D0A in HEX). This displayed correctly if you are not using rich text editor. If you are using Rich Text Editor, the CRLF (0D0A) are not interpreted correctly. Basically, they are ignored. We opted to turn off the rich text editor which requires a restart of Maximo.

 
This will tell yo uhow to disable rich text editor
https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/IBM%20Maximo%20Asset%20Management/page/Making%20long%20description%20a%20text%20field
 
If you do run the updaterichtext.bat it will convert the CRLF to <br />. We found with Crystal Reports, text interpretation to HTML requires <br> not <br />, so we had to use a formula to perform additional processing before display.
 
stringvar output := {LONGDESCRIPTION.LDTEXT};
output := Replace(output,"<br />","<br>"); //get rid of line feed character
output := Replace(output,Chr(13) & Chr(10),"<br>"); //get rid of carriage return character