0 Replies Latest reply on Mar 6, 2014 6:16 AM by Lifer

    Adding reader extended forms to PDF Portfolio using PDFG

    Lifer Level 1

      Environment: ES4 LiveCycle11

       

      I have a number of pdf forms which I want to distribute to clients as a single PDF portfolio.  Some of these forms are editable and have reader extensions applied, the others are just static forms.

       

      First off the editable forms have reader extensions applied using the Reader Extensions web service.  Then all the candidate forms are passed to the Assembler Service to create the PDF Portfolio.  The following is a representation of the DDX

       

      <?xml version="1.0" encoding="UTF-8"?>

      <DDX xmlns="http://ns.adobe.com/DDX/1.0/">

                  <PDF result="out.pdf">

      <Package/>

      <PackageFiles>

      <PDF source="Editable1.pdf"/>

      </PackageFiles>

      <PackageFiles>

      <PDF source="Editable2.pdf"/>

      </PackageFiles>

      <PackageFiles>

      <PDF source="Static1.pdf"/>

      </PackageFiles>

      <PackageFiles>

      <PDF source="Static2.pdf"/>

      </PackageFiles>

      <PackageFiles>

      <PDF source="Static3.pdf"/>

      </PackageFiles>

      </PDF>

       

      The PDF Portfolio is created successfully however when it is opened in Adobe Reader (XI) the following message is displayed.

      AdobeREmsg.JPG

      The editable forms are not changed in any way after reader extensions are applied. My expectation was that the individual reader extended files would still be editable within the PDF Portfolio.  Am I missing a step, perhaps in the DDX config which is causing the reader extensions settings to be disabled?

      Thanks