Question
TD Bank Group
CA
Last activity: 8 May 2016 11:40 EDT
Create PDF generates document with white text on white background
We are trying to leverage the "Create PDF" smart shape to generate a PDF based on a section, but for some reason the text contained in a grid is generated in white text on a white background.
The section used does not format those texts with a white color, so we don't understand why it is not using the style defined on the section.
We run PRPC 7.1.7.
How can we get this to generate a PDF with text colors that match what is defined on the section?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
TD Bank Group
CA
GCS is saying that this is "working as designed" for 7.1.7 and has been "fixed" in 7.2...
I do not agree that if something gets fixed in a later release anc can be considered as "working as designed".
Here is what I got in an email from Pegasystems Support: "If the main issue you are having is the white-colored text, this is a known quirk with PD4ML."
Not sure why a fix for 7.1.7 cannot be provided.
Pegasystems Inc.
IN
- would it be convincing to quick test with a regular smart layout to learn the observations...
TD Bank Group
CA
Pegasystems Inc.
IN
>>> Only the grid repeat layout seems to be causing an issue
- do the layout contain any specific styles?
- can we double check if there are any changes on skin rule...
- also - could we test with dummy sample grid repeat layout [with headers]/recreating it new works?
Pegasystems Inc.
IN
also please delete the browser cache once...
TD Bank Group
CA
PDF is generated on the Server side, so not sure what the broswer cache would have to do with this.
Pegasystems
US
You can go into tracer in the htmlToPdf activity and capture the html from the "markup" param BEFORE the actual conversion to pdf.
If you store this html from the param into a file and display the file in your browser, does it show the same problem ? If so, then the pdf conversion is not the issue. /Eric
TD Bank Group
CA
I just did this (save the MARKUP param as an HTML file) and the HTML looks good in a browser. The text is showing as black text on white background.
So I guess this means that the PDF conversion of the HTML file is the issue...
Hi Patrick,
My guess is that the grid is referencing some style with background color as defined in the skin.
Now when you export to pdf then the skin styles are not picked up and so the background color is lost.
Please try with adding inline styles and they should come up in the exported pdf.
Regards,
Amit
TD Bank Group
CA
Based on the test I did, following Eric's instructions with the tracer, it does not look like it's a styling issue.
Hi Patrick,
Though it doesn't seem like styling issue, pega styles are cached in browser and so html might still display it correctly especially if run in same session as pega.
I will still try once with inline styles if nothing else works out
Updated: 17 Mar 2016 12:59 EDT
TD Bank Group
CA
Hi,
I may be missing something but isn't a Create PDF Smart Shape in a flow executed on the server side and not on the browser?
If so, how would the browser cache be involved in a step that is run on the server side?
Also, based on the above, I traced the execution and capture the HTML produced before sending it through the PDF java library and the HTML looks good. So to me, it's a PDF generation issue, not a problem with the HTML that's produced.
Hi Patrick,
Please let us know the SR number here, if you end up raising one.
Thanks,
Lochan
TD Bank Group
CA
Pegasystems
US
I agree it's a defect. In fact I see the same issue. Merely put a label in a section and pdf it with the smart shape and run the flow and click the attachment and I see the white stuff. To get the issue fixed, please put in an sr.
However, to get something working quickly, try this: the pdf smart shape uses activity pxCreatePDF . That activity does two things basically. First, it converts your section to pdf. Second, it attaches the result to your work object. There are two catches. One is that it doesn't convert JUST your section to pdf, but rather it encapsulates your section in a harness called pzCreatePDFHarnessWrapper. The other catch is that everything involved is a "final" rule.
So, try doing a save-as of the few pieces you need, namely the activity and the activities it calls. Change the names and references accordingingly. Then, instead of encapsulating your section in the harness, have it use your section directly.
Then, use a utility shape in your flow instead of the "smart" shape, and refer the utility shape to your new version of pxCreatePDF. Does it solve your problem ? /Eric
TD Bank Group
CA
Accepted Solution
TD Bank Group
CA
GCS is saying that this is "working as designed" for 7.1.7 and has been "fixed" in 7.2...
I do not agree that if something gets fixed in a later release anc can be considered as "working as designed".
Here is what I got in an email from Pegasystems Support: "If the main issue you are having is the white-colored text, this is a known quirk with PD4ML."
Not sure why a fix for 7.1.7 cannot be provided.
Pegasystems Inc.
JP
Hi,
I am facing the same issue on Pega 7.2. According to the following PDN article, this issue seems to be already resolved in 7.2. I think I need to do some modification on pyEndUser skin but exactly what should I do? I am using the section which is used in assignment and I don't want to affect UI on actual screen.
https://pdn.pega.com/support-articles/create-pdf-generate-document-white-text-white-background
Thanks,
Kensho
Pegasystems Inc.
IN
Hi Kensho ,
The work around would be, Application developers can change the OOTB skin "pyEndUser71", "pyEndUser" settings or they can add in line styles respective to the supported PD4ML library . Please find the below links to find CSS properties and HTML tags supported by PD4ML . This might be helpful for you.
Pegasystems
US
If you are not able to find a satisfactory local change for yourself in Pega 7.2, or you are concerned that the support article is inaccurate because it says the issue is fixed in 7.2 and you are observing it not fixed, I suggest you either re-open the previous SR or put in a new one as appropriate.
If you are the same customer as submitted the previous SR, and the resolution to the previous SR said the issue is resolved in Pega 7.2 and you observe it is not resolved, re-opening that SR is appropriate.
If you are a different customer, I would suggest opening a new SR, and citing the old SR number and this discussion url.
Of course, if you can find a satisfactory solution with a local change, that would be great, and if you still decide to pursue an SR, please mention what local change worked for you. Thanks. /Eric