Completion Certification

Published on February 10, 2026 DRTE



Configuration - Certificate of Completion

Overview: The Certificate of Completion (CoC) bundles the signed document with a formal audit-trail certificate. Following installation, the module requires specific configuration within DRTE and Salesforce Setup. This guide covers manual generation, automatic generation after signature, and troubleshooting.


Step 1: Create the Certificate of Completion Document Template

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

    Document Templates tab

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

    New Document Template named Certificate of Completion

  3. Save the record.

    Saved Document Template record

Import the JSON Template

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

    Static Resources - CertificateOfCompletionDocumentSectionsJSON

  2. Return to the newly created Document Template record and use the Import functionality to upload the downloaded JSON file.

    Importing the JSON file

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

    Imported document sections

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

    Customizing section placeholders

    Placeholder text example


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.

    DRTE Allowed Object custom metadata type

  3. Create two new records to include the following objects:

    • pscdnyrichtext__ESignature_Log__c
    • pscdnyrichtext__ESignature_Request__c

    Allowed Object record for ESignature Log

    Allowed Object record for ESignature Request


Step 3: Configure DRTE Settings - Custom Setting

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

    DRTE Settings custom setting

  2. 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 Step 1.
    • CertificateOfCompletionDocumentPrefix: Provide a unique text prefix (e.g., COC-) for the generated document's generic ID.

    Populated DRTE Settings fields


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 with these values:

    • 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"
  4. Add Action to Page Layout: Edit the Page Layout(s) for the target object and 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

  1. Trigger the Flow when a record is updated. Set Entry Condition "isSigned" equal to "TRUE", and run only when the record is updated to meet the condition requirements.

    Trigger flow entry conditions

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

  1. Use a Get Records element and query as shown in the screenshot below.

    Get Records for E Signature Log

Step 3: Create a packaged platform event record

  1. This triggers the functionality that generates the Signed Document with CoC and attaches it to the related document record.

    Important: You may set Trigger Send Email equal to True to send an automatic email with the signed document to related contacts/signees.

    Platform event record configuration

Step 4: Configure the scheduled path

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 the scheduled path shown below).

Scheduled path (async processing)


Manual - Certificate of Completion

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

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

    Action button in the highlight panel

  2. Validation: The system displays the Certificate, allowing you to validate that all signer, document, and signature information is correct.

    Certificate preview for validation

  3. PDF Generation: Proceed to generate the completed PDF, which bundles the signed document with the formal Certificate of Completion.

    Generating the completed PDF

  4. Distribution: The generated document is saved to the Files related list of the record. Download it or use standard Salesforce functionality to attach it to an email for the signer(s).

    Saved document in the Files related list


Troubleshooting - Certificate of Completion

Issue

Potential Cause

Resolution

Action button is missing.

Action not added to the Page Layout.

Ensure the action is added to the Lightning Actions in the Highlight Panel.

Certificate data is blank/incomplete.

Objects not added to DRTE Allowed Objects.

Verify that pscdnyrichtext__ESignature_Log__c and pscdnyrichtext__ESignature_Request__c have been correctly added to DRTE Allowed Objects.

Error upon button click.

Incorrect Template ID in DRTE Settings.

Confirm the 18-digit SFDC ID of the Document Template is accurately placed in the CertificateOfCompletionTemplateId field.


Knowledge Article Number: KA-00111

View more articles in the knowledge base