| Tip |
|---|
Looking for a section on this page? Hover your cursor over the Table of Contents icon |
...
When a section is signed, the data in the section, together with a time stamp, the signing user, and a few other things are used to generate a message digest. The message digest is digitally signed using the private key. The signatures (there can be more than one) are included with the submission – in the repository and sent in the HTTP POST so you can can save it yourself if you want.
When the form is re-initialized from the submission documents, you must also supply the signatures. The initialization process will verify that the data has not changed (i.e., has not been tampered with) and the signature is still valid. If the signature is not valid, it is removed and the entire Section is displayed with a visible error (large red background). If it is valid, there is a green background and the Section cannot be edited.
...
The Lock sign means that the next person in the workflow can not remove the signature and edit the signed data. A good use case is an employee performance review where the manager starts the form, and signs the review, and sends it to the employee. You would check Lock sign so the employee cannot unsign and edit the data entered by the manager.
The Must sign property makes the signature required. With Must sign, a form cannot be submitted or a workflow is not sent to the next person until the signature is added.Checking Must sign will disable the None Required option from the Signature dropdown and automatically selects Text/Signature Image. You can change the Signature dropdown to Wet Signature.
Sections that are hidden/not hidden via a rule or the Visible property in the designer, behave as stated below with respect to Must Sign:
...