Resco mobile apps can integrate with a third-party electronic signature provider DocuSign to create legally binding signatures directly in the app. This function is available from forms (if the record has an attachment that can be signed) or from mobile reports (including reports generated after an inspection).
Create a DocuSign account
You need a DocuSign account before you can start signing documents in Resco. DocuSign offers a free trial.
Configure DocuSign in Woodford
- Edit an app project in Woodford.
- Select Configuration from the Project menu.
- Switch to the Integrations tab, then scroll down to DocuSign
- Enable DocuSign: Set to true to display the DocuSign Connect option in the app’s Setup section.
- Use DocuSign sandbox: Use a sandbox environment when connecting to DocuSign services. Using this mode leaves a watermark on your documents.
- Docusign Integrator Key: DocuSign Integrator (API) Key, created in DocuSign Admin console.
- Docusign Secret Key: DocuSign Secret Key, generated under Integrator Key settings.
- Save all changes and publish the project.
Connect to DocuSign in the app
App users have to connect to DocuSign to start signing documents.
- Tap Setup or Settings on the home screen.
- Scroll down to Account > DocuSign, tap Connect, and log in to your DocuSign account using your email address and password.
Signing PDF documents
You can sign any PDF document that is available as an attachment in the app.
- Open any PDF file attached to any entity record
- Select the eSignature command from the hamburger menu.
- Fill in the details of the signer. Optionally, tap the + button to add more signers.
- Tap the Sign command in the top right corner to initiate the signing via DocuSign.
- Drag and drop your signer’s signature into the document, then tap Finish.
After successfully signing, you will be redirected back to the application. The newly added signature(s) is now a part of the PDF file.
In DocuSign, an envelope is a container for documents that have to be signed.1 We can store the envelope ID with the target entity record. If the target entity (for example, work order, appointment, or questionnaire) contains a field containing the text "DocuSignEnvelopeID" (case-insensitive), it is automatically filled with DocuSign envelope server ID.
The ID can serve as a direct link between the CRM document and DocuSign Inbox. It can be used as an indicator that a document was signed. It allows further workflows like forcing documents to be signed before the entity is saved.
Configuring report templates
When signing a random PDF, each signer can position the signature to a random location on the page. With mobile reports, you can add signature fields to report templates to determine their location on a page.
To add a new signature field:
- Edit a report template in the Report Designer.
- Click Add Signature. The signature field can be placed wherever you need it: in the header, grid, or footer.
- As Label, use the word "Signature" and a number (e.g. "Signature1").
You can place more than one signature field on a report. Each of these fields indicates the order of report signers. For example, if 2 signature fields for 2 signers are defined, their names must be Signature1 and Signature2. With two signature fields with correct names available on the report, the application will automatically enable the flow for two signers.
Multiple signature fields with the same name can be also defined in the mobile report. In that case, all are assigned to the same signer. This is useful when a signer needs to sign the document in multiple places.
Reports are signed just like any other documents. When you start the eSignature command, the default number of signers equal to the number of Signature fields defined in the report template.
The app tries to prefill signer fields automatically:
- The app searches for entity fields containing the word "signer". If found, these are assigned to signature fields (alphabetically sorted).
- If no such fields are found, the possible signers are the people who were the last to modify, own, or create the record.
In other words, if there are lookup fields on the report's source entity pointing to User, Contact, or Account entity that contain the phrase “signer” in their name, Resco extracts and prefills the Name, Surname, and Email from the related record. If such lookups don’t exist, Resco tries to prefill the values from OwnerId, ModifiedBy, or CreatedBy.
You can also change the prefilled signers if needed, remove them, or even add more signers, just like for any other PDF document.
On Android and iOS devices, you can also sign documents without internet access. You can enable this option in Woodford configuration.
- Use offline signing: Prefer offline signing mode for DocuSign service. The app will try to use a cached offline token for signing documents. If not available, online signing is used.
- Submit signature immediately in offline: Try to submit signature to the DocuSign server immediately even in offline signing mode. When you turn this off, signature submission is performed during synchronization.
The access token required for offline signing is valid for a limited duration (8 hours by default). When it expires, the app will try to contact DocuSign servers for a new token. The token is also renewed during a synchronization.
When you use offline signing and immediate submitting is disabled or fails, the document including signatures is submitted during synchronization. The information about this process is also available in the sync log.
<DocuSign Signed='1' TotalTime='9500ms' />
Documents waiting for signing
One of the storage analyzer reports offers insight into technical details about the documents waiting to be signed. This kind of information can be useful for Resco support when investigating problems.