Question
Estes Forwarding Worldwide
US
Last activity: 3 Mar 2023 21:58 EST
Creating PDF through Local Action
I'm attempting to create a pdf and attach to multiple cases using a local action that calls an activity. The activity works on its own, but when calling from a local action, the PDF gets corrupted.
Here is the activity for creating and attaching PDF (a few lines commented out for testing purposes):
Here's the local action that I'm using to call the activity:
Here is the HTMLToPDF parameter page when called from an activity (working):
Here is the HTMLToPDF parameter page when called from an activity within a local action (not working):
Looks like the modal is effecting the Markup parameter? How do I prevent this from happening?
Thanks! Devin
Bits in Glass
IN
@DevinD16607791 were you able to find the root cause for this?
Estes Forwarding Worldwide
US
@Anoop Krishna I found a workaround. Instead of calling the activity from local action post-processing, I created a new modal template and called the activity from a button click. Not ideal but will work for the time being.
I'll be submitting a support request for the issue. I believe this is a bug, at least for the version I'm using.
Pegasystems Inc.
US
Hey @DevinD16607791!
Let us know the ticket number for your case with Support so that we can connect this post with it for tracking!
Wipro
US
It seems that the issue you're facing is related to the local action affecting the Markup parameter when calling the activity. One possible solution is to pass the Markup parameter value directly to the activity as a parameter, instead of relying on the local action to populate it.
To do this, you can add a parameter to your activity with the same name as the Markup property and set its value to the HTML markup you want to convert to PDF. Then, in the local action, you can pass the HTML markup value as a parameter to the activity.
Another solution could be to use a different method for creating and attaching the PDF file, such as using the Pega OOTB PDF generation functionality instead of a custom HTMLToPDF activity.
It's also worth checking if there are any issues with the PDF generation process itself, such as missing or invalid font files, as this could cause the PDF file to become corrupted.
I would recommend trying out these solutions and doing some additional testing to determine the root cause of the issue. If you're still facing issues, it may be helpful to reach out to Pega support for assistance.
Estes Forwarding Worldwide
US
@RishabR16722312 I had the same suspicion. I will try this out. Thanks!
Wipro
US
I am glad to hear that you found a possible solution to the issue you were facing with creating and attaching a PDF through a local action. Passing the Markup parameter value directly to the activity as a parameter is a good approach, as well as using the Pega OOTB PDF generation functionality instead of a custom HTMLToPDF activity.
It is also important to thoroughly test any changes or workarounds before deploying to production to ensure that the PDF file is not corrupted and users are able to access and view it properly.
If you encounter any further issues or challenges, do not hesitate to reach out to Pega support for assistance. They will be able to provide additional guidance and support as needed.
Thank you for sharing your experience and solution with the Pega community. Your contribution is valuable in helping others overcome similar issues and challenges.