...
If the Contract Party Information section is not properly filled out and linked to records, a validation action warns the user to finish creating new records before generating the attachment. However, many other fields in a contract may also be referenced in the template, such as clauses and signing parties. For this reason, it's usually best to check that as many fields as possible are finalized before generating attachments from templates.
Creating contracts and attachments from inbound emails
...
The Select Files drop-down on the action bar is used to operate on multiple selected attachments to update the fields to the far right in the table view. Add or Remove for the Approval Packet sets the Include in Approval Packet field to Yes or No. Add or Remove for the E-sign Packet changes the To Be eSigned field to yes or no. And Set Status to Superseded sets the status for the selected attachment(s) to Superseded.
Tracking company documents and insurance certificates
...
Fields under the Signers heading are used to populate the signature page of the contract's print templates and to identify the signers for either esignature program. For this reason, these fields must be filled before generating an attachment from a template, which in turn must be generated and set as To Be eSigned before returning to the Signature tab to create esignature envelopes.
Before using either DocuSign or Adobe Sign, you will need to configure the integration by going to Setup > Integration and choosing the appropriate platform. For DocuSign, you must sign up for a Docusign account directly with DocuSign. For Adobe Sign, Agiloft can set up the account and allow you to purchase envelopes directly without any long term contract. See the sections on DocuSign and Adobe Sign below for more details.
...
Records in this table are owned by the contract Requester. Specifically, a record is owned by the user whose ID matches the number in the Requester ID field. By default, the Contract Requester is the user who created the contract record. For this reason, the owner of a contract record is often an end user Requester, rather than a power user Internal Contract Owner, despite the field name.
Automation
The Contracts table has several rules set up. Their actions have been described in the use cases above. Rules which are run based on a schedule (rather than those which are event-triggered) are identified by the prefix "TB", for time-based and are disabled by default.
...