Using Triggers to Handle Events
Each time a document is signed, sent out for signature, rejected or approved, an event is generated and the corresponding record is updated. You can use a trigger to listen for these updates and take a specific action. For Example, you could set up a trigger to watch for a record's agreement_status changing to SIGNED, at which point you could automate an email to a 3rd party (note: all signing parties are automatically notified of this event via Adobe© EchoSign©).
List of Possible States of Agreement Status
| Value | Description |
|---|---|
| OUT_FOR_SIGNATURE | The document is currently waiting for one or more parties to sign it. |
| OUT_FOR_APPROVAL | The document is currently waiting to be approved. |
| WAITING_FOR_REVIEW | The document is currently waiting to be reviewed. |
| SIGNED | The document has been signed by all the requested parties. This is a terminal state. |
| APPROVED | The document has been approved by all requested parties. If the document has both signers and approvers, terminal status will be signed. |
| ABORTED | The signature workflow has been cancelled by either the sender or the recipient. This is a terminal state. |
| WIDGET | The status for the user's widgets. This is a terminal state. |
| EXPIRED | The document has passed the expiration date and can no longer be signed. This is a terminal state. |
Learn More:
- What are Electronic Signatures
- Electronic Signature Profile Settings & Options
- Collecting Signatures via Embedded/Widget Mode
- Using a Trigger to initiate the Signing Process on Update
- Placing Signature (text Tags) with Dynamic PDF's
- Placing Signature (text Tags) with PDF Forms
- Generating PDF Documents
- Cancelling a Document
- Manually Sending a Reminder to Sign
- Viewing a Documents Audit Log or PDF
Have more questions? Submit a request
Please sign in to leave a comment.
0 Comments