How can we customize the default document naming convention on the E-Signature Request object to follow a custom format (e.g., [Organization Name]_[Billing Company Name]_Contract) instead of the package default?

Published on October 3, 2026 DRTE

Customize the E-Signature Document Name Automatically with a Before-Save Flow

While the Document Name field on the E-Signature Request record is initially set during request creation, you can easily override it using a Salesforce Record-Triggered Flow (Before-Save / Fast Field Updates) before the document is generated or sent to recipients.

Why Before-Save? Because a Before-Save Flow executes prior to committing the record to the database, it updates the Document Name field seamlessly without requiring custom code or triggering additional DML operations.

Step-by-Step Implementation Guide

Step 1: Create a Record-Triggered Flow

Flow Setting	Value
Object	`E Signature Request`
Trigger	A record is created or updated
Entry Conditions	None (or set to run when `Document Name` is populated)
Optimize the Flow for	Fast Field Updates (Before-Save / Before Insert & Update)

Step 2: Create a Naming Formula Resource

In the Flow Manager, create a new Formula Resource (Data Type: Text) that dynamically constructs your target file name.

Formula Syntax Example:

{!$Record.pscdnyrichtext__Account__r.Name} & "_" & {!$Record.Billing_Company_Name__c} & "_Contract"

(Adjust the field API names to match your specific Salesforce object structure).

Step 3: Assign the Formula to Document Name

Add an Update Records / Set Field Values step (or Assignment element) with these values:

Setting	Value
Target Field	`Document Name` (`pscdnyrichtext__Document_Name__c`)
Value	`{!fx_CustomDocumentNameFormula}`

Note: the formula example uses sample field API names. Adjust them to match your specific Salesforce object structure before activating the flow.

Knowledge Article Number: KA-00443