Adobe 22002486 Digital Signature User Guide - Page 64

Specifying a Post-Signing Action

Page 64 highlights

Acrobat 9 Family of Products Security Feature User Guide Authoring Signable Documents Specifying a Post-Signing Action 64 2. Right click on the field and choose Properties. 3. Check Required on the General tab. 4. Choose Close. Users can still open, close, save, and send the document without any indication that the field is required until the document author sets up a check for the required flag. For example, the check could be as simple as emailing the document. In this case, the author would add an action to the button to submit the document and configure a URL. If the document recipient clicks on the field and then cancels the signing process, an alert will appear. Server-side and other JavaScript checks are also possible. Figure 53 Required field not signed alert 4.4.4 Specifying a Post-Signing Action JavaScript actions can be associated with a signature field so that an action occurs whenever the user interacts with the field in some predefined way. However, documents are usually signed to protect, guarantee, and or attest to the signed content. Signers usually want to know that the document they are seeing is the document they are signing, and document recipients usually need to know that the document they are viewing is the same as the document that was signed. For this reason, adding actions to a signature field is inadvisable. Field actions change the underlying bytes of a PDF and could adversely affect document security as well as content integrity. Caution: Using this feature is NOT recommended since such actions are contrary to the secure and trusted nature of most signing workflows. Adding actions will result in a legal warning about the legal integrity of the document. To associate an action with a field. 1. Create a new field. Note: For existing fields, place the form in edit mode by selecting Forms > Add or Edit Fields and then double click on them OR right click and choose Properties. 2. Display the Action tab.

  • 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
Authoring Signable Documents
Security Feature User Guide
Specifying a Post-Signing Action
64
2.
Right click on the field and choose
Properties
.
3.
Check
Required
on the General tab.
4.
Choose
Close
.
Users can still open, close, save, and send the document without any indication that the field is required
until the document author sets up a check for the required flag. For example, the check could be as simple
as emailing the document. In this case, the author would add an action to the button to submit the
document and configure a URL. If the document recipient clicks on the field and then cancels the signing
process, an alert will appear. Server-side and other JavaScript checks are also possible.
Figure 53
Required field not signed alert
4.4.4
Specifying a Post-Signing Action
JavaScript actions can be associated with a signature field so that an action occurs whenever the user
interacts with the field in some predefined way. However, documents are usually signed to protect,
guarantee, and or attest to the signed content. Signers usually want to know that the document they are
seeing is the document they are signing, and document recipients usually need to know that the
document they are viewing is the same as the document that was signed. For this reason, adding actions
to a signature field is inadvisable. Field actions change the underlying bytes of a PDF and could adversely
affect document security as well as content integrity.
Caution:
Using this feature is NOT recommended since such actions are contrary to the secure
and trusted nature of most signing workflows. Adding actions will result in a legal
warning about the legal integrity of the document.
To associate an action with a field.
1.
Create a new field.
Note:
For existing fields, place the form in edit mode by selecting
Forms > Add or Edit Fields
and then double click on them OR right click and choose
Properties
.
2.
Display the Action tab.