Category

Release Notes

April 2024

By Release Notes

April '24 Generally Available Release

Elevate your document workflows with the April '24 S-Docs and S-Sign Release. Explore new enhancements focused on efficiency, security, and customization, demonstrating our dedication to continuously improving your user experience.

S-Docs Updates

Supercharge Your Workflow With Batch Generation

Generate hundreds of documents at once with the power of Batch 2.0. This new functionality extends the capabilities of the S-Docs SDK to include an alternative to Mass Merge (Legacy) that meets your batch generation use cases.

Note: Post generation actions for batch processing are currently in development and will be included in a future release.

Streamline Document Storage

Storing documents in external repositories just got easier and more secure. The new Document Actions Framework allows you to automatically send generated documents to credentialed external storage locations including Google Drive, AWS, and Microsoft SharePoint. Keep an eye out for future releases, where this new feature will enable teams to configure and automate post document generation actions for an even wider array of business needs.

Get Enhanced LWC Compatibility With Legacy Support

S-Docs Lightning Web Components (LWCs) allow you to generate, view, and send documents right from Salesforce records. Now, documents generated via legacy methods (The S-Docs button and S-Docs jobs) are displayed in the Generated Documents LWC.

Note: At this time, HTML file formats are not supported for display in the Generated Documents LWC. Additional post-generation functionality (preview, refresh, live edit, etc.) may be limited for legacy documents. Additional enhancements for these capabilities are planned for future releases.

S-Sign Updates

Sign Once To Seal The Deal

Signers can now sign and initial once to use those inputs across all signature and initial fields in an S-Sign document. Once added, signatures and initials can be applied to remaining signature fields by simply tapping or clicking on unpopulated fields. Signers can also easily redesign and re-adopt their signatures and initials at any time, further optimizing the signature user experience.

Simplify User Authentication

Signature experiences requiring user authentication now only require signers to enter their verification PIN code once per session, instead of once per document. This new feature implements a session-based cookie that is destroyed upon session end, meeting GDPR compliance requirements and offering a more streamlined user authentication flow.

February 2024

By Release Notes

February '24 Generally Available Release

The February '24 generally available S-Docs and S-Sign Release brings a host of new features and improvements that aim to provide more efficient, secure, and customizable document workflows. As always, we are dedicated to catering to the evolving needs of our users.

Note: See considerations for this release

S-Docs Updates

Simplify Admissions and More With Education Cloud Support

Support was added for using S-Docs with standard objects in Education Cloud, providing document generation that meets the unique needs of the education sector. Educational institutions can now leverage S-Docs’ powerful features to create student-centric experiences that foster positive relationships and long-term success.

S-Sign Updates

Set Up S-Sign Faster Than Ever

S-Sign no longer requires the Salesforce Connected App framework. This change greatly streamlines the S-Sign onboarding experience, improves security, and increases the overall performance of S-Sign.

Sign Smoother and More Securely In Experience Cloud

Authenticated Experience Cloud users can now sign documents directly in Experience Cloud with S-Sign. The entire signing process takes place within the Experience Cloud environment, allowing you to deliver seamless and secure agreement execution within your online portals.

Streamline Multi-Document Signature Workflows

This release eliminates redundant interactions and disconnected signing experiences for agreement workflows that require signatures on multiple documents. Experience a more streamlined and efficient process for consent, user authentication, and signing across multiple documents.

Meet Compliance Requirements With Electronic Record and Signature Disclosure (ERSD) Support

Support was added for displaying the Electronic Record and Signature Disclosure (ERSD) to signers on the S-Sign consent screen. This allows administrators to tailor S-Sign to meet GDPR and CCPA compliance requirements, and is available to configure in the S-Sign Custom Settings.

Set Custom Notification Email Templates with Template Names

Support was added for using template names to specify which custom notification, reminder, and expiration email templates should be used during the signing process for a particular S-Sign template, as an alternative to template IDs. This provides a more intuitive template building experience and improves the overall signer experience.

Release Considerations

Before upgrading to the February '24 S-Sign release, it is required to perform a patch upgrade if you are transitioning from the September '23, October '23, or November '23 versions listed below:

November 2023

By Release Notes

November '23 Generally Available Release

The November ‘23 Generally Available S-Docs and S-Sign Release delivers a range of stability improvements, performance optimization, and functionality expansion that aims to enhance the overall user experience. This release also includes the foundational development work necessary to build future functionality, in particular, diagnostic/instrumentation, feature flagging, and the removal of connected app dependencies that will be tested thoroughly and expanded on as part of the next major release, to be delivered in January. As always, we are dedicated to improving and expanding the capabilities of S-Docs to meet the evolving needs of our users. 

S-Docs Updates

Add Runtime Input To Documents In Lightning Web Components and SDK Document Generation

S-Docs Runtime Prompts collect and merge user input into documents during classic (non-LWC) document generation. Support was added for capturing and merging dynamic user inputs into documents generated using LWCs and the S-Docs SDK through Screenflows and Omniscript.

Use Document Options With The SDK

Comprehensive support was added for Document Options when generating documents through the S-Docs Software Development Kit (SDK). This includes enhanced functionality for related lists, screen flow inputs, special merge fields, and more.

Edit And Email Documents Via LWC Modals More Intuitively

Enjoy a smoother, more intuitive interface as you create and customize your documents with the revamped editing experience in both the live edit and email LWC modals. The new and an improved editing experience aims to increase efficiency and user satisfaction.

S-Sign Updates

Create Multi-Doc Signature Flows Via The S-Sign SDK

S-Docs now offers SDK support for multiple document signature flows. Configure and execute multiple signature documents through the SDK, further enhancing flexibility in managing document workflows.

Get A More User-Friendly PDF-Upload Component Experience With S-Sign

When using S-Sign enabled PDF-Upload component templates, you no longer need to use unique S-Sign input numbering across those PDF-Upload component templates. Seamlessly integrate S-Sign capabilities into document generation processes without the hassle of managing distinct input numbering structures.

October 2023

By Release Notes

October '23 Generally Available Release

The October ‘23 Generally Available S-Docs Release introduces a range of improvements to enhance the document creation and generation experience. This release aims to empower users with new capabilities and features, further aligning S-Docs with the evolving demands of document management within Salesforce.

S-Docs Updates

Allow Experience Cloud Users to Use Lightning Web Components

A new permission set is now available for Experience Cloud users, enabling them to use S-Docs Lightning Web Components (LWCs) seamlessly. This makes it easier for Experience Cloud users to generate documents while maintaining secure access.

Add Email Attachments via Lightning Web Components

Support was added for adding additional attachments from Salesforce directly to your emails prepared through LWCs, streamlining your document distribution process and ensuring that all relevant files are attached to your outgoing emails.

Select Templates More Seamlessly in Lightning Web Components

The template selection LWC has a new design that is more user-friendly and intuitive, making it easier for users to pick the right template for document generation.

Allow Experience Cloud Users To Email via Lighting Web Components

Experience Cloud users can now leverage S-Docs email capabilities through the LWC library. This enhancement extends document generation and email functionality to Experience Cloud users, improving the ability to reach and engage with a broader audience.

Use Special Merge Fields In The Lightning Web Component Email Module

Support was added for using special merge fields in emails sent from S-Docs LWCs to merge data about the document or generating user.

Make On The Fly Edits More Easily in Lightning Web Components

The Live Edit LWC editor was updated to provide a more universal and robust set of document editing capabilities, matching the user experience of the S-Docs template editor.

Control Lighting Web Component Feature Access

Fine-tune the actions and interactions end users have after generating documents, providing greater control over their experience and securing workflows. Support was added to enable or disable end-user access to Refresh Data, Delete, and View Version History for documents generated and displayed in the Documents LWC.

Gain More Flexibility When Displaying Related List Records via Components

Support was added for using <splitevery> for users leveraging Method 2 when merging related list records via components, offering more flexibility in component management and more options for structuring documents.

September 2023

By Release Notes

September '23 Generally Available Release

The September ‘23 Generally Available S-Docs and S-Sign releases usher in the next progression of operational efficiency for our customers, reflecting S-Docs’ commitment to innovation, usability, and security.

In this release, you’ll find:

  • Document Generation via Lightning Web Components (LWCs) - A major customer experience overhaul that significantly streamlines the document creation process
  • S-Docs & S-Sign Software Development Kits (SDKs) - Advanced tooling that allows admins to customize and simplify complex workflows for end-users
  • Product Security Enhancements - Including Salesforce Named Credentials for external storage integrations and a new minimum viable permission set for S-Sign

S-Docs Major Updates

Transform Your Document Lifecycle With S-Docs Lightning Web Components (LWCs)

The September '23 release marks the arrival of three new customizable Lightning Web Components, available in the Lightning App Builder:

  • Documents (S-Docs)
  • Generate Documents (S-Docs)
  • Generate Document SDK (S-Docs)

S-Docs LWCs allow you to generate, preview, email, edit, and manage document versions without leaving the base Salesforce record. This update accelerates productivity, accuracy, and user experiences while simplifying the document lifecycle.

Learn about configuring S-Docs Lightning Web Components in our Knowledge Base:

Key Benefits Of S-Docs LWCs

Streamlined Configuration For Salesforce Admins
Use an intuitive setup process through the Lightning App Builder to configure seamless document generation processes including effortless template selection, data mapping, and post-generation options - without relying on code or external tools

Conditionally Reveal Templates At The Right Time
Dynamically show templates based on record attributes or events to ensure accurate and contextually relevant document generation, and reduce manual intervention

Generate Documents With Ease
Experience lightning-fast document creation through the LWC interface without the need to navigate away from the base record

Seamlessly Send PDF Attachments
Accelerate communication efficiency by sharing data-rich documents directly from the base record

E-Signatures
Seamlessly integrate S-Sign e-signature processes into document workflows

Inline Edit Generated Documents
Empower users to make quick edits to static and data-driven elements in generated documents without leaving the base record

Refresh Documents With Updated Data
Keep documents up-to-date with the latest information by refreshing documents with new Salesforce data without regenerating or leaving the base record, ensuring accuracy & compliance

Customize And Simplify Workflows With S-Docs Software Development Kit (DocumentSDK)

Introducing the DocumentSDK, also referred to as the S-Docs SDK: an essential tool for developers aiming to streamline document generation and email creation within their organizations. This SDK empowers developers to effortlessly integrate document generation and email creation features into their applications.

If you’re interested in incorporating the DocumentSDK, contact your Customer Success Manager or S-Docs Support.

Increase Integration Security With Named Credentials

The September '23 release marks the shift from traditional credentialing methods to Salesforce Named Credentials for seamless and secure integration with popular external storage providers such as AWS S3, Google Drive, and SharePoint. This is a move that enhances the security and flexibility of external storage integrations.

Key Benefits of Named Credentials

Enhanced Security
With Salesforce Named Credentials, your external storage credentials are stored in a secure and encrypted manner, reducing the exposure of sensitive information. Salesforce's built-in security measures are extended to your external storage integrations, ensuring that your data remains protected.

Simplified Setup Process
With Named Credentials, you can now configure external storage integrations through a user-friendly interface within Salesforce Setup. This intuitive process minimizes the potential for configuration errors and speeds up the integration process.

Centralized Credential Management
Gone are the days of managing external storage credentials separately. With this update, admins can manage all external storage credentials in one place. This centralization simplifies credential maintenance and updates, reducing the likelihood of errors and enhancing overall system management.

Support For Multiple Providers
S-Docs supports the following options for external storage providers:

  • Amazon Web Services (AWS) S3
  • Google Drive
  • SharePoint
  • Sendgrid

S-Sign Major Updates

Seamlessly Integrate Electronic Signature Functionality With S-Sign Software Development Kit (ESignSDK)

The ESignSDK, also known as the S-Sign SDK, empowers developers to seamlessly integrate electronic signature functionality into their organizations. This SDK offers a range of methods designed to simplify the process of preparing and managing envelopes delivered for eSignature execution on signature documents.

If you’re interested in incorporating the ESignSDK, contact your Customer Success Manager or S-Docs Support.

Prioritize Security With The Minimum Viable Permission Set For S-Sign

In the rapidly evolving landscape of digital business operations, maintaining data security while ensuring seamless functionality has become paramount. This holds especially true for systems like Salesforce, which handle sensitive information critical to an organization's success. When integrating with applications like S-Sign, striking the right balance between access and security becomes essential. In this context, the concept of a Minimum Viable Permission Set (MVPS) emerges as a robust strategy.

Understanding Minimum Viable Permission Set (MVPS)
A Minimum Viable Permission Set (MVPS) is a carefully crafted collection of permissions that grant users the essential access they require without exposing unnecessary or potentially risky functionalities. This strategy involves combining Salesforce profile settings with S-Sign permission set settings to create a harmonious and secure user environment.

Salesforce Profile Settings - Minimum Access - Salesforce
The foundation of the MVPS strategy begins with Salesforce profile settings. Specifically, the "Minimum Access - Salesforce" profile setting entails configuring user profiles with the bare minimum permissions required to carry out their tasks effectively. By restricting access to only what is necessary, the risk of unauthorized data manipulation or breaches is significantly reduced. Users with this profile will have a limited scope of actions, reducing the attack surface for potential security threats.

S-Sign Permission Set - S-Sign Internal User
Complementing the Salesforce profile settings, the S-Sign permission set plays a crucial role in defining the specific capabilities users have within the S-Sign application. In this context, the "S-Sign Internal User" permission set setting comes into play. This permission set has been carefully designed to provide users with the essential functions needed to work within the S-Sign environment, while avoiding the inclusion of unnecessary or overly permissive privileges.

The Synergy of MVPS
The true strength of the MVPS strategy lies in its ability to combine these two components - the Minimum Access - Salesforce profile settings and the S-Sign Internal User permission set settings. This synergy creates a holistic security approach where users have the least privileges necessary across both the broader Salesforce ecosystem and the specific S-Sign application.

Benefits Of MVPS Strategy

  • Reduced Attack Surface: By limiting access to only what is essential, the potential avenues for malicious actors to exploit security vulnerabilities are minimized
  • Customization without Risk: MVPS enables customization without compromising security. Users can perform their tasks efficiently within the boundaries defined by the MVPS
  • Efficient Onboarding: New users can be onboarded swiftly by assigning them the MVPS. This eliminates the need for time-consuming manual adjustments to permissions
  • Adaptability: As user roles evolve, the MVPS can be easily adjusted to accommodate changing needs without compromising security protocols

July 2022

By Release Notes

S-Docs 4.516

Note: See considerations for this release

Major Updates:

Save time with stronger dynamic email functionality

  • S-Docs templates can automatically populate dynamic email settings like Subject, Recipient, and Sender using data from Salesforce. Now, these fields can access even more data, including users’ Runtime Prompt responses and metadata like information about the user emailing the document.

Distributing batch documents is easier than ever

  • S-Docs Mass Merge allows S-Docs customers to generate hundreds of documents at once. Now, users can click a button to download each individual file and distribute them their way. Plus, users can now email the batch with one click even if certain docs don’t generate based on business rules or other criteria. Read more about Mass Merge in this documentation article.

Minor Updates:

General

  • Support was added for querying ContentDocumentLinks that return PDFs to stitch to your current template with the PDF Stitch feature
  • Templates using the PDF Stitch feature now require the Create Salesforce Attachment and link to record or the Create Salesforce File and link to record checkboxes to be checked if the generated document needs to be emailed
  • File name encryption was removed from supplementary DOCX template files (metadata and other files automatically included when a DOCX file is uploaded to S-Docs)
  • Support was added for using special keywords BRACKETOPEN and BRACKETCLOSE to include the [ and ] characters in generated DOCX files
  • Support was added for embedding images stored as Document records in DOCX templates
  • The From field on the S-Docs Email page is now rendered as a locked field for templates that don’t have the Enable user to choose/select from a picklist checkbox checked in the Email Sender Settings in the template editor. Previously, this field was hidden when the checkbox was unchecked
  • The Runtime Prompt Text Prompt option Allow users to create new lines, which allowed users to use the Enter key to create new lines of text in response to Text prompts,  was removed for non-rich text inputs. The Enable Rich Text Input Fields checkbox must now be checked to allow users to create new lines of text

Merge Field Attributes

  • Support was added for the CR (Character Recognition) merge field attribute
    • Usage: This attribute converts text into OCR-A or OCR-B font (Optical Character Recognition), which is used for generating checks and other number strings that need to be read by computers
    • Syntax: {{!Object.FieldName CR="[OCR-A/OCR-B],[FONT SIZE (REQUIRED),[SPACING (OPTIONAL)]"}}
    • Example: {{!Opportunity.Description CR=“OCR-A,20,5"}}
    • Notes: 
      • Only digits 0-9 are transformed. Other characters are ignored
      • Spacing defaults to 0 if it is not specified. Negative spacing values are allowed. The lower the spacing value, the closer together OCR characters
      • Read more about this and other merge field attributes in this documentation article

Apex Button Parameters

  • Support was added for the customAddFilesButton parameter
    • Usage: This parameter allows you to add a custom button to the S-Docs Email page that calls your custom Apex class to query Salesforce File IDs for automatic attachment to the outbound email. Find out how to set up and use this feature in this documentation article

⌛Coming Soon⌛

The product team is hard at work on exciting new features making S-Docs more powerful and easier to use. Take a look at these upcoming innovations slated for future releases.

Distribute documents via Secure URLs

  • Routinely distribute documents with PII or other sensitive information? This feature will allow you to send your documents as a secure URL requiring a PIN code to access for added security, bypassing vulnerabilities associated with email attachments.

The Insert Related List interface is getting sleeker and smarter

  • The template editor Insert Related List button allows you to quickly set up dynamic tables that merge field data from related list records. We’re overhauling its interface to provide access to more functionality with an easier-to-use UI.

Batch Generate multiple templates at once with Mass Merge

  • The S-Docs Mass Merge feature allows you to generate one template for hundreds of records at once. We’re adding support for multiple templates to save you time and streamline your workflows.

Release Considerations:

  • This press release may contain forward-looking statements that involve risks and uncertainties when referring to future plans, objectives, expectations and intentions. These statements may be identified by the use of words such as "anticipate," "future," "intend," "plan," "expect" and other similar expressions. The actual results of S-Docs could differ materially from those discussed in, or implied by, such forward-looking statements. Statements contained in this press release are based upon information presently available to us and assumptions that we believe to be reasonable. We are not assuming any duty to update this information should those facts change or should we no longer believe the assumptions to be reasonable.
  • The API version of all package components was updated to Salesforce's latest API version (54.0)

S-Sign 2.299

Note: See considerations for this release

Major Updates:

Customize the Signer Experience with More Data From Your Org

  • Have you ever needed to automatically name an S-Sign file based on a custom object record name, or populate signer names with data from unrelated objects? You can now use Named Query merge fields to input dynamic data from related or unrelated objects into S-Sign Template Settings, Signer Profile settings, and Field settings.

Collect up to 5x more signatures per hour

  • Manage high-volume agreement workflows? We’ve upgraded S-Sign’s processing capacity to handle up to five times more signature capture events per hour, enabling you to keep business moving no matter your requirements.

Data Security, Continually Improved

  • At S-Docs, your data security is priority number one. Our product team employs rigorous security testing against Salesforce’s strictest standards every release cycle, ensuring your data is always protected.

Minor Updates:

General

  • Content in the To field in the Email Recipient Settings in the template editor is now cleared when the template is enabled for S-Sign
  • Removed the ability to type dates into date input fields. All dates must now be selected from the calendar menu
  • Field access is now enforced for update and upsert activities in S-Sign
  • Support was added for translating the UI of the  “Confirm Signers” and “Confirm Document Signing Order” pages
  • Support was added for printing documents generated using PDF-Upload S-Sign templates
  • Support was added for toggling whether document preview links on S-Sign Envelope Document records (View Original Document and View Signed Document) should auto-download the document or open it in a new tab
    • By default, documents are auto-downloaded. Check the Prevent auto-download upon S-Sign document preview field in the S-Sign Setup Advanced Settings to set these links to open documents in a new tab
    • Note: Documents generated before toggling this setting will continue to auto-download, and only future signed documents will be impacted

⌛Coming Soon⌛

The product team is hard at work on exciting new features making S-Sign more powerful and easier to use. Take a look at these upcoming innovations slated for future releases.

Secure your signed documents in DocuNECT eVault

  • Customers using the secure document repository eVault service DocuNECT will soon be able to configure S-Sign to store completed documents in their eVault automatically, adding an additional layer of document security and integrity.

Streamline template development with an improved S-Sign panel

  • Template builders can configure signer profiles, S-Sign input fields, and other settings to customize the e-signature experience for your customers. We’re updating the interface for these settings to make template building faster and more intuitive.

More flexibility in your customers’ e-signature experience

  • If your customers decline to sign a document, they’re able to input a typed reason to give you more context. Soon, they will be able to add attachments when they decline a request to give you a fuller picture and keep the process moving smoothly.

Release Considerations:

  • This press release may contain forward-looking statements that involve risks and uncertainties when referring to future plans, objectives, expectations and intentions. These statements may be identified by the use of words such as "anticipate," "future," "intend," "plan," "expect" and other similar expressions. The actual results of S-Docs could differ materially from those discussed in, or implied by, such forward-looking statements. Statements contained in this press release are based upon information presently available to us and assumptions that we believe to be reasonable. We are not assuming any duty to update this information should those facts change or should we no longer believe the assumptions to be reasonable.
  • The API version of all package components was updated to Salesforce's latest API version (54.0)

April 2022

By Release Notes

S-Docs 4.506

Note: See considerations for this release

Major Updates:

Leave disparate documents behind with S-Docs PDF Stitch

  • PDF Stitch keeps your documents organized by enabling you to combine your S-Docs PDFs with any PDF in Salesforce. Find out how you can use PDF Stitch to create seamless document packets and more in this documentation article.

Support your multinational customers with data translation

  • One template, boundless languages. You can now create translation maps for any field values in your documents, enabling you to deliver personalized experiences across the globe. Find out more in this documentation article.

Generate larger PDFs without skipping a beat

  • Hefty content requirements? S-Docs PDFs that exceed Salesforce file limits now split into multiple files, allowing you to generate larger documents without breaking your stride.

Scale your workflows by up to 50% with higher bulk processing capacity

  • Get more docs out the door faster. S-Docs queueable bulk generation now provides increased processing speeds and 50% higher document limits.

Bigger batch jobs, lower limitations

  • You can now use batchable apex to bulk-generate more documents daily than ever before - though keep in mind that more processing time is required compared to queueable apex. Reach out to our team to find out more.

General

  • Support was added for uploading documents to Amazon S3 folders
  • Support was added for automatically including ContentDocument, ContentVersion, and/or Attachment IDs in the folder file path for documents uploaded to Amazon S3 folders
    • Usage: Check the Use File Id For AWS Folders checkbox in your S-Docs Custom Settings record
    • Example: A file called “TestFile.pdf” with ContentDocument id of 0693s00000LjO2UAAV and ContentVersion id of 0683s00000MYvbkAAD would have a file path that looks like:
      • 0693s00000LjO2UAAV/0683s00000MYvbkAAD/TestFile.pdf
  • Support was added for using the PDF-Upload template format with PDFs of any dimension
  • The embedImage() function for DOC/DOC-NEW templates now uses the PageReference method getContent for images in the current org and HTTP requests for image outside the org
    • Note: Images in DOC-NEW templates that aren’t stored within the org should be in the proper content.force or documentforce URL format, since improperly formatted URLs cannot be converted from outside orgs
  • Support was added for translating Email Settings data using data translation maps
  • Support was added for embedding static resource images in DOC/DOC-NEW templates
  • Pound (#) and comma (,) characters are no longer replaced with underscores in file names for documents generated using the DOC template format
  • The Header and Footer tabs were removed from the template editor for the XLS template format
  • Support was added for converting HTML-based blobs into strings using merge field attributes or related list column tags
    • See the Merge Field Attributes or Related List Column Attributes sections of these release notes for more information
  • The view state storage limit was increased for DOC-NEW templates that contain embedded images on the Generated Documents page and S-Docs Email page
  • Support was added for disabling default queries S-Docs runs on the Contact object when users navigate to the S-Docs Email Page
    • Enable this feature by checking the Disable Contact Record Queries For Email checkbox in the S-Docs Custom Settings
  • Support was added for defining styling at the per-page level for the PDF template format, allowing for different page sizes/margins for individual pages 
        • Usage: Use <pagebody> tags in your templates like you would regular <body> tags. The <pagebody> tags will be replaced with HTML <body> tags at runtime.
        • Example:
          <style type="text/css">@page parentTemplate {
              margin: 1in;
            }
            body.parentTemplate {
              page: parentTemplate;
            }
            @page componentTemplate {
              margin: 0in;
            }
            body.componentTemplate {
              page: componentTemplate;
            }
          </style>
          <pagebody class="parentTemplate">
              Page 1
          </pagebody>
          <pagebody class="componentTemplate">
              Page 2
          </pagebody>
          <pagebody class="parentTemplate">
              Page 3
          </pagebody>
          

           

  • Support was re-added for including page breaks after a specified number of documents when using the Mass Merge Combine all into single printable document function
    • This feature can be enabled in the Mass Merge Options section of the Document Options tab in the template editor
  • Users without View Setup and Configuration permissions can now generate documents 
    • Note: If users without the View Setup and Configuration permission generate DOC or DOC-NEW documents with embedded images, those images may not render due to that user being unable to retrieve the image URL
  • Support was added for using merge fields to define which SharePoint folder documents will be uploaded to. Find out more in this documentation article.
  • Support was added for delimiting components merged though related lists with page breaks. Find out more in this documentation article.
    • Syntax: <component delimiter="pagebreak">Component Name</component>
    • A page break will be added after each component
  • Support was added for modifying the reply-to address for emails sent with S-Docs
    • You can set the reply-to address within the Email Settings tab in the template editor or on the S-Docs Email page
  • Added the S-Docs Jobs (Guest User) permission set
    • This permission set should be assigned to guest users that need to insert S-Docs Jobs
  • Support was added for the French phone number format (## ## ## ## ##). Please see Formatting Phone Fields for more information.
  • Users without admin credentials can now upload documents to Microsoft Sharepoint
  • Support was added for unlinking Microsoft SharePoint credentials
  • Support was added for allowing end users to specify which Microsoft SharePoint folder a document should be uploaded to after generation. Find out more in the SharePoint Integration documentation article.
    • Note: The Document library will default to the Documents (/Shared Documents/ in URL) library
  • The top of the template editor now displays the Template Format and Related To Type (base object) field values
  • Modified the behavior of the S-Doc Relationship Email button (presented as an envelope icon for each generated document in an object’s S-Docs related list) to allow for generation of email templates or additional attachments directly from the S-Docs email page
  • Help text was added to the Allow user to create new lines setting for Runtime Prompts fields

Merge Field Attributes

  • Support was added for the blobToString merge field attribute
    • Usage: This attribute converts HTML-based blobs into strings
    • Example: {{!Object.Field blobToString=“true”}}
    • Notes: 
      • The blob content must be able to be converted to a string or well-formed HTML
      • This attribute is also available as a related list column attribute

Related List Column Attributes

  • Support was added for the blobToString column attribute
    • Usage: This attribute converts HTML-based blobs into strings
    • Example: <column blobToString=“true”>Object.Field</column>
    • Notes: 
      • The blob content must be able to be converted to a string or well-formed HTML
      • This attribute is also available as a merge field attribute
  • Support was added for grouping records in related list tables by multiple fields
    • Usage: Add a comma-delimited list of fields within <groupby> tags
    • Example: <groupby>quantityunitofmeasure,family</groupby>
  • Support was added for passing static merge fields (like Runtime Prompt merge fields or Special Merge Fields) into components merged through related lists
    • Usage: Use the mergeFieldName column attribute to set the name of the merge field as it will be referenced in the component. Use the mergeFieldValue column attribute to input the merge field syntax that the field should pull its value from
    • Example: 
      • Parent Template Syntax (with a Runtime Prompt text merge field called {{!UserComments}}
        • <!--{{!<LineItemsSOQL>
          <component>Component_Template</component>
          <soql>SELECT Id FROM Opportunity WHERE AccountId='{{!Account.Id}}'</soql>
          <column mergeFieldName="RPTTextField1" mergeFieldValue="{{!UserComments}}"></column>
          </LineItemsSOQL>}}-->
      • Component Template Syntax: 
        • {{!RTPTextField1}}

Release Considerations:

  • The API version of multiple classes was updated from 42 to at least 52
  • The Add Image button in the template editor and Live Edit editor is now hidden on mobile devices

S-Sign 2.287

Note: See considerations for this release

Major Updates:

Create templates faster with help from document previews

  • Pixel-perfect S-Sign documents have never been easier to achieve. You can now preview how a document will appear to its signers as you build your template - helping you work more efficiently and always ensuring seamless customer experiences. Find out more in this documentation article.

Get a bird’s-eye view of your e-signature requests

  • The new S-Sign Request Management page provides a window into an org's e-signature activity. Create and manage requests from one centralized location with less clicks and higher efficiency. Find out more in this documentation article.

Deliver smoother customer experiences with faster agreement execution

  • Less waiting, more doing. We’ve accelerated the document submission process by up to 50% so your customers can execute faster - and you can achieve quicker time to contract value.

Minor Updates:

General

  • Added a new status to the Envelope Document object to reflect when signers save their progress
    • New Status: Saved inputs for [SIGNER_PROFILE_NAME]
  • Support was added for using the legacy Sign Here arrow icon as the signature input button on signable documents. This can be set on the S-Sign Configuration page.
  • Added the [[EMAIL_SUBJECT]] S-Sign merge field
  • Signer profiles without associated input fields are no longer removed from the template
    • This behavior allows for adding signer profiles that can review & submit a document without needing to fill any fields
  • Adds text-wrapping in S-Sign via Allow New Lines,
  • Support was added for enabling new lines for text input fields by default
  • Support was added for using hyperlinks in S-Sign documents
    • Note: This is only supported for the PDF template format
  • Support was added for previewing S-Sign requests with the PDF-Upload template format
  • The Date field ‘MMM d, yyyy’ format option was changed to ‘MM d, yyyy’ and now displays a full month, e.g. ‘December 1 2021’
  • Support was added for using custom S-Sign Request HTML email templates for signers signing via email after In-Person signers
  • Support was added for abbreviating text-to-signature initials by default (if John Smith is typed into the input box, the initials displayed will be J.S.)
  • Support was added for hiding unchecked checkboxes on the final signed document
  • Support was added for limiting the number of characters in Text Input Fields
  • Support was added for using S-Sign with the InsurancePolicy standard object

Release Considerations:

  • Multiple signer profiles now require unique names
  • S-Sign now only creates one signer profile by default instead of two
  • Date input fields now use the jQuery DatePicker

November 2021

By Release Notes

S-Docs 4.471

Note: See considerations for this release

Major Updates:

Upload Documents to Microsoft SharePoint

  • Using Microsoft SharePoint? You can now upload documents to SharePoint directly from Salesforce without missing a beat. Learn how to configure and use the S-Docs SharePoint integration in this documentation article.

Merge Components Dynamically

  • S-Docs components, which are templates that can be merged seamlessly into other templates, just got even smarter. You can now leverage merge fields to dynamically insert different components based on field data. For more information about this feature, including important limitations, check out this documentation article.

Leverage the power of PDF with the ease of PDF-Upload

  • S-Docs PDF-Upload templates, which allow users to upload any PDF to Salesforce and drag-and-drop merge fields, can now be inserted as components into traditional PDF templates. Find out more details in this documentation article.

Ensure your critical fields are always populated

  • Documents with missing or incomplete data can be frustrating. Now, you can set field population as a condition for document generation, ensuring your critical data is always present. Find out more details in this documentation article.

Minor Updates:

General

  • Added new functionality for related list Runtime Prompts
    • Support was added for displaying the records selected in one related list Runtime Prompt as options for additional related list Runtime Prompts
    • Support was added for using <column>rownum</column> to insert each record’s row number
    • Support was added for setting a minimum/maximum number of records that can be selected
    • Support was added for using {{!objectID15}} and {{!objectID18}}
    • Column headers now display field labels instead of field names
  • Support was added for allowing users to respond to Text Runtime prompts with rich text (e.g. bold, italics, tables, images)
  • Support was added for the Individual Application standard object
  • Support was added for selecting the Render level in the Insert Conditional Logic menu in the template editor
  •  Added the base URL to Salesforce checkbox images
  • Groupby values in DOCX templates now take on the styling of the column they occur in 
  • Support was added for using the rownum special merge field within components called with LineItemsSOQL tags to reference the component’s position (e.g. 1,2,3, etc.) in the output list
    • Usage: Use the following syntax within the component to reference its position
      • Method 1: {{!RowNum}} 
      • Method 2: {{!MergeFieldPrefix.rownum}}
  • Support was added for formatting phone fields through merge field and related list attributes. Refer to this documentation article for more information.
    • A phone formatting picklist will now appear when phone fields are selected within the Insert Field and Insert Conditional Logic wizards
  • Support was added for handling Box upload errors without throwing an exception
    • This option ensures that DML occurring in the Box package does not get rolled back by an S-Docs exception
    • Follow the instructions in this article to enable this feature
  • Support was added for including all files related to the base record of an S-Doc Job in the email sent by the job. 
    • Check the Include All Related Files checkbox on the S-Doc Job record to enable this setting
  • Temporary files generated while using the Live Edit feature are now saved as .txt files 
  • Components with a Related To Type value other than “Component” now inherit the Page Settings styling from the parent template
  • Support was added for using Named Queries with the PDF Upload template format
  • Support was added for excluding template Attachments (e.g. uploaded DOCX files or PDFs) from template exports using the S-Docs Template Migrator
  • Support was added for routing documents to your Amazon S3 buckets through your F5 gateway proxy URL. This can be configured with the S3 Proxy URL field on the AWS S3 Integration page
  • Salesforce Attachments and Files generated via Mass Merge or batch S-Docs Jobs now appear in the Notes & Attachments and Files related lists for objects specified by the template’s Additional Relationship field
  • Support was added for the {{!UserDepartment}} special merge field

Merge Field Attributes

  • Support was added for the justifyNewlines merge field attribute
    • This attribute prevents irregular spacing when merging multi-paragraph long text area fields wrapped in justify tags
    • Usage: When justifyNewlines=“HTMLElement”, each paragraph will be treated as its own paragraph
    • Example:  <div style=“text-align: justify;”>{{!Opportunity.Long_Text_Area__c justifyNewlines=“div”}}</div>
      • Output: <div style=”text-align: justify;”>Paragraph One</div><div style=”text-align: justify;”>Paragraph Two</div>
      • Limitations
        • This attribute can only be used for style=“text-align: justify”
        • This attribute cannot be used with Microsoft templates

Related List Column Attributes

  • Support was adding for using the format-date column attribute with Related List Runtime Prompts
  • Support was added for the addToEmail attribute
    • This parameter adds email addresses merged through related list columns as document email recipients
    • Usage: The addToEmail attribute must be added to a related list column and either the S-Docs button URL or S-Docs Job Email Params field, depending on if the document is generated manually or automatically
    • Example: 
      • <column addToEmail="true">CreatedBy.Email</column>
        • Additionally add addToEmail=‘true’ to your S-Docs button URL if generating the document manually
        • Additionally add addToEmail=true to the S-Docs Job Email Params field if generating the document automatically

Apex Button Parameters

  • Changed the template editor button apex parameters showCVJSON and rpRichText into fields in the Document Options tab in the template editor
  • Support was added for using the autodownload parameter with Microsoft templates
  • Support was added for the addToEmail parameter 
    • Usage: This parameter is used in conjunction with the addToEmail related list column attribute (see above) to add email addresses merged through related list columns as document email recipients
    • Example: {!URLFOR('/apex/SDOC__SDCreate1', null,[id=Object.Id, Object='Object', addToEmail=‘true’])}

Release Considerations:

  • If your Salesforce org has enabled stabilized URLs for Visualforce, Experience Builder, Site.com Studio, and Content Files, any DOC/DOC-NEW templates with the Embed Images checkbox checked will not be able to generate. To resolve this, navigate to your S-Docs Custom Settings record and check the Stabilize URLs Checked checkbox.
    • Note: Stabilized URLs are automatically enabled in all new or refreshed Sandboxes, and will be enabled for all orgs in the Summer ‘22 release. View this Salesforce Help article for more information.
  • The Live Edit feature is no longer supported for the DOC template format. DOC templates with Live Edit enabled will not be editable at all until the Live Edit checkbox is unchecked on the template detail page
  • All references to Salesforce API versions under 20.0 were updated

S-Sign 2.241

Note: See considerations for this release

Major Updates:

Personalize S-Sign with custom reminder and expiration emails

  • Keeping your S-Sign requests on track with reminder or expiration emails? You can now create custom templates that deliver personalized, on-brand experiences every time. Learn more about custom email templates in this documentation article.

Deliver a faster signing experience with auto-selected text-to-signature

  • The text-to-signature feature allows signers to skip the drawing pad and insert their signature as a cursive font. You can now keep this option checked by default, increasing the speed and simplicity of the signing experience.

Gain more insight into your S-Sign requests

  • The Sign Status field on the S-Sign Envelope Document object was updated with new values to more accurately record the progression of a request through the final S-Sign submission steps, allowing you to view more detail about the status of your in-progress requests than ever before. 

Minor Updates:

General

  • Support was added for translating S-Sign Picklist from Field values
    • Usage: Define field translations in the Salesforce Translation Workbench, then add the ssignParams='language:Salesforce_Language_Code' parameter to your S-Docs button. Be sure to replace “Salesforce_Language_Code” with the appropriate language code (e.g. de for German, fr for French, etc.). 
    • Note: If you’d also like to translate the S-Sign UI, ensure the name of your UI translation is the same Salesforce language code used with the ssignParams parameter
  • Support was added for formatting S-Sign Text Fields according to a chosen currency (i.e. U.S. currency as $1,234.56, E.U. currency as €1.234,56, etc.). This can be configured with the Currency picklist in the S-Sign Text Field settings
    • Support was additionally added for preformatted text fields according to user-specified formatting
  • Support was added for inserting new lines in text input fields. This setting can be configured with the Allow New Lines checkbox in the S-Sign Text Field settings
  • Support was added for setting the Reply-To field on S-Sign confirmation emails to the email of the requester
  • The special merge fields [[REQUESTER_NAME]] and [[REQUESTER_EMAIL]] (used with custom S-Sign notification templates) now merge values from the createdby.name and createdby.email fields, even when the From address is set to an org-wide address
  • Support was added for including/excluding the timestamp and signer name underneath completed signatures. This setting can be configured with the Show Timestamp and Signer Name on Signature Images checkbox on the S-Sign Configuration page.
  • Support was added for sending previously generated documents for e-signature
    • Usage: Create a new button on the SDoc object with the URL listed below and add it to the SDoc page layout. When users navigate to an S-Doc record and click the button, they’ll be able to pair the document with an S-Sign email template and send it for signature
    • URL: {!URLFOR('/apex/SDOC__SDCreate1', null, [id=SDOC__SDoc__c.SDOC__ObjectID__c, Object=SDOC__SDoc__c.SDOC__ObjectType__c,showSSignInPerson='true',preinsertedDocs=SDOC__SDoc__c.Id])}
  • Modified the e-signature user interface for ease of use
    • The navigation toolbar was moved from the bottom to the top of the screen
    • The Previous button is now hidden for documents with only one input
    • The Submit button is now highlighted for better visibility
    • The Sign Here and Initial Here input squares are now darker with larger, bolder text for better visibility
  • Support was added for adding extra recipients to confirmation emails
  • Support was added for customizing and adding CSS styling to error messages for the input field groups feature
  • Added a default text-to-signature font selection

Release Considerations:

  • The deprecated custom setting Save Confirmation Emails As Activities was reinstated
  • ‘No Contact Records’ inserted by S-Sign are now able to be auto-deleted by the package
  • All ContentDocumentLinks inserted by S-Sign now have a Visibility of AllUsers
  • The S-Sign User and new S-Sign Experience Cloud User permission sets now allow View All permissions on the S-Sign Envelope object

July 2021

By Release Notes

S-Docs 4.439

Note: See considerations for this release

Major Updates:

Do More With Runtime Prompts

  • S-Docs Runtime Prompts, which collect and merge user input into documents during generation, keep getting better and better. You can now prefill prompt answers for use with one-click automation, auto-format phone numbers and other preformatted text structures, and more. Read more about recent runtime prompt enhancements in this documentation article.

Preview Microsoft Word, Excel, and PowerPoint Documents Before Generation

  • You can now preview Microsoft Word, Excel, and PowerPoint documents before saving final copies. Read more about the previewFirst parameter in this documentation article.

Storing Your Documents In Google Drive?

  • You can now upload documents to individual Google Drive folders, making this integration even more useful. Folders are chosen at the template level. Learn more about configuring this feature in this documentation article.

Minor Updates:

General

  • Support was added for uploading  documents to Google Drive folders
    • Usage: Add a Google Drive folder ID to the Google Drive Folder Id for Upload field (which appears in the Other Options section of the Document Options tab in the template editor for Google Drive enabled templates). Documents generated with that template will be uploaded to that folder
    • Note: You may use merge fields from the base record
  • Modified the Google Drive Integration to only ask for permission to View and Manage Google Drive files and folders that you have opened or created with this app
  •  Support was added for Macro-Enabled Microsoft templates
  • Support was added for preformatted runtime prompts that automatically fill in user-specified formatting characters as the user types
  • PDF dimensions are now verified prior to a PDF being uploaded with the PDF-Upload feature
  • The S-Docs Template Migrator now notifies users of modified or ignored fields during template import
  •  Support was added for referencing related list record IDs in merge fields that were selected in a Runtime Prompt
  • Removed license key validity checks in testing contexts
  • The S-Docs Jobs LineItemsData_XML field character limit is now 131,000 characters
  • Added the ConnectedAppAudienceURL field to S-Docs Custom Settings
    • Usage: This field is used in Salesforce Government Cloud orgs, and should be set to either https://login.salesforce.com or https://test.salesforce.com, depending on if you are working in a Production or Sandbox environment
    • Note: In non-Government Cloud orgs, this field can be left blank
  • Support was added for adding an API Key for sending secure emails with SendGrid
  • Added code to remove the inserted image from Salesforce Inspector Chrome Extension
  • Modified the Edit link on S-Doc records to allow for use in Experiences/Communities
  • Added the Community site prefix to the Edit link on the Generated Documents page, and the View link on the Live Edit page
  • Support was added for true image embedding in DOC-NEW and DOC template formats
  • Support was added for embedding images in components used in DOC-NEW and DOC template formats
  • Support was added for customizing which contacts appear in the Contact Quick Pick menu on the S-Docs Email page and the Document Generation page with user-defined queries
  • Removed the Close button from the S-Docs Live Edit page. After saving edits, a message will appear notifying the user when they can safely close the page or continue editing
  • Added more descriptive error messages to the S-Docs Job Status field
  • Increased the range for email address domain length (such as .com, .net, .org, etc.). Domains with 2-64 characters are now accepted
  • Added UTF-8 encoding to all generated HTML files
  • Support was added for automatically including all files related to the base object on emails sent with S-Docs Jobs
  • Support was added for displaying a custom message across the top of the S-Docs email page
    • You can add this message on the S-Docs Setup page. It will appear for all emails sent with S-Docs.
  • Support was added for single-row PPTX table formats

Merge Field Attributes

  • Support was added for the merge field attribute toCells
    • This allows you to split a field into single letter cells
    • Usage: {{!Opportunity.Three_Character_Code__c toCells=“number of cells to generate,CSS Class to apply to the table cells”}}
    • Example: {{!Opportunity.Three_Character_Code__c toCells=”3,cssClass”}}
    • Note: This should be added in a <td> cell and will add the specified number of cells
  • The  breakeverynchars attribute now supports RTF-enabled merge fields and international characters

Apex Button Parameters

  • Support was added for the autodownload parameter
    • Usage: If autodownload=‘true’, generated documents will be automatically downloaded to the user’s computer once generation is complete. This can be used along with other URL parameters to control the flow of the generation process
    • Note: This does not currently work with DOCX, XLSX, or PPTX documents, but support is planned to be added in the future
  • Support was added for the showCVJSON parameter
    • Usage: This parameter allows you to preset Content Version file attributes in the Template Editor. Add showCVJSON=‘true’ to the Template Editor button to add the Content Version Field Assignment JSON field to the Document Options tab. You can then input a JSON map of Content Version field API names and values
    • Example:
      {
      "Checkbox__c": "true",  "Date_Created__c": "{{!Opportunity.CloseDate}}",  "Type_Picklist__c": "Three",  "Type_Text__c": "{{!Opportunity.Name}}","Decimal_Value__c": "12.34","Integer_Value__c": "1234"}
    • Note: You may use merge fields from the base record
  • Support was added for the hideContactLookup parameter
    • Usage: If hideContactLookup=“true”, the contact lookup window will be hidden on the Merge Contact Information page and the S-Docs email page
  • Support was added for the showBackButton parameter
    • Usage: If showBackButton=‘false’, the Back button will be hidden from the Template Selection page and the View Documents page
    • Note: Any other value, or the absence of the parameter, will lead to the Back button appearing as normal

Release Considerations:

  • The template editor image browser now uses content.force links

S-Sign 2.214

Note: See considerations for this release

Major Updates:

Need Signatures From Both In-Person and Remote Signers?

  • You can now collect e-signatures from multiple in-person signers before automatically routing your request to remote signers via email. S-Sign Mixed Mode lets your team do business from anywhere. Read more about this and other S-Sign template settings in this documentation article.

Send Signed Documents As Secure Links

  • After an e-signature request is completed, you can now opt to send the signed document as a secure link requiring the signer to verify their identity before downloading, rather than a PDF attachment. This can be useful if multiple users are included on a confirmation email, but only the signer should have access to the document. Read more about this and other S-Sign notification settings in this documentation article.

Data Security, Designed In

  • Our product team is continually striving to ensure S-Sign employs the highest level of security that aligns with Salesforce's most rigorous standards.

Minor Updates:

General

  • Support was added for logging emails associated with the signing process in the base record’s Activity History
  • Support was added for hiding the E-Sign Documents In Person button
  • Support was added for using merge fields in the Send Email After Specified Signer setting in the S-Sign Template Settings
  • Support was added for setting a custom width for Picklist (from Text) and Picklist (from Field) input options
  • Removed the timestamp and S-Sign logo from signature images
  • S-Sign requests generated through S-Docs Jobs now record the Job ID that generates the signable PDF on the S-Sign Envelope Document record
  • Added object-level Create, Edit, Delete, and field-level Edit access for all S-Sign Template fields to the S-Sign User permission set
  • Increased the character limit for the S-Sign Input Field XML fields on both the S-Sign Template and S-Sign Envelope Document objects from 32,000 characters to 64,000 characters 
  • Support was added for voiding S-Sign requests through global functions
    • Usage: Users can void an entire S-Sign Envelope or an individual S-Sign Envelope Document. These functions will notify signers of the voided document(s) and update relevant fields on the S-Sign Envelope Document and the S-Sign Envelope
    • Function: SSign.SSUtil.voidContracts(SSIGN__SSEnvelope__c sse, String voidReason)
      • This takes in a S-Sign Envelope object. It needs to have at least queried the Id of the S-Sign Envelope before being passed to the function
    • Function: SSign.SSUtil.voidContracts(SSIGN__SSEnvelope_Document__c ssed, String voidReason)
      • This takes in an S-Sign Envelope Document object. It will need to have at least queried the Id of the S-Sign Envelope Document before being passed to the function
    • Function: SSign.SSUtil.voidContracts(String idToVoid, SSUtil.VoidType voidType, String voidReason) 
      • This takes in an Id of the object to void the contract for, an Enum of type SSUtil.VoidType (the options are SSUtil.VoidType.SSEnvelope and SSUtil.VoidType.SSEnvelopeDocument), and a reason for voiding the contract
      • Example: 
        • SSign.SSUtil.voidContracts( 'a085G00000moUp6', SSign.SSUtil.VoidType.SSEnvelope,  'This contract has expired.' );
  • Modified S-Sign Input Response records to be Attachments rather than ContentVersions
  • Support was added for opting to save no S-Sign documents to the base record (previously, a user had to choose to save either the signed document, the audit document, or both to the base record). This can be configured at the template level in the S-Sign template settings.
  • Downloaded documents now include the attachment/document name
  • Added the global function SSIGN.SSLicensesController.getSSignLicensedUsers() that will return a list of User Ids for all licensed users in the org
  • Added a warning message to prevent users from closing the tab before the signing process completes
  • Support was added for using a custom site guest user permission set for S-Sign

Release Considerations:

  • If duplicate S-Sign Input tags are found within the S-Doc Template body for the same signature/initials input, an error will now be thrown

March 2021

By Release Notes

S-Docs 4.404

Note: See considerations for this release

Major Updates:

Cruise Through S-Docs With The New Navigation Hub

  • We’ve added a one-stop shop for all of your S-Docs administrative needs. Update your license key, migrate templates, translate the S-Docs UI - it’s all accessible from the new S-Docs Setup tab. Find out more details in this documentation article.

Add Radio Buttons To Your Templates

  • The checkbox’s circular cousin has arrived at S-Docs. You can now display boolean merge field and related list data as radio buttons in your documents. Find out more details in this documentation article.

 Bulk Processing Just Got Up To 45X Faster

  • As a 100% native document generation & e-signature solution, speed has always been our forte - and it just keeps getting better. Over the last few months, we’ve accelerated our processing speed for bulk jobs by up to 45 times so that you can work more efficiently.

The Mass Merge Interface Now Has Sleek Lightning Skinning

Minor Updates:

General

  • Support was added for uploading images on the Live Edit page
  • Support was added for Org-agnostic image merge fields
    • Usage: These merge fields will display images across different Salesforce orgs without needing to be modified
    • Example: {{!Image type=“Attachment” query=“Description = ‘A unique description’”}}
    • The type parameter specifies the image file type (Attachment, Document, or ContentDocument). The query parameter specifies a SOQL query WHERE clause that will return that image uniquely
    • Note: The user must use double quotes for the type and query
  • The Callable Apex feature was expanded to allow for populating tables in your S-Docs templates via custom apex classes. Learn more about using callable apex within <lineitems> statements in this documentation article.
  • Support was added for leaving off file extensions on the Title field of Salesforce Files
    • This can be configured on the S-Docs Setup page by checking the “Do Not Include Extensions In File Names” checkbox
  • Beta support was added for ordered lists and unordered lists in DOCX rich text fields
  • Support was added for sending  emails via Mass Merge with no attachments
  • Support was added for using the doclist parameter on the Mass Merge page 
    • Usage: This auto-selects a template to use in the Mass Merge. It accepts a comma-delimited list of template IDs.
  • Support was added for using the autostart parameter on the Mass Merge page
    • Usage: This will start the Mass Merge immediately. The doclist parameter must also be provided for this to take effect.
  • Additional support was added for the tab parameter on the Mass Merge page
    • Usage: tab=“3” will select the “Generate Docs” tab (tab 3) by default on page load
  • Support was added for the useDynamicViewLink parameter
    • Usage: After uploading a document to external storage, the document view icon automatically links to the external repository, and the document number link links to the document within Salesforce. Adding this parameter to the S-Docs button will cause the document number link to also link to the external repository
  • Support was added for using the translate and display attributes in merge fields in components that are part of a component related list
  • Support was added for auto-clearing completed S-Docs Jobs after emailing in mass merge
  • Support was added for reviewing/editing details of Salesforce Tasks created using the Auto Create Task feature

Merge Field Attributes

  • Support was added for the inline component attribute in DOCX templates
    • Usage: If inline=“true,” S-Docs will merge the component on the same line as the current paragraph. By default, components are placed on new paragraphs.
    • Note: The component must be on the line by itself. You cannot use more than one inline=“true” component per line. If any additional text is on the line, it will be removed.
  • Support was added for the font-family and font-size attributes in DOCX rich text fields
    • Example: [{{{{!Opportunity.Rich_Text_Field__c font-family="Wingdings" font-size="17.5"}}}}]
  • Support was added for the breakeverynchars attribute for merge fields and lineItemsSOQL columns
    • Usage: breakeverynchars=“N” will insert a line break every N characters
    • Example: {{!Opportunity.Long_Field__c breakeverynchars="10"}}

Release Considerations:

  • The Save Data field was removed from the S-Doc Template Editor. Data is now always saved to the S-Doc record
    • Note that if you unchecked the Save Data field before this change was made, your setting will be preserved. To change it in the future, you can add the Save Data field to the S-Doc Template layout and modify it there.

S-Sign 2.164

Note: See considerations for this release

Major Updates:

Security

  • The S-Docs team is constantly conducting rigorous tests to ensure our 100% native application is as secure as possible and meets Salesforce standards. Guest user permissions were reduced in the Salesforce Spring ‘21 release to enhance data security. We've updated our products to adhere to these new requirements, providing our customers with the highest possible level of security.

Minor Updates:

General

  • Support was added for custom alert messages when a signer fills in a restricted amount of fields in an input field group
  • Support was added for adding Additional Style CSS for Signature & Initial fields
  • Support was added for opening the Sign In Person interface in a new tab in Salesforce Communities
    • This can be set within the S-Sign Configuration page
  • Support was added for allowing signers to select their email address from a picklist when email verification is disabled
  • Modified S-Sign to check if an S-Sign Input Field attribute is required for that specific type, and only stores the data in the Input Field XML if it is required.
  • Additional support was added for adjusting Date fields
    • Adjusting date field size: Edit the “input height” and “input width” fields for the date field in the S-Sign Fields panel
      • Note: Values must be input as any valid CSS length unit without a semicolon
      • Inputs to these fields will be added to the date input field’s width and height values in the style attribute
    • Adjusting date field Additional Style: Edit the Additional Style field for the date field in the S-Sign Fields panel
      • Note: Values must be written using CSS syntax with semicolons
      • You can use the Letter-Spacing property, which is otherwise not supported by Salesforce
        • Example: color:blue; letter-spacing: 3px; font-size: 14px;
  • Support was added for multi-document S-Sign envelopes when all templates do not require a Sign In Person email
  • Support was added for auto-displaying initials (pulled from the Signer Name) on initials fields

Release Considerations:

  • Expiration and reminder alerts were modified to only trigger after 24 hours x the # of days since the S-Sign Request was created, when greater than the number of days these fields are set to. Previously, expiration and reminder alerts would be sent out in the first hour of the date the S-Sign request was set to expire or the date the reminder was set to be sent out
  • Object-Level Edit access was removed on all objects for the S-Sign Site Guest User permission set
  • The S-Sign Templates tab was added to the package. If this tab was manually added in your org and you encounter the following error upon upgrading, "This app can't be upgraded. There are problems that prevent this package from being installed. (SSTemplate__c) Unmanaged custom object tab already exists, package upgrade cannot create another tab," then delete the custom S-Sign Templates tab and try updating again
Top