CT Sign Description and Deployment

Here you can find the CT Sign solution description and a step-by-step guide to configure your Salesforce organization.

CT Sign

CT Sign is provided as two connected components:

  1. The CT Sign managed package.

  2. The Application Service, also known as the CT Sign app, is intended to connect with the e-signature provider.

  3. The native CT Mobile app for iOS and Windows with added CT Sign module.

    CT Mobile Android does not support the CT Sign module.

  4. An e-signature provider.

    CT Mobile Windows does not support the integration with e-signature providers.

The following scheme covers the case of using a legally binding signature. When using simple signing, data exchange only takes place between the mobile device and Salesforce.

CT Sign Architecture

CT Sign Package Description

Available for the following Salesforce editions: Enterprise, Unlimited, Force.com, Developer, Performance.

UI Tools

  • CT Sign Control Panel is a tool to provide clear and convenient UI to connect the Salesforce organization with the Application Service and e-signature provider;

  • Template Editor is a tool for creating and configuring templates that will be used to form documents based on Salesforce data.

Custom Objects and Fields

There custom CT Sign fields on the Contact and User objects, such as ctsign__CompanyName__c, ctsign__ContraliaIdentityID__c, and ctsign__ContraliaIdentityPIN__c are no longer in use.

  • Sign Settings is intended for template access management and to store the main CT Sign settings, such as objects to sign and layouts for the Form Document page.

  • Sign Document is intended to store the statuses of the outgoing transaction with the attached document being signed.

  • The custom fields of the standard Content Version object are intended to store the attributes of the templates for documents being signed and to send them as document parameters.

  • The generated documents are saved as files to allow users to attach the same document to different records. Until a transaction (a Sign Document record) receives a successful completion status, the document is attached only to this transaction. Next, the document is additionally attached to the record from which the signing process was started.

  • The Signing Contact field is used as a link between Account and Contact who should sign the generated document.

Custom Setting

  • The protected Sign Credentials custom setting is intended to store the Application Service credentials. To fill out the custom setting, the system uses the custom web service. Users have no access to this custom setting.

Components

  • Apex classes:

    • TemplateEditorCommonController

    • TemplateEditorController

    • TemplateObjectsSetting

    • TemplateSelectionAuraController

    • ApplicationConnectorRest

    • Batch_DocumentSender

  • Apex triggers:

    • SignDocumentProcess

  • Visualforce and Lightning components for UI Tools.

  • Web service to get authorization data of the Application Service.

  • * Custom Labels to provide multilingual support.

CT Sign Package

Application Service and e-Signature Provider

Users can add handwritten signatures to a document without additional integration.

To use a legally binding e-signature, connect the Salesforce organization with the installed CT Sign package, the Application Service, and the e-signature provider.

  • Application Service, provided by the Customertimes team, is used as a third-party service to connect your Salesforce org or CT Mobile app with an e-signature provider for sending and receiving transactions and signed documents.

  • As the e-signature provider, each customer should prepare the DocuSign account to connect with the Application Service and Salesforce organization.

    1. Create the developer account with the configured DocuSign app and the enabled DocuSign Connect to test the e-signature process.

    2. Obtain the production account and go live with the DocuSign app to allow the legally binding signing.

Deployment Steps

Users may sign documents with legally binding or simple signatures in Salesforce and on a mobile device. Depending on the purpose and the platform of a mobile device, skip the unnecessary steps, for example, if there is no need to give iOS users the ability to sign documents with a legally binding signature.

Deployment of CT Sign solution is performed in the following order:

  1. Install the CT Sign package in your Salesforce organization and assign the CT Sign license to the users.

  2. Configure the main parameters of the CT Sign package: objects to sign, libraries to store documents, and layouts for a forming document page.

  3. Create templates for contracts, e-mails, or any other form.

  4. Set up the DocuSign integration if needed.

    1. Connect your Salesforce organization with the Application Service and DocuSign account.

  5. Form and sign documents with legally binding or simple signatures in Salesforce.

  6. Add the CT Sign module to the CT Mobile app for signing documents in the CT Mobile app.

  7. Form and sign documents with legally binding or simple signatures on a mobile device.

``