Our e-signature application allows users to send out legally binding documents based from leads and loans. By making use of third-party providers, we can easily send documents to specific people, track its progress and perform actions based on signing activity. We have made the application as generic as possible, allowing our clients to decide which providers they want to use.
This documentation serves to explain the application’s setup and features.
Contents
Setup e-sign account
Navigate to the E-Signatures application.
Find and click on the E-Sign Accounts menu item.
Click on the create button.
You will be greeted by the following screen. Note that all highlighted fields are required.
Select the appropriate Provider. If they require additional fields, the form view will be populated with them. The screenshot illustrates what Eversign’s form view looks like as an example.
Note that the application requires the appropriate connector modules to be installed for the provider you want to use.
6. Populate the empty fields as indicated by the required highlighting and click Save.
Some providers might require additional steps. Refer to the next section for these instructions.
Additional account setup required
Eversign
The required fields for Eversign can be found on the API dashboard after you’ve registered a new app. The name of the fields on our side match the name of the fields on theirs.
If the environment is meant for testing, check the Sandbox Mode checkbox. This will ensure any documents sent are not legally binding.
After clicking Save, click on the Authenticate button. This will take you to Eversign’s interface for authorizing TaskFlow. Allow us authorization and you should be greeted by a message telling you “Successfully authenticated with Eversign.”
Creating e-sign documents
Navigate to the E-Sign Documents menu item.
Click on the Create button.
Select a provider account you have set up.
E-sign documents are provider-specific, i.e. you can not use the document configured for one provider on another.
4. Select the model that the document should be applied on. At the moment, you can choose between a Lead or a Loan.
5. Select the report type to link to this document. ODT Template refers to uploading your own .odt file and specifying the fields that are defined within it. This is the option you should generally choose. Pre-defined QWeb Template refers to an existing report template and can be used for testing purposes.
6. If you’ve selected ODT Template, the following section will appear:
Here, you should define the max amount of signers. Generally, this is the amount of signers you will need to sign the document. Some providers (such as Eversign) will allow you to submit less signers than indicated by the hidden tags.
7. Click on the Add Field button to start defining fields.
The following options are available:
Signer No - the nth signer who needs to sign this field.
Type - the field type, which is dependent on provider
Required - whether or not the signer should be forced to fill in this field
Field Height & Field Width - the field’s size (in pixels)
When selecting the field type as Text, the following extra fields will become available:
Placeholder - hint text that will be removed as soon as the user starts typing
Pre-Filled Value - text to pre-fill (i.e. the signer will have to delete the text if they want to replace it)
Validation to Apply - applies letters only, numbers only or email validation to the field, as selected
Once you’ve finished setting up the field, click on Create and it will be added to the list along with its hidden field definition:
If you need to copy the hidden tags into your .odt file, click on the View Tags button to get a view of all of the fields.
8. Upload your file using the Upload ODT File button.
9. Additional configuration options are available:
Communication Configurations - text that will be displayed to the signers in the email communication they receive.
Requester Name - Name of the origin of the signature request.
Title - Title of the signature request.
Message - A custom message to display to the user along with the link to the provider.
Automation - Automated actions (ir.server) that can be linked to each event on the signature request.
Some events might trigger multiple times per actual event. This needs to be accounted for in your server action.
0 Comments