Hi Anupama,

Thanks for posting on PSC.

An enhancement request is raised with Pega for the same when a similar requirement was posted on PSC earlier. You can track the development of this feature using the feedback id(FDBK-19717) through your account executive.

How about using OOTB HTMLTOPDF activity? As of now, it doesn't take margin as parameter thus there is the drawback. And this enhancement request will consider that aspect as well.

In one of the post, a Pega developer was using <img alt="" src="binary-file-location"/> and was able to generate the margin too.

Hope it answers your query, please mark it answered if it does.

Regards,

Asif

Hi All,

If any one provide information,that will be much helpful.

Thanks

Anupama

To my understanding:

If you use the underlying library to convert HTML to PDF - you miss out required functionality ; with regard images/stylesheets being found/fetched for conversion.

Ideally: you should stick to using the OOTB HTMLTOPDF Activity as mentioned above.

I know you said you needed 'different footers' for each pages; can you elaborate on what this would mean.

Because there is a basic feature already built-into HTMLTOPDF to provide a 'page x of y' type footer (or header in fact)

You should just need to set the Parameter for HTMLTOPDF "pyPDFFooterHTMLTemplate" to "${page} of ${total}"

Which will show a different footer for each page.

If you have something more advanced to do here; then let us know - I have another idea (to 'post-process' the PDF to 'post-process' the generated PDF) - but it is a bit more involved.