Hello, everyone!
If we are working with usual PDF forms, we can apply Usage Rights to it (via Reader Extensions). So, we can create pdf form, add some rights to it, and after that send this form to our users, and they will have working barcodes, ability to import\export data and save form with theirs input.
But what about Mobile Forms?
In Forms Manager we have a .xdp template and we can provide user url to this template with PDF Render Profile. And as a result - user will see form with not working barcode (becoming grey after each input), no ability to save form and no functionality of import/export data.
So, how reader extensions can be applied to such forms?
Views
Replies
Total Likes
I've found that currently the only way to render up extended PDF forms is to use the older method of creating a render service and exposing it via REST.
Views
Replies
Total Likes
Are you using LiveCycle ES4?
IIRC, You can probably plug your own PDF Render Profile which, in addition to render the PDF , can also apply RE to that. And then from Forms manager UI, you should be able to associate that custom render PDF render profile to your XDP.
Views
Replies
Total Likes
Give it a try in ES4, you'll probably find that the default render for PDF isn't called.
Views
Replies
Total Likes