Gonexa University
Gonexa University

Gonexa WebDoc


The Gonexa solution to allow you to send your document via a consultation link, retrieve the data entered & obtain a non-certified signature

Configuring WebDoc interactions

Retrieve the data entered at the time of signing to insert it into Salesforce fields

Prerequisites

BEFORE STARTING

⚠️ Be sure to contact support if the licenses are not active for your environment.

  • Have installed and configured Gonexa WebDoc
  • Have created a Gonexa Doc document template
  • Have Gonexa Sign Admin set permission to set up interactions
  • Have at least the “Nice” version of the Package (July 2024)

Capturing data through interactions

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

The fields supported for WebDoc interactions are the fields of type text, checkbox, picklist, date and number.

On a document template, the objects on which interactions are possible are as follows:

  • The main object 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

Place one or more interaction tags in the document

STEP #1

Build your Word template with signers as desired, and add interaction tags from the Wizard

  • Open the Gonexa Wizard 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 “Interaction Configuration” component in the WebDoc 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
  • Pre-fill: check this box if you want to pre-fill the field of the generated document with the data found in Salesforce
  • Automatic 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
  • Adjust the size of the interaction and the number of characters expected

Add recipient tags

ETAPE #3

When the document is generated, the Gonexa interaction tags are visible on the document but disappear when it is sent for signature.

⚠️ The tag does not disappear during generation, but will no longer be visible when the signature is sent, so the signatory will not see the tags and can directly fill in the requested information.


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 signatory, 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
  • Update [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