Completion Certification

Configuration - Certificate of Completion

Following installation, the module requires specific configuration within DRTE and Salesforce Setup.

Step 1: Create the Certificate of Completion Document Template

• Navigate to the Rich Text Button/Document Templates Tab.

• Create a New Document Template record and name it "Certificate of Completion."

• Save the record.

Import the JSON Template:

• Open Setup in a new tab, search for Static Resources, and locate the CertificateOfCompletionDocumentSectionsJSON JSON file (this file is bundled with the managed package). Download this file.

Return to the newly created Document Template record.

• Utilize the Import functionality to upload the downloaded JSON file.

Upon successful import, refresh the page. The pre-defined document sections will now be visible.

Customize Placeholders: Review each section and modify the static text placeholders as necessary to meet organizational branding and requirements.

Step 2: Configure DRTE Allowed Objects

This step ensures the DRTE query engine can access the relevant e-signature log data for certificate generation.

1. In Setup, search for Custom Metadata Types.
2. Locate and manage the records for the DRTE Allowed Object custom metadata type.

Create two new records to include the following objects:

• pscdnyrichtext__ESignature_Log__c
• pscdnyrichtext__ESignature_Request__c

Step 3: Configure DRTE Settings - Custom Setting

• Navigate to Setup, search for Custom Settings, and manage the DRTE Settings record.

Populate the following fields with the required values:

• CertificateOfCompletionTemplateId: Enter the Salesforce ID (e.g., a01XXXXXXXXXXXXXXX) of the "Certificate of Completion" Document Template record created in ‘Configuration’.
• CertificateOfCompletionDocumentPrefix: Provide a unique text prefix (e.g., COC-) for the generated document's generic ID.

Step 4: Create and Implement the Generation Action (Manual Way)

An action is required to trigger the flow that generates the COC document on the relevant record page.

1. In Setup, go to Object Manager and select the object on which your E-Signature workflow is enabled (e.g., Opportunity, Contract).
2. Navigate to Buttons, Links, and Actions.
3. Create a New Action:

• Action Type: Flow
• Flow: Select the packaged flow named Save Completed Documents To Files.
• Label/Name: Choose a descriptive label, such as "Save Signed Document To Files"

Add Action to Page Layout:

• Edit the Page Layout(s) for the target object.

Add the newly created Action to the Salesforce Mobile and Lightning Actions section of the record's Highlight Panel.

Configuration - Automatic Signed Document (w/CoC) Creation after Signature

Step 1: Create a new Trigger Flow on E Signature Request Object. 

Trigger the Flow when record is updated, Set Entry Condition “isSigned” equal to “TRUE”. Only When Record Is Updated to Meet the conditional requirements

Step 2: Query Related E Signature Log (Child Record)

Use Get Records element and query as shown in the screen shot below

Step 3: Create a packaged platform event record.

To trigger the functionality to generate Signed Document with CoC and attach to related document record.

(Imp: You may set Trigger Send Email equal to True, to send automatic email to related contacts/signees with signed document)

Step 4: Configure the scheduled path for this functionality.

This object holds critical functionality for e-signature request generation and handling the response after signature. To make sure your custom code doesn’t hinder e-signature native functionality, move the logic to Async Processing (as scheduled path shown below)

Manual- Certificate of Completion

Once configured, the Certificate of Completion generation process is straightforward for the end-user.

• Trigger Generation: On the record where the e-signature workflow was executed, the user clicks the action button (e.g., "Save Signed Document") located in the highlight panel.

• Validation: The system will display the Certificate, allowing the user to validate that all signer, document, and signature information is correct.

• PDF Generation: The user proceeds to generate the completed PDF, which bundles the signed document with the formal Certificate of Completion.

• Distribution: The generated document will be saved to the Files related list of the record. Users can then download this file or utilize standard Salesforce functionality to attach it to an email for distribution to the signer(s).

Troubleshooting - Certificate of Completion