Extracting pages with form fields results in poorly written

[DSSavant]

Extracting Form Fields on multiple pages results in an improperly written PDF file

When extracting pages of a multi-page form, if a given form field is found on two or more pages, the extraction will result in the creation of a flawed PDF file. When JavaScript is then used to extract form field information, the script will cause the viewer to completely go away. “Go away” means that the Viewer process terminates in a very heavy handed manner.

Since this is a very difficult problem to describe and show how to reproduce using forum tools, I have done so in Word and attached the instructions and PDFs needed. Please refer to the attached ZIP file and read the instructions and problem definition found in SimpleFormIssue.pdf.

[Ivan - Tracker Software]

Thanks for clear description! Problem is reproduced and will be fixed in the next build of the viewer

[Tracker Supp-Stefan]

Hello DSSavant,

We also created a ticket in our internal system for your case:
#1138: Extracting pages with form fields results in poorly written PDF files
So that it can be easily followed by all involved in resolving it.

Best,
Stefan

[DSSavant]

Many thanks!

[Tracker Supp-Stefan]

[DSSavant]

As of build 4.0200, this issue remains outstanding. (Using Viewer 2.5.199 and 2.5.200 to test with.)

While the Viewer does not blow up when loading the poorly written PDF, it displays Form Fields for pages that no longer exist in the Field Pane. In my latest test on my box, I extracted one page from a document with 100 pages and multiple form fields. The page I extracted had No form fields on it though the Fields Pane shows fields for 20 different pages as found in the original document.

When running Javascript to access the Form Fields on a given page, since the fields no longer exist, the scripting engine blows the viewer up causing it to fault.

Please let me know if you need any more information in reproducing this.

[Tracker Supp-Stefan]

Hello DSSavant,

I am now checking this once again with Ivan and we will advise if we need any further details on this.

Best,
Stefan

[Tracker Supp-Stefan]

Hello DSSavant,

after checking this topic with the guys - we've created a separate ticket for the issue with blowing up viewer when you try to extract non existing form fields:
#1403: Viewer 2.5.200 displays form fields for pages that do not exist and crashes if one attempts to access those fields

Best,
Stefan

[DSSavant]

Will this be in the next build that will coincide with the next Viewer build of 2.5.201? My company uses this functionality on thousands of documents each day. When one of those documents has form fields, things tend to go sideways quickly.

[John - Tracker Supp]

Yes - barring any unforeseen issues it will be.

[Tracker Supp-Stefan]

Hello DSSavant,

I see in the ticket that it's already been investigated - so just as John said - if everything goes normal - it should be.
We will update this topic once again when we have more info on the ticket.

Best,
Stefan

[Tracker Supp-Stefan]

Hello again DSSavant,

Just a quick update that the crash has been resolved, and the initial problem will be fixed in the next major version.

Best,
Stefan

[DSSavant]

Stefan,

"next major build". Does that mean 2.5.202 or 3.X? If 2.5.202 then great and thank you as my customers will be able to benefit from the fix very soon.

[Paul - Tracker Supp]

hi DSSavant,

we are anticipating a build 202 - we don't have a firm date yet, however you will not have to wait for V3.

hth

[DSSavant]

Many thanks.

[Paul - Tracker Supp]