Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Handling Dynamic Signers in S-Sign Enabled Templates

This guide explains how to configure S-Sign templates to handle a variable number of signers by leveraging automation to generate profiles and signature fields based on record data.

1. Using Conditional Logic

The S-Docs Render Feature allows you to show or hide signer profiles and input fields based on specific conditions in your Salesforce data.

  • How it works: Wrap your signer tags in `` statements. Entire Statement must be wrapped in double square brackets: [[EXAMPLE]]

  • Example Use Case: Require a "Secondary Signer" only if the Opportunity Stage is 'Closed'.

  • Key Syntax Example:

    <!--RENDER='{{!Opportunity.StageName}}' == 'Closed' -->
[[SSIGN_PROFILE Email='signer2@example.com' ProfileName='Signer 2' RoutingPosition='2']]
[[SSIGN_INPUT Profile='Signer 2' Type='Signature']]
<!--ENDRENDER-->

Available Signer Profile Attributes

  • ProfileName

  • Email

  • RoutingPosition

  • DenyAudit

  • DenyConfirmation

  • SignerName

  • PrevSignerProvidesThisSignersEmail

  • denyConfirmationEmail (None, Partial, Complete, or Both)

Avaiable Input Field Attributes

  • Type

  • Profile

  • Required (Type='Text', Type='Checkbox', and Type='Date' only)

  • WriteTo (Type='Text' and Type='Date' only)

  • TextDefault (Type='Text' only)

  • Disabled (Type='Date' only)

  • DateFormat (Type='Date' only)

2. Using Related Lists (LineItemsSOQL)

This method is best for scenarios where you need a signature from every person in a related list (e.g., all Contact Roles on an Opportunity).

  • How it works: Use LineItemsSOQL to query a list of people and loop through them to generate unique signer profiles.

  • Scaling: It automatically handles 1, 5, or 50 signers without manual updates.

Implementation Strategy

To use this, you typically create two SOQL statements:

  1. Profile Generator: Creates the invisible [[SSIGN_PROFILE]] tags for each person.

  2. Input Generator: Creates the visible [[SSIGN_INPUT]] (signature boxes) in the document body.

Example Configuration (Conceptual):

PreviousHow to: Generate various inputs using Component TemplatesNextHow to: Write back to a Salesforce Record using S-Sign Input Fields

Last updated

Was this helpful?