Adding Custom Signing Reasons - Adobe 22002486 User Manual

Acrobat 9 Family of Products
Security Feature User Guide
Authors in such environments can specify which signature appearance is required for any given signature
field. As with other seed values, a flag bit is used to indicate whether or not the field is a recommendation
or mandatory. A signature field is correlated with a specified name which is then used to match a given
appearance. The string name must exactly match the name of a signature appearance for it to be selected.
Example 5.3
f = this.getField(<Field Name>);
f.signatureSetSeedValue({appearanceFilter:"Example Appearance Name"});
//Set the setting as required
f.signatureSetSeedValue({appearanceFilter:"Example Appearance Name", flags:0x100});

5.5 Adding Custom Signing Reasons

Acrobat predefines several common signing reasons such as "I am approving this document. " However,
the author can specify custom reasons and make those reasons required or optional. When custom
reasons are marked as required, users cannot enter any new reasons as the field becomes read-only. When
those reasons are flagged as optional, signers can choose one of the provided reasons or create a new one
by typing in the Reason field. Specifying a signing reason will remove all of the default reasons from the
reason drop-down list.
User interface impact: Note that end users have a user interface preferences that allows them control
whether or not the reason's field appears. The preference interacts with the reasons flag as shown in
9, and the logic is as follows:
The document author has control over whether the UI appears and the

user-specified settings.
When a flag makes the field

To specify custom signing reasons:
1. Create a signature field with an intuitive name and tooltip.
2. Create the JavaScript that gets the field object and uses the seed value method
3. Add the reasons. The reason list is an array in the format of ["one", "two", "three"].
4. Enter a flag value to indicate whether the value is required or not.
If a reason is not required, signers can add their own custom reason while signing.

If the predefined reasons are required, signers are prevented from saving a document with their

own reason
5. Run the JavaScript, save the document, and test the field.
Table 9 Reason field behavior
# of Reasons UI Pref
0 (empty array) off
Seed value: signatureAppearance
optional
(Figure 59).
Flag Reason Behavior
Required Reason field does not appear in UI.
, end users can enter custom reasons.
Controlling Signing with Seed Values
Adding Custom Signing Reasons
flag overrides
required
(Example 5.4).
75
Table