advertisement
A
PPENDIX
A – S
AMPLE
C
ONTRACTS FOR
E-S
IGNING
The best way to have a hassle-free user experience of the DocuSign Integration is for the administrator to prebuild standardized Print Templates in Agiloft with the necessary DocuSign tags. Once print templates for your various contract types have been created in Agiloft, the e-signing process becomes both simple and automated.
To assist you with your DocuSign setup, an abbreviated contract document is provided here. The next two pages will be the first and last pages (pages 1 and 6, respectively) of a sample Agiloft contract. The first page shows some standard “$” metadata tags and the next page shows the signing page for the contract, which was set up for one internal signer (Agiloft) and two external signers (ABC Electronics).
Note that the “$docusign:<type>:<field name>:<role name>” tags on this signing page are “invisible”
(i.e., font color = white). All tags added to documents should be in white font, because the entries made by the Signers are simply placed “on top of” these tags. The tags are anchored to the location on the page where the data will be displayed, but they need to be invisible on the document. If the
$docusign:xxx tags are visible in the document, they will remain visible after DocuSign has inserted their signing icons (e.g., “Sign Here”, etc.)
The page after the example template shows that same signing page with the $docusign:xxx tags made
“visible” (i.e., font color = black). You can also view any $docusign:xxx tag by selecting the tag area and then hovering over the “font color” icon as shown below:
Figure 55 - Using Color to see Tags
Note that this two-page contract is an example only, and of course you can create any type of signing block(s) you wish.
74
AGILOFT CUSTOMER SUPPORT AGREEMENT – Sample
This Agreement is between Agiloft, Inc., a California Corporation, (“Provider”) whose principal place of business is
460 Seaport Court, Suite 200, Redwood City, CA, USA 94063 and $company_name, located at $street_address,
$city, $state_province $zip_or_postal_code (“Customer”).
This Agreement supplements the End User License Agreement for Agiloft and hereby incorporates the limitations of liability and general provisions of that Agreement. The Customer has purchased the standard annual support/upgrade contract for its license of Agiloft.
1. INTRODUCTION
This Agreement covers standards for the provision of software support and upgrades by Provider to Customer, in connection with that End User License Agreement dated as of $contract_start_date between Customer and
Provider (the "License Agreement"). This Agreement terminates on $contract_end_date, and may be renewed for additional twelve-month periods.
In accordance with the License Agreement, Provider has granted to Customer a license to use the Licensed
Software (as defined in the License Agreement). Customer will operate the Licensed Software at its location in
$city, $state_or_province (the "Customer Facility", which shall include any other location to which Customer may move its operations center in the future).
Customer has purchased licenses for both staff users (“Staff User”) (typically, technicians and other high-level employees) and end users (“End User”) (typically external customers and internal end users).
2. SUPPORT AND UPGRADE SERVICES
2.1 SCOPE OF SERVICES a) The following are the Support and Upgrade Services that will be offered by Provider in connection with the Licensed Software:
Provider shall:
(i) develop and provide corrections, changes, or workarounds ("Corrections") for any defects, errors, or malfunctions in the Licensed Software (collectively, "Defects"), discovered by Customer or Provider, on a timely basis, given the nature and scope of the Defect;
(ii) provide to Customer all improvements, modifications and enhancements to the Licensed
Software which Provider shall make from time to time and which Provider makes available to its Customers generally in the form of new releases; and
(iii) provide Customer with any upgrade releases ("Upgrade Releases") to the Licensed Software and all new Versions and Releases of the Licensed Software, which Provider makes available to its Customers generally; provided, however, that if any such Version or Release contains significant new or improved functionalities, Provider shall have the right to make such Version or Release available to Customer only upon the payment of additional license fees, or upon such other terms, as the Provider requires of its Customers generally therefor.
[Contract page 1 is above; (Contract pages 2-5 are deleted); Contract page 6 is below]
75
f) This Agreement may not be assigned by either party except in connection with and under the circumstances permitted under the License Agreement. Subject to the foregoing, this Agreement will be binding on the parties and their respective successors and permitted assigns. g) This Agreement may be signed in one or more counterpart copies, all of which together shall constitute one Agreement and each of which shall constitute an original.
IN WITNESS WHEREOF, the parties of $docusign::contract_title:InternalSigner
Agiloft
Signature: $docusign:SignHere::InternalSigner
Name: $docusign:FullName:internal_signer_full_name:InternalSigner
Title: $docusign:Title::InternalSigner
Date: $docusign:DateSigned::InternalSigner
$company_name
Signature: $docusign:SignHere::Customer1
Name: $docusign:FullName:party1_signer_full_name:Customer1
Title: $docusign:Title::Customer1
Date: $docusign:DateSigned::Customer1
Signature: $docusign:SignHere::Customer2
Name: $docusign:FullName:party2_signer_full_name:Customer2
Title: $docusign:Title::Customer2
Date: $docusign:DateSigned::Customer2
[Contract signing page 6 above, with “invisible” tags]
[This is what should get sent to DocuSign]
[The same page with these tags made “visible” is below]
76
f) This Agreement may not be assigned by either party except in connection with and under the circumstances permitted under the License Agreement. Subject to the foregoing, this Agreement will be binding on the parties and their respective successors and permitted assigns. g) This Agreement may be signed in one or more counterpart copies, all of which together shall constitute one Agreement and each of which shall constitute an original.
IN WITNESS WHEREOF, the parties of $docusign::contract_title:InternalSigner
Agiloft
Signature: $docusign:SignHere::InternalSigner
Name: $docusign:FullName:internal_signer_full_name:InternalSigner
Title: $docusign:Title::InternalSigner
Date: $docusign:DateSigned::InternalSigner
$company_name
Signature: $docusign:SignHere::Customer1
Name: $docusign:FullName:party1_signer_full_name:Customer1
Title: $docusign:Title::Customer1
Date: $docusign:DateSigned::Customer1
Signature: $docusign:SignHere::Customer2
Name: $docusign:FullName:party2_signer_full_name:Customer2
Title: $docusign:Title::Customer2
Date: $docusign:DateSigned::Customer2
[Contract page 6 above, shown with “visible” tags]
[Note: Do not send “visible” tags to DocuSign]
77
advertisement
advertisement
Table of contents
- 6 DocuSign Overview
- 6 Agiloft Certification by DocuSign
- 6 Agiloft Interface to DocuSign
- 7 Definitions
- 9 E-Signing with Agiloft
- 10 Overview of the Agiloft/DocuSign E-Signing Process
- 10 General Description of the E-Signing Process
- 13 Create and Configure an Account at DocuSign
- 14 Configure Your KnowledgeBase for DocuSign
- 14 Set Up the DocuSign Users (at DocuSign)
- 17 Set Up the DocuSign Extension (at Agiloft)
- 19 Set Up the DocuSign Administrator
- 20 Define the DocuSign Server
- 20 Enable DocuSign Connect
- 21 Add the Remaining DocuSign Users
- 23 Deciding How to Store the Signers and Documents in Agiloft
- 24 Review/Configure DocuSign Envelope Creation Actions
- 24 The DocuSign Action Wizard
- 25 Set up the Recipients on the Recipients Tab
- 28 Create/Update Print Templates to Add DocuSign Tags
- 28 Agiloft Metadata Tags
- 28 Agiloft Metadata Tags for DocuSign
- 30 Example of Setting Up a DocuSign Contract
- 35 Signing Contracts Provided by External Parties
- 35 Contract Manager Manually Adds Tags in the DocuSign Interface
- 35 Signers Add Tags while Signing
- 36 Using a Preconfigured Signature Page Template
- 37 Procedures for Sending Documents to DocuSign
- 37 Steps for DocuSign Users (Senders)
- 37 1) Prepare the Contract Record
- 40 2) Create a DocuSign Envelope
- 44 3) Preview the Document at DocuSign to Check the Tags
- 48 Adding Tags
- 48 4) Send Out the Document for E-Signing
- 50 5) Monitor the E-Signing Process
- 52 6) E-Signing Completion
- 56 Procedures for E-Signing at DocuSign
- 57 Notification Email from DocuSign
- 59 E-Signing the Document at DocuSign
- 63 Self E-Signing a Document at DocuSign
- 65 Additional Functionality at DocuSign
- 65 Account Features at DocuSign
- 67 Dashboards at DocuSign
- 68 Email Notifications at DocuSign
- 69 Permissions at DocuSign
- 70 Reports at DocuSign
- 71 Templates at DocuSign
- 74 Appendix A – Sample Contracts for E-Signing
- 75 AGILOFT CUSTOMER SUPPORT AGREEMENT – Sample
- 75 1. INTRODUCTION
- 75 2. SUPPORT AND UPGRADE SERVICES
- 75 2.1 SCOPE OF SERVICES
- 78 Appendix B - DocuSign Tables and Fields in Agiloft
- 78 DocuSign Users Table
- 78 Automation
- 78 DocuSign Roles
- 79 DocuSign Envelopes
- 79 Automation
- 80 DocuSign Recipients
- 80 Changes to the Contracts Table