Validation Patterns and locking Digitial Signature

The code for a validation script in LiveCycle Designer needs to return either a logical true of false value. The false value indicating that the data failed to pass the validation script. When a logical false value is returned, then the message in the "Validation Script Message" option when the "Error" option check box is enabled.

Since signatures rely on a valid certificate, there should be no need to validate this field.

All I want to do is simply lock all of the fields after the form is signed. I selected Lock Fields After Signing.

When I go to test it in the PDF tab, Live Cycle Designer performs a validation of the fields after I sign it, and says that the fields fail the Validation. I didn't want that or set it, but it does it anyway. Even if I leave the validation pattern field blank, LCD still wants to validate the fields after I sign it.

The act of "signing" a form is an act of finality on the form - any change to the form following signing would result in revocation of the signature. Look at it from the form's point of view - if you are signing it, then it must be correct, hence the automatic validation.

From the help file: "If an edit pattern has not been specified and the user input does not match LiveCycle Designer defaults, validation fails."

Instead of setting the validation to blank, you may want to consider applying a broad enough validation for each field that would accept all valid answers. The failure to validate at that point would boil down to one of two things - either the data in the form is incorrect, which being the case you shouldn't be signing it, or the programmer overlooked a possible valid combination (which never happens..... ok, hardly ever!)

Within LiveCycle Designer, press F1 (windows) and type "validation" into the search box for a full explanation as to how validation works.

Hope that helps you out some! :)

DaveyB

So then what is the edit pattern to use when the input could be anything - alpha characters, numbers or symbols and the display should be exactly as the User input it. (I checked the help file and another resource and couldn't find anything)