Adobe 22002486 Digital Signature User Guide - Page 74

Forcing Signers to Use a Specific Signature Appearance

Page 74 highlights

Acrobat 9 Family of Products Security Feature User Guide Controlling Signing with Seed Values Forcing Signers to Use a Specific Signature Appearance 74  false: A false value indicates that the document should not be locked after signing. By default, the user is given the option of locking after signing. Again, the required flag determines whether this is a required constraint.  auto: Default. The auto value allows the consuming application to decide whether or not to present the lock UI for the document and whether to honor the required flag based on the properties of the document. Example 5.2 Seed value: lockDocument f = this.getField("mySigFieldName"); f.signatureSetSeedValue({lockDocument:}); //Set the setting as required f.signatureSetSeedValue({lockDocument:, flags:0x80}); Figure 58 Sign Document dialog: With Lock Document checkbox added 5.4 Forcing Signers to Use a Specific Signature Appearance Enterprises and other structured work environments sometimes provide uses with predefined signature appearances. These appearances are then used for specific signing purposes. For example, the appearance may identify the signer's organizational affiliation or a particular task or workflow that pertains to the signed document.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189

Acrobat 9 Family of Products
Controlling Signing with Seed Values
Security Feature User Guide
Forcing Signers to Use a Specific Signature Appearance
74
false
: A false value indicates that the document should not be locked after signing. By default, the user
is given the option of locking after signing. Again, the required flag determines whether this is a
required constraint.
auto
: Default. The auto value allows the consuming application to decide whether or not to present
the lock UI for the document and whether to honor the required flag based on the properties of the
document.
Example 5.2
Seed value: lockDocument
f = this.getField("mySigFieldName");
f.signatureSetSeedValue({lockDocument:<true/false/auto>});
//Set the setting as required
f.signatureSetSeedValue({lockDocument:<true/false/auto>, flags:0x80});
Figure 58
Sign Document dialog: With Lock Document checkbox added
5.4
Forcing Signers to Use a Specific Signature Appearance
Enterprises and other structured work environments sometimes provide uses with predefined signature
appearances. These appearances are then used for specific signing purposes. For example, the appearance
may identify the signer’s organizational affiliation or a particular task or workflow that pertains to the
signed document.