Gonexa University
Gonexa University

Advanced training


The Gonexa Sign solution allows you to send an electronic signature without leaving the Salesforce environment.

Sign interactions and fillable fields

Retrieve data entered at the time of signing to insert it into Salesforce fields or only into the signed document

Prerequisites

BEFORE STARTING
  • Gonexa Sign installation and configuration
  • Creating a Gonexa Sign document template with a signature location
  • Get permission set Gonexa Sign Admin
  • Have at least package version 2.10

Sign interactions

Interactions give the recipient the ability to complete information at the time of signing and then sync that data into Salesforce.

On a document template, the objects on which interactions are possible are as follows:
  • The main purpose of the document template: for example “Opportunity”
  • The parent object of the main object: for example the opportunity account
  • Secondary objects configured on the document template

Before setting up your interactions, check the compatibility of field types according to your signature level:
💡 Note, however, that it is possible, for the certified signature, to use a text-type interaction for a Salesforce field such as a number or currency.

Place one or more interaction tags in the document

STEP #1
Build your Word template with the signers as desired, and add the interaction tags that look like this:
  • Open the Assistant and find the field you want to add an interaction for
  • Click on the 3 dots, select “Create an input field”, choose the recipient concerned and click on Copy
  • You can then paste the tag where you want it on your document.

Set up interactions

STEP #2
Once all interaction tags have been added to your document, upload them to Salesforce.

The document will then be scanned to identify all the interaction tags. You will find the interactions identified in the “Interactions Configuration” component in the Sign tab of the document template.

Here you'll find the Salesforce field label, interaction tag, recipient, and field type.

It is possible to personalize each interaction via the arrow at the end of the line:
  • Name : Named by the field label in Salesforce by default, but can be customized. This will be the information that will be visible to the signatory when filling in the data
  • Help text : add an instruction here to guide the signatory in completing the data
  • Required : check this box if the required information must be filled in by the signatory to sign the document
  • Is Autofilled : check this box if you want to pre-fill the field of the generated document with the data found in Salesforce
    ⚠️ Attention: this option is only available for non-certified signatures.
  • Auto update : check this box if you want the information entered by the signatory at the time of signing to be automatically updated in the associated Salesforce record, without prior verification by the user
  • Width : adjust the width of the field to be displayed in the document
  • Row amount : Adjust the number of lines to be displayed when the signatory enters information
  • Max length : adjust the maximum number of characters expected

Generating and sending the document for signature

STEP #4
Once the document is generated, it can then be sent for signature via the standard component or via a flow.

At the time of signing the document, the signatory is invited to fill in the requested information and to sign the document.

From the recipient object, you will find the “Data Update” component that displays the information entered at the time of signing, and allows the sender to accept the changes or to archive them.

💡 Consider dragging and dropping the Gonexa - Listing Recipients custom Lightning component onto the context object page to have quick access to the filled data and validate the sync quickly.


From the recipient, it is possible to:
Accept
  • Accept bulk changes by selecting the lines via the checkboxes and then clicking the “Accept change” button. This action will update the data in the designated fields in the designated objects with the “New Value” values present on the rows
  • Accept a change individually by using the arrow on the required line, by clicking on the “Accept modification” action. This action will update the data in the designated field in the designated object with the “New Value” present on the line
Archive
  • Archive changes in bulk by selecting the rows using the checkboxes and then clicking on the “Archive selection” button. This action will put the designated lines into the “Archived” status.
  • Archive a modification individually using the arrow on the required line, by clicking on the “Archive” action. This action sets the designated line to the “Archived” status
Reinitialize
  • Reset a change by using the arrow on the required line, by clicking on the “Reinit” action. This action is only available if the line is in the “Updated [Manual]” or “Updated [Auto]” status. It will allow you to update the data in the designated field in the designated object with the “Old Value” present on the line, this value is the value that was present in the field before the update

Meaning of statutes

  • Updated [Auto] : This status indicates that the value entered by the signatory when signing the document was automatically inserted into the designated field of the designated object, as soon as the document was signed
  • Updated [Manual] : This status indicates that the value entered by the signatory when signing the document was accepted by the user and therefore inserted into the designated field of the designated object
  • Archived : This status indicates that the value entered by the signatory when signing the document was not accepted by the user but that it was processed
  • Pending : This status may indicate two different cases. Either the signatory has not yet signed the document, or the value entered by the user when signing has not yet been processed
  • Error : This status indicates that an error occurred while updating the designated field of the designated object with the value entered by the signatory. In this case, there is a help text showing the error that occurred

Fillable fields

You can add check boxes, dynamic text boxes, or even statements to be filled in by the signatory before signing the document, either mandatory or optional.
This information will be added to the document after it is signed, and there is no data in Salesforce fields.

Add a mention
  • From the Assistant, access the signer on which you want to add fillable fields
  • Access the “Mention” block
  • Personalize the text to your liking or keep the mention Read and Approved on %date%, which will show the date of the day of signature
  • Copy the tag and paste it into your document where you want

⚠️ Be careful not to cut the tag on two lines

Add a checkbox
  • Go to the “Checkbox” block
  • Give the check box a title
  • Copy and paste the tag into the document where you want

💡 Note that you can add a written mention in your document for the understanding of the signatory

⚠️ Be careful not to cut the tag on two lines

Add text
  • Go to the “Text Field” block
  • Give the text field a title
  • Then copy and paste the tag created in this way into your document template.

⚠️ Be careful not to cut the tag on two lines

Note that the data entered in these fields will only be visible in the signed document. Salesforce records are not updated
If you need to collect data to update a Salesforce record, go to The article dedicated to Interactions