Set signatures to sign global and page options such as global fonts and background colors. While omit
filters automatically sign form and page globals unless they are specifically excluded, it is easy to neglect global options when using a keep
filter. However, modification of non-secure global options can effect the entire form.
Form developers will sometimes omit globals because they contain custom items that need to keep operating after the user has signed the form. However, custom information should be placed in custom items.
Why use this practice
If you do not secure your form's global and page options, someone could alter these options to obscure what is being signed. For example, someone could change the background color of a form so that text becomes unreadable.
Global and page options such as global fonts and background colors are not automatically signed by the keep
filter. As a result, it's best to use omit
, which automatically secures your global and page options unless you intentionally exclude them from a signature. However, if you must use a keep filter, ensure that form and page globals are identified in a signoptions
Assume that you have created a one-page form with a grey background color and black font color. At the bottom of the form, you've written a notice in a yellow font that reads, "By signing this form, you agree to allow XYZ Inc. to sell information about you."
In this scenario, if you haven't set the signature filters to sign global background and font colors, it's possible for someone to change the default background color from gray to yellow. The new default background would render your notice in yellow font invisible to the reader. This leaves the signed form vulnerable to repudiation and XYZ Inc. exposed to possible legal consequences for selling personal data without permission.
The following code sample shows a keep
filter that specifically secures the background and font color set in a form global and font information set in a page global. Additionally, it secures custom items placed in the page and form globals
Exceptions to this practice
There are no exceptions to this practice.