Gonexa University
Initial training
Advanced training
Français
English
Contact Support
Gonexa University

Advanced training


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

Automate signature sending

Accelerate the process of sending for signature with an automated process

Prerequisites

BEFORE STARTING

💡 Find all our feeds in our Flow Org

  • Have a document template
  • Have done the configuration for sending by simple signature
  • Have to test the model well before sending a simple message before sending via Flux

Initializing the flow

STEP #1
  • In the configuration, create a Screen Flow
  • Name it properly according to your company's naming rules
  • Create a “recordId” variable available at the input if you want to do a screen flow

💡 You can make a flow that generates and sends for signature or simply that sends for signature depending on what you want to do. Here, we are going to explain a complete generation and sending flow

Generating the document

STEP #2
  • Add an item to your Apex Action flow
  • Select the “Generate a Document” action: apex-gnc__DocumentGenerationInvocable
  • Name it “GenerateDocument”


Fill in the following 3 items:

  • Output format : “pdf”, “xlsx”, “pptx” or “docx” (to be hardcoded or dynamically according to your choice)
  • Record Id : retrieve the Salesforce ID of the departure record here. For example, use the “recordID” variable created at the start.
  • Template Id : get the Salesforce ID for the document template of your choice here. For example, you can display a selection list on the first screen and use here the Id of the template chosen by the user.

Get the generated document

STEP #3
  • Add a Get Record item to your feed.
  • Enter a label and an API name.
  • Choose the “Document template log” object


Filter records using the following criteria:

  • Champ : Id
  • Operator : equal to
  • Value : equal to “GenerateDocument” text (Name of the Apex Action done previously)

Creation of the recipient

STEP #4
  • Add an item to your Action flow.
  • Select the “Create a certified recipient” action: APEX-GNX__certifiedRecipientInvocable.
  • Enter a label and an API name: for example “createRecipient”.


Fill in the following 2 elements:

  • Contact, User or Lead Id : you must indicate the Salesforce ID of the Contact, User or Lead who will receive the document as a signature. For example, you can put a search field in the start screen or search dynamically for the right record.
  • Recipient Order : fill in the order of the signatory, for example “1"
  • Advanced signature : if you want to do advanced signing for this signatory, activate this parameter and enter the value “true”. Make sure you have subscribed to the advanced signature or contact your sales contact
  • New transaction: In the drop-down menu at the bottom “Show advanced option”, check the box “Always start a new transaction”

Creation of collection variables (Contact + Recipient)

STEP #5
Create a new resource
  • Resource type : Variable
  • API name : “ContactCollection”
  • Data type : Text
  • Check the “Allow multiple values” box

Create a new resource
  • Resource type : Variable
  • API name : “RecipientCollection”
  • Data type : Text
  • Check the “Allow multiple values” box

Assign values to the variables created

STEP #6
Add an “Attribution” element

In the first line of attribution
  • Variable : ContactCollection
  • Operator : Add
  • Value : Signatory Contact Id

Add a second line in the attribution with:
  • Variable : RecipientCollection
  • Operator : Add
  • Value : “CreateRecipient” text

Create the delivery

STEP #7
  • Add an item to your Apex Action flow
  • Select the “Create a certified delivery” action: APEX-GNX__certifiedDeliveryInvocable.
  • Name it “CreateDelivery”

Add an “Action” element:
  • Collection of Contacts Ids : the collection variable “ContactCollection”
  • Collection of Recipients : the “RecipientCollection” collection variable
  • Content Document Id : The id of your document via “Get Generated Document”
  • Name : enter a name, for example “Signature procedure”
  • Collection of Content Version Ids : you can activate this setting if you want to send multiple documents in the same procedure. Then fill in the collection variable where you will have previously stored the IDs of the versions of content to be signed.
  • Document Template Id: the Id of the document template used. This value is not mandatory but it is strongly recommended that you fill it in for the correct functioning of the signature message.
  • New transaction: In the drop-down menu at the bottom “Show advanced option”, check the box “Always start a new transaction”

Save, debug, and activate your flow.

Don't forget to add a flow component to the lightning page of your choice.

💡 For more examples, check out our Flow Org