Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Workbench-process produced PDF's browser support.

Level 1
Level 1

Dear All,

We have recently started working on a new project LC ES4. The output-PDF we produce out of the workbench process is sent to client/end-user to further edit/update and get Docusigned. But as you know such dynamically generated PDF cannot be opened in browser hence getting it DocuSigned isnt possible. On the other hand, making the XDP static loses the dynamic feature we applied to it using Javascript, and PDF-output generated from such static-XDP could open in browser but no javascript validations work nor the prefilled data is appearing when viewed in browser.

Out of this all, we have managed to find some workaround like keeping XDP and PDF-output as Dynamic and have user save the edited version of the given PDF by printing/saving the given PDF as "Adobe PDF". Can you comment on this workaround?

Last but not least question. We have been shared a PDF form which is a Adobe InDesign produced and surprisingly when opened in browser, it is showing fine with data along with ALL the javascript properly working in browser. On the other hand, the process generated PDF-output using static XDP, just opens in browser NO-Javascript is working(but the same PDF is opening in Adobe Reader with data populated and full javascript support). Does thsi mean, Designer created PDFs doesnt support javascript in browser but InDesign does?

Looking forward for your valuable reply.



0 Replies