LiveCycle ES2: PDF form state not maintained after converting to PDF/a

Issue

 After converting a PDF file to PDF/A using LiveCycle ES2 you may notice that the form state has not been maintained for unsigned files.  This can manifest itself in that form objects (fields, buttons, subforms etc…) which were hidden in the original PDF file, are now visible in the resulting PDF/A file.

The form state is always maintained for signed files.

Solution

 This is an issue in LiveCycle ES2 (9.0.0.0, 9.0.0.1 and 9.0.0.2).  This issue will be addressed in ES2 SP3 and the new ADEP platform.  There are patches available for ES2 SP1 and SP2, so contact enterprise support if you require one of these patches.

Additional information

 We have added a new flag to the PDFOutputOptionsSpec used during the PDF to PDF/A conversion called “retainFormState“.  This flag must be set in the API parameters, or using the new option in the Workbench UI, to retain the form state on the resulting PDF/A file.

Here is the existing javadoc for PDFOutputOptionsSpec:

http://help.adobe.com/en_US/livecycle/9.0/programLC/javadoc/com/adobe/livecycle/output/client/PDFOutputOptionsSpec.html

reference: (182219821/2818751)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)