Form with mandatory fields can be saved, printed, etc. even when empty

[icanteven19]

Hello there,

we are currently working with Acrobat DC Pro 2017 and it seems like the forms with mandatory Fields dont work as intended.

The user created a Form in Excel (O365 under Win10) and saved it as a PDF. Next she edited the fields in DC Pro 2017 so that they are mandatory before you should be able to process it any further.

This results in a PDF-File that kann bei saved as a copy even when None or only few of the mandatory Fields are filled in. Ive read that it should be that if not filled in completely an empty copy should be saved, which is not the case here.

Sadly this is the first form since our switch to Office 365 with Win10 and according to our users, forms with mandatory fields where already created before our Office and OS upgrade.

So i wondered if by any Chance the new Office/OS is doing something the old didn't, that DC Pro 2017 can't handle or is responsible in any other way that the Fields dont work as intended.

ive Read a lot About implementing JAVA- or VBA-Scripts but i think this should not be necessery. only if you want to Output an errornotice to the user that filled the form only partially.

Greetings

[try67 · Accepted solution]

This is a common misunderstanding of required fields in PDF files. They are only validated when the file is submitted. Not when it is saved, or printed, or anything else.

It is possible, however, to utilize the required property to display an error message (or even save/print a blank copy) in these situations, using a script, like this (paid-for) one I've developed: Custom-made Adobe Scripts: Acrobat -- Validate Required Fields Before Printing or Saving

[icanteven19]

thank you very much for your Reply. Even though it is not what i was hoping for it is what i most certainly expected. Thanks again for your fast Reply.

[Test Screen Name]

Just a note that for many people saving BEFORE the form is completed is a vital part of their workflow. It allows them to leave their work for breaks, research, calls, interruptions, etc. and return to it later. We often hear from people where the form designer has tried to stop saving - unsuccessfully - and they have lost work and productivity. Just a different perspective on usability.

This should not matter if the intended FINAL use of the form for the person filling it is to submit it, to a web or intranet server. The problems begin where the planned final use is to save the form - this can be a big problem.