If you need custom information to update after the user signs the form, place the information in a custom item rather than in the form or page globals. This allows you to sign form and page global options without freezing the custom option.
Why use this practice
You should set signatures to sign global and page options in a form. However, if you place custom options in a global item, those options are 'locked' when the global item is signed. This means that the custom options cannot be modified after the user signs the form. As a result, if you need to update your custom information after the user signs the form, you must ensure that the custom information is placed outside of signed global options.
The following sample shows a custom item that contains a custom option and an XFDL option:
Exceptions to this practice
If locking will not affect your custom item’s functionality (that is, if you don't need to alter the value after it has been signed), you do not need to follow this practice. However, it is still considered good practice to create custom items for storing custom information.
Back to: Signatures