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