Category

Release Notes

Sep 27
Love0

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
Jul 20
Love0

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)
Mar 29
Love0

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
Nov 10
Love0

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
Jul 08
Love0

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
Mar 10
Love0

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
Dec 17
Love0

December 2020

By Release Notes

S-Docs 4.347

Major Updates:

Refreshed Template Editor UI

  • We've cleaned up and standardized the Template Editor from top to bottom to provide a more consistent and intuitive experience for users of all skill levels. Read more about how our sleek new look will streamline your document-building workflows while preserving the user experience you're accustomed to in this blog post.

Callable Apex

  • Need to evaluate complex logic to produce values to merge into your templates? You can now leverage your own custom Apex classes to generate merge field values in your S-Docs templates. Find out more about the Callable Apex feature in this documentation article.

Switch Statements

  • You can now simplify certain conditional statements into just a few lines. The Switch feature allows you to create switch statements that evaluate hundreds of field conditions at once. Find out more about using switch statements in your templates in this documentation article.

Access Deeper Object Relationships

  • You can now merge field data into your templates from objects up to 5 relationships removed from your base object. There's no need to write any syntax yourself; use the Insert Field button and let S-Docs do the work for you.

Document Storage Integrations

  • Automatically storing your documents in Google Drive, Box, or Amazon S3 has never been easier. We've updated our integrations to deliver a more up-to-date and consistent experience.

Minor Updates:

General

  • Support was added for the Related List Runtime Prompt type. This feature displays records from a related list on the Runtime Prompts page and allows the user to select which records should be merged into the document
    • Usage: Create a new Runtime Prompt and select the Related List type. Copy and paste the generated tags (e.g. <runtimeprompts>RTP-NAME</runtimeprompts>) into the <LineItemsSOQL> block that you want to display on the Runtime Prompts page at runtime. Check out this documentation article for more information
  • Added the “Insert Image” button to the S-Docs Live Edit page
  • Modified the Live Edit “Preview” button verbiage to “Preview Last Save,” allowing you to preview your last saved edits without saving again
    • This also adds the “Revert Last Save” button
    • The temporary document used to accomplish this feature is stored as an attachment on the S-Doc record
  • Support was added for conditional rendering in CSS
  • Support was added for <preprocess>true</preprocess> tags in Callable Apex definitions
    • This will cause the callable apex merge fields to be replaced first, then return the template XML without any other processing
  • Modified the functionality of the Delete Related Attachment upon S-Doc delete checkbox in the template editor to now delete related Salesforce File records upon S-Doc deletion as well
  • Support was added for the useDynamicViewLink parameter
    • Usage: If useDynamicViewLink=’true’, any event involving sending a document to external storage will refresh the View Link button
    • This also updates the View Link field on the SDoc object to be able to be set by a ‘document Uploaded to Box’ event
  • Removed Contact.Title as a default field when the template’s Related To Type is Contact
  • Added new global methods to allow for bulk updates of large numbers of templates via the Salesforce Developer Console
    • Example:
      List<SDOC__SDTemplate__c> sdtemplates = [SELECT Id FROM SDOC__SDTemplate__c];
      for (SDOC__SDTemplate__c sdtemplate : sdtemplates) {
      //modify templates here
      sdtemplate.SDOC__Template_XML__c = sdtemplate.SDOC__Template_XML__c.replace('####','#,###');
      }
      SDUtil.disableSDTemplateTrigger();
      update sdtemplates;
      SDUtil.enableSDTemplateTrigger();
  • Support was added for holding template XML source in an attachment when it’s too long for standard XML fields
  • Support was added for using the XML S-Doc Template Format with Mass Merge
    • This must be a template with a master tag. You can set your master tag in the Document Options tab in the Template Editor (under Mass Merge Settings)
  • Added a new custom setting “Allow Templates With Error to Generate,” which will convert non-critical errors to warnings, allowing users to generate templates that would previously halt upon the error
    • A warning message will still be displayed, but the templates will be able to be generated
  • Added the Product2 (Product2__c) field to the SDoc Relationship object, which prevents users from needing to create the field themselves after running into an Invalid Field error
  • Made noOutputIfEmpty=’true’ the default behavior for <template> tags
  • Ordered Org-Wide Email Addresses by label in the template editor, instead of email
  • The From picklist on the S-Docs email page now sorts by Display Name to Org-Wide Email Addresses
  • Support was added for date arithmetic 
    • Support was added for using YearsBetween with date arithmetic
      • Example: <MATH type="date">YearsBetween({{!Opportunity.createdByDate}},{{!Opportunity.closedate}}</MATH>
      • For more information, view our documentation article on arithmetic functions
  • Added parentheses encoding on Strings within render statements that are between quotes
    • Templates with render statements which are trying to compare strings that involve parentheses will require a new save for this new encoding to be applied
  • Support was added for LineItemsSOQL Render tags in the Named Query feature
  • Support was added for the checkbox=”black” and reverse_checkbox=”black” attribute for merge fields and related lists. This will merge in a checkbox image with a solid black border
    • You can use {{!Object.Field checkbox=”true”}} or {{!Object.Field checkbox}} to render the old checkbox image
    • We recommend using checkbox=”black” in S-Sign templates, as S-Sign will be using the new checkbox image
  • Support was added for re-uploading a PDF for PDF-Upload templates without moving any placed merge/input fields
  • The delete button for records in the S-Docs related list now asks for confirmation in Salesforce Lightning
  • Support was added for images and list styling for multi-level DOCX components
  • Support was added for pagination in the Insert Field, Insert Related List, and Insert Conditional Logic field picklists. This allows you to set how many fields should be displayed on each page of the picklist
    • The size of the page can be configured by setting the template editor Page Size custom setting to the number of fields per page desired. If no value is provided, the default page size is 995
  • Support was added for automatically populating custom lookup fields to the record specified by the S-Docs Jobs Oid__c field
    • This is useful for supporting any base object for the Mailing Labels template from the S-Docs Template Library
    • Example (standard object): Create a lookup field to Opportunity on the S-Docs Job Object with API Name Opportunity__c. When you create an S-Docs Job on an Opportunity, that lookup field will be populated with the corresponding Opportunity record and it can then be referenced in SOQL queries to grab fields from that Opportunity.
      • For custom objects, the lookup field API name should be exactly the same as the custom object name (e.g. if the object name is My_Custom_Obj__c, the lookup field API name should also end up being My_Custom_Obj__c)
      • Note that Account and Contact lookup fields come pre-packaged
  • Support was added for using the doclist parameter in PDF-Upload to generate other documents alongside the one-off
  • Added the “Download most recently uploaded XLSX” button to the Template Editor when the Template Format is XLSX
  • Added the “Download most recently uploaded PPTX” button to the Template Editor when the Template Format is PPTX
  • Support was added for JSON on the LineItemDataXML__c, RecordDataXML__c, and RecordData2XML__c fields for S-Doc Job
  • Support was added for creating new Salesforce Attachments each time a document is edited using the Live Edit feature
    • Usage: Check the Create New Attachment with Each Edit checkbox in the Document Options tab of the Template Editor. Each time you use the Live Edit feature to edit a document generated with that template, the S-Doc record’s data will be updated, a new attachment will be created and labeled with the attachment name and the date/time that the edit was made, and the name of the original document will be changed to mark it as the original
  • Removed querying of certain fields on standard objects by default (specifically linked Contacts and addresses for Account and Opportunity)
    • If someone is using special contact picklist fields, these fields will be queried, and the user will need to have access to all these fields. Otherwise, they are not applied since they are not needed
  • Modified the syntax for RTL styling
    • Usage: Use <rtl> instead of <span dir=”rtl”>
  • Modified the behavior of Mass Merge before email events to allow the user to edit the email and/or the attachment and then click a button to send the email
  • Support was added for merging external lists into S-Docs templates
    • Usage: External lists are specified as <LineItems> in a template and should have the attribute externalList="true" within <listname> tags. They are then populated based on the LineItemDataXML field of the corresponding SDJob. Please view this documentation article for more information
  • Support was added for inserting/updating license keys on the S-Docs License page
  • Support was added for translating the labels for Additional Fields and the drop down menus on the template selection page
  • Support was added for component template attributes
    • These are used to pass merge fields/information values into component templates
    • Usage: {{{{!ComponentName attribute="value"}}}}
    • Example:
      Parent Template: {{{{!Component example="{{!Object.Example__c}}"}}}}
      Component Template: {{!example}}
  • Updated our rich text editor to use pt instead of px
  • Removed Helvetica as a second option to the Arial font family
  • Removed “Yes” and “No” as the default output value for checkboxes. “True” and “False” are now the default output values
    • To opt into using “Yes” and “No” instead, set the yes_no attribute to true
    • Example: <column yes_no=”true”>...</column>

Related List Column Attributes

  • Removed case sensitivity for related list column attributes
  • Support was added for the escapeRenderOutput attribute on columns with a render attribute
    • Usage: If escapeRenderOutput =’false’, the results of the render will not be escaped

Merge Field Attributes

  • Removed case sensitivity for merge field attributes
  • Support was added for the display merge field attribute
    • Usage: If display=”true”, the merge field value will be translated based on translations defined in the Salesforce Translation Workbench. This attribute functions the same as the translate attribute
  • Support was added for translate, tolowercase, and touppercase merge field attributes
    • Example:  {{!Opportunity.Name translate=”true”}}
  • Altered strip-render’s behavior with parentheses to replace the ( and ) characters with their unicode ascii values rather than just removing them, so comparisons can still be made in render statements
    • If a complex render statement isn’t working as intended while using parentheses within a comparison string, you can use &#40; and &#41; in place of ( and ) in that comparison string
  • Applied strip-render to any merge field that has either the strip-render or usedInRender attribute set to true

S-Sign 2.141

Major Updates:

Refreshed S-Sign Panel UI

  • We didn't stop at refreshing the S-Docs Template Editor - the S-Sign panel got a new coat of paint, too. Build e-signature request templates using a modern, refined UI that's consistent with the rest of your document-building workflows.

Document Signing Order

  • Sending multiple documents in a single e-signature request? You can now specify the order in which each one should be signed. To learn more about the flexibility provided by this and other S-Sign template settings, please visit this documentation article.

Increased Flexibility for In-Progress Requests

  • Ever had an e-signature request halt due to a signer being out-of-office or otherwise unreachable? You can now resume an active S-Sign request as the current signer directly from Salesforce and keep the signature process moving.

Minor Updates:

General

  • Support was added for making S-Sign Date fields required. This will remove auto-population of the current date when the value is empty
  • Support was added for writing back to Salesforce number fields
  • Removed “Delete”, “View All” and “Modify All” permissions on all S-Docs and S-Sign objects in the S-Sign Site Guest User permission set per Salesforce Summer ‘20 requirements
  • Support was added for choosing whether the confirmation email is sent as one email to all signers or an email to each signer
    • This can be configured in the S-Sign panel in the template editor
  • Support was added for using merge fields for the Signed Document name and the Signed Document with Audit Trail name. You can find both fields in the S-Sign template settings
  • Set the owner of documents created during the signing process to the owner of the S-Sign Envelope Document they are related to
  • The Print Documents button on the generated documents page is now only available for in-person sign requests
    • This will only show up if the showSSignPrintDocuments parameter on the S-Docs button is set to “true”
  • Support was added for disabling Text-To-Signature org-wide
    • This can be configured on the S-Sign Configuration page by checking the When signing a S-Sign Request, prevent the signer from using the Text-To-Signature feature checkbox
  • Added the Reply To Email custom setting. This accepts a valid email address, which will be used as the Reply-To address for all S-Sign emails
  • Support was added for additional style on checkbox inputs
    • If adjusting checkbox size, include a height and a width measurement in px 
  • Modified S-Sign checkboxes to use the new solid black bordered checkbox image
    • These can be referenced in S-Docs version 4.314+ by using checkbox=”black”
  • Support was added for disabling the email requirement for Sign In-Person events
  • Support was added for disabling “intermediate” emails (i.e. “there are still X signers remaining…”)
  • Support was added for writing the signer’s typed name (applicable for signature and initial fields) back to Salesforce
  • Support was added for including the bounced email body in the bounced email notification
  • Support was added for modifying the resolution of PDFs on the mobile signing page using the Mobile PDF Page Resolution field in the S-Sign panel
    • The default resolution for desktop is 2.5, and the default value for mobile is 1.0. Higher values can cause longer load times
  • Updated the version of SendGrid used with Verification Code emails sent out from V2 to V3
    • This update was made to proactively avoid “406 Not Acceptable” errors
Jul 29
Love0

July 2020

By Release Notes

S-Docs 4.274

Major Updates:

New Template Migrator 

  • This new tool does exactly what it sounds like: It makes migrating templates from one org to another fast and easy. With this update you can migrate batches of templates between Salesforce orgs with ease, saving you time and resources for any deployments down the road. Check out more details in this documentation article. 

Arithmetic Functions

  • Avoid handling arithmetic in formula fields or Apex with this new feature. You can now leverage standard math functions directly in your S-Docs templates, helping your documents be smart and dynamic, just like you need them to be. Here’s more information to help answer questions about the new arithmetic functionality. 

Component Feature Enhancements  

  • Enhancements to the S-Docs Component template capabilities increase flexibility with customizations, and  allow for more sophisticated formatting.  You can now dynamically generate component templates using a simple related list query, making use cases like an Account report easier than ever to build. Check out this documentation article for more detailed information on how to use these component features. If you’re new to component templates, find out more about them here.

Minor Updates:

General

  • Added warning messages on the S-Docs email page when an email address that has been previously marked by Salesforce as bounced is entered in the To, CC, or BCC fields
  • Support was added for using the REPLACE tag to replace given substrings in a main string with input values in the S-Docs template editor
    • Example:
      REPLACE('main_string', 'replace this wherever it occurs in main_string', 'replace with this')
      REPLACE('{{!Opportunity.Long_Text_Field__c}}','User\'s example string \(a parenthesis\)','{{!Opportunity.Owner.Name}}')
      Note: Parentheses and single quotes must be escaped with \
  • Support was added for Table of Contents in DOCX templates
  • Adjusts use of render merge field attribute to also remove parentheses from a field’s content
  • Support was added for the AdditionalFields parameter to have field values with commas in them
    Note: Commas must be replaced with the following non case-sensitive placeholder: |-|COMMA|-|
  • Support was added for using the ReturnOrder and WorkOrder objects with Mass Merge
  • Support was added for the noOutputIfEmpty attribute for <template> tags in DOCX templates
    • Usage: If noOutputIfEmpty=”true”, this will prevent DOCX components that have no real value from adding additional lines to the template

Apex Button Parameters

  • Support was added for the previewFirst parameter
    • Usage: If previewFirst=”true”, after clicking Next Step to generate documents, a “Generate and Save” button will appear instead of the “Email Selected Docs” button. The “Generate and Save” button will create the attachments/files for the documents and create the SDRelationship record
    • If the “Generate and Save” button is not clicked, no attachment/file will be created nor an SDRelationship record
      Note: this is not currently supported for documents using job splitters

Related List Column Attributes

  • Support was added for the Rownum + X feature
    • Example: <column startIndex="3">rownum</column> 
    • If the rownum is 4, this will output 7
    • startIndex can be a negative value
  • Support was added for the <splitEvery> tag in lineitems and lineitemsSOQL
    • This is intended for use when building a list of components
    • Example: <splitEvery>5</splitEvery>
    • This will add a dynamic job splitter every fifth row
    • Limitation: Currently not supported for DOCX, PPTX, and XLSX formats
  • Support was added for the <tableend> tag in DOCX lineitems/lineitemsSOQL
    • Example: <tableend>]*insert table*[</tableend>
    • Intended to append pre-set table rows to the end of generated tables
  • Support was added for the related list <column…> attribute checkbox 
    • Usage: If checkbox=”true” a checked checkbox will render for true cells and unchecked for false cells
    • Using reverse_checkbox=”true” produces the opposite results
  • Support was added for column replaceAll placeholders: #LT#, #GT#, and #LINE_BREAK#
    • Syntax (omitting parentheses): Greater Than: (>), Less Than: (<), Line Break: (\n)
      GT - >
      LT - <
      LINE_BREAK - \n (This would be a line break in a non rich text field)
  • Support was added for using <nullprefix>, <nullpostfix>, <allprefix>, and <allpostfix> tags in components.

Merge Field Attributes

  • Support was added for using the merge field attribute translate in components
  • Support was added for the merge field attribute encrypt
    • Example: {{!Opportunity.EncryptedField__c encrypt}}
      Note: This is not supported for Named Query merge fields

S-Sign 2.108

Major Updates:

PDF Upload

  • Working with prebuilt PDF documents just got easier with S-Sign. Simply upload your PDF document, drag & drop signer fields, and route for signature. Could it be any easier? For more detailed instructions, check out this documentation article. 

Save Progress & Edit Later

  • S-Sign will save your progress at every step of the signing journey - from creating the signature request, to pausing in the middle of signing the final paperwork, rest assured your progress will be saved if you need to step away.

S-Sign Picklist Feature

  • This feature enables picklist options for your signature requests. Signers can choose from a drop-down list, and the data can be optionally written back to a field in Salesforce. These lists can be populated using existing Salesforce picklists, or you can create your own within the Template Editor. 

Minor Updates:

General

  • Added the Input Field Group feature. Using this feature, users can group checkbox fields together and set requirements for the group as a whole.
  • The use of custom email notification templates now requires assigning an S-Docs License to the S-Sign Site Guest User.
    • There is now a panel on the S-Sign Configuration Page (/apex/SSIGN__SSConfig) that you can use to assign the S-Sign Site Guest User a license. 
  • Support was added for adaptive font sizing for Text-To-Signature
  • Support was added for choosing if you want to attach the audit document and/or signed document to the base record. By default, only the audit document will be attached
    • This is available as a picklist in the S-Sign Template Settings
  • Adds a “Print Document” button next to the “E-Sign Documents in Person” button
  • Support was added for the “Omit Signer if” Signer Profile setting
    • This setting uses S-Docs Render syntax, and removes the signer profile from the S-Sign envelope document if the statement given is true
    • Functions similarly to the “Email address is provided by previous signer if” option
  • Support was added for applying styling to text input fields
    • Example:
      Field value is 500px
      Text input HTML: <input type=’text’ style=’width:500px;’>
    • Inputs to this field must use CSS syntax
    • 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 redirecting the signer to a custom URL after submitting a document
    • The custom URL can be defined in the “Redirect Signer to Page” field in the S-Sign Template  Settings
  • Support was added for listing multiple document names in emails when using the [[DOCUMENT_NAME]] S-Sign merge field
  • Support was added for creating a custom list of parties to notify upon document void, expire, or decline
  • Support was added for limiting what signer receives a copy of the signed document attached to the confirmation email
    • This is available as a checkbox on the Signer Profile settings
  • Support was added for copying attachments/files/documents from the initial signature request email onto the signature request email to all subsequent signers
  • Support was added for S-Docs attachment params to carry through to the CreateEnvelope page
  • Adds field “Email Address To Notify Upon Bounce” to S-Sign Envelope Document records
    • If this field is blank, the creator of the S-Sign request will be notified if the request bounces. If this field is filled in, the email address in this field will be notified, and the creator of the S-Sign request will not be notified
    • Updates bounce management feature to send a separate email for each request that has bounced
  • Adds the “Clear Attachments Upon Completion” checkbox to the S-Sign Template Settings
    • This will delete all of the files that S-Sign attached to the S-Sign Envelope Document once the last signer signs, including the unsigned document, signature images, and copy of signed document that does not include the audit trail
    • This will not delete the copy of the signed document that includes the audit trail, or user-created files
Apr 30
Love0

April 2020

By Release Notes

S-Docs 4.205

Major Updates:

Security 

  • At S-Docs, security is our top priority. We are constantly testing our security measures to ensure our application is as secure as possible and always in accordance with Salesforce standards. This rigorous testing has resulted in improved app functionality, and continues to differentiate S-Docs as the most secure solution for document generation & e-signature for Salesforce.  

Speed 

  • Generating documents quickly is one of our main differentiators. Over the past few months, we’ve improved our processing power and can now generate extremely large documents at the speed of a single-page generation….with just one click!   

Template Customization  

  • Ever wish you could add both Salesforce field labels and field values directly to your template? Now you can. We’ve added this feature to our template editor. This ensures that your field labels will always be accurate in your documents, even if you change them in Salesforce. It works with any base object, making it extremely versatile for a multitude of use cases. Here’s an example with the syntax for the Account object below: 
    • Syntax: {{!Label.Account.NumberOfClients}} - {{!Account.NumberOfClients}} 
    • Output: Number of Clients - 16

Using the S-Docs Named Query Feature? 

  • We’ve expanded on this feature allowing you to query for multiple records at the start of a template and reference the returned fields for any of those records as merge fields later in the template. This feature, designed for flexibility and avoiding redundancy, has become more powerful than ever before.

Minor Updates:

General

  • Support was added for collapsible Runtime Prompt options
  • Adds an option in the Document Options tab of the template editor to only create attachments when emails are sent
  • Support was added for attaching Lightning Knowledge files to emails
  • Support was added for lookup fields when using the <distinct>FieldName__c</distinct> feature for LineItemsSOQL queries
    • Example: <distinct>Lookup__r.FieldName__c</distinct>
  • An update was made to sort LineItems and LineItemsSOQL queries on the QuoteLineItem and OpportunityLineItem objects by the SortOrder field if no <orderby> tags are specified
    • This will not be applied to related lists containing <soql> tags
  • Support was added for special characters in DOCX rich-text fields
  • Support was added for sorting Mass Merge documents by a number value by adding the parameter “NUM” to the field labeled “When using this template in mass merge, sort the docs in the consolidated single doc by this field” on the Document Options tab in the template editor.
  • Adds field ObjSortVal__c to S-Doc object. This field can have base object record field data stored in it and then be sorted on when combining multiple documents into a single combined document
    • Example: SDJobTemplateController.combineSDocs('ORDER BY ObjSortVal__c ASC', 'PDF')
    • This update also adds the field ObjSortValFieldsForSDoc__c to the S-Docs Job object. This can be populated with a comma-delimited list of base object field names, which will then be used to populate the ObjSortVal__c on the generated S-Doc.
      • Usage: A user can insert an S-Docs Job with ObjSortValFieldsForSDoc__c set to something like Type,StageName and the corresponding field data values for the base object record will be stored in the S-Doc object’s ObjSortVal__c field 
  • Support was added for passing parameters into components to be used as merge fields.
    • Example:
      BASE TEMPLATE:
      <!--{{!<LineItemsSOQL>
      <component>Component_Template</component>
      <soql>SELECT Id FROM Opportunity WHERE AccountId='{{!Account.Id}}'</soql>
      </LineItemsSOQL>}}-->
      COMPONENT TEMPLATE:
      Opportunity ID: {{!Opportunity.id}}
      Opportunity Name: {{!Opportunity.name}}
      Opportunity StageName: {{!Opportunity.stagename}}
  • Support was added for disabling the “Allow Edit” option for all users regardless of template settings unless the current user's profile is whitelisted
    • Usage: To whitelist a profile, go to /apex/SDOC__SDConfig and enter the profile’s name in the "Whitelisted Profiles for Document Editing" text box. Note that separate profiles should be delimited by new lines in this text box.
  • Support was added for automatically linking a file or attachment to the parent object when a user has Auto-Create File or Auto-Create Attachment checked on line items objects.
    • This is because Salesforce does not allow you to create Files or Attachments on line items objects such as OpportunityLineItem.

Apex Button Parameters

  • Support was added for parameter AFEquals
    • Usage: If AFEquals=’true’, text-based additionalFields will be evaluated based on exact match rather than using ‘LIKE’
  • Support was added for parameter generatedFields to show fields from the template detail page on the generated documents page
    • Usage: Add generatedFields=’Base_Object_Type__c,Name’ to button code to show the related list object and the template name in columns in the table on the generated document page
  • Support was added for parameter useAttNameForDocName
    • Usage: If useAttNameForDocName=’true’, the attachment name will be used instead of the document name on the generated documents page
  • Support was added for parameter AFPicklist
    • Usage: If AFPicklist=’false’ it will hide the picklist that is shown on the template selection page when using the AdditionalFields=’...’ parameter
  • Support was added for the replyToMostRecentEmail
    • Usage: If replyToMostRecentEmail=’true’ it will include the most recent email's text in the body on the S-Docs email page

Related List Column Attributes

  • Support was added for queryname and queryname2 merge fields in LineItemsSOQL prefix/postfix column attributes
  • Support was added for the related list <column…> attribute escapeXMLChars
    • This will escape characters from the cell value that will cause XML parsing errors when included in XML tags
    • Example: <column escapeXMLChars="true" allprefix="<template lastname__c='" allpostfix="'>testing</template>">name</column>
  • Support was added for single quotes in the replaceAll attribute for related list columns
    • You must use #QUOT# in replaceAll first comma delimited string
      Example:
      <lineitems>
      <class>table1</class>
      <listname>attachments</listname>
      <column>bodylength</column>
      <column replaceAll="#QUOT#,#escqt#" >name</column>
      </lineitems>
  • Support was added for rendering HTML into the document when using the <column render="..."> feature
    • Example: <column render="RECORD.StageName == 'Closed',<span style='font-color:red;'>Closed</span>,Open">
  • Support was added for RENDER1 and RENDER2 when using the <column render="..."> feature
    • Example: <column render="RECORD.Country__c == germany,[RENDER1]RECORD.City__c == berlin,north[RENDER2]RECORD.City__c == munich,south[ENDRENDER2][ENDRENDER1]">id</column>

Merge Field Attributes

  • Support was added for the merge field attribute replaceAll
    • Example: {{!Opportunity.Some_Field__c replaceAll="..."}}
  • Support was added for the merge field attribute render
    • For use when evaluating text fields that may contain rich-text-like contents in render statements
    • Example: {{!Opportunity.Rich_Text_Containing_Field__c render}}
  • Support was added for merge field attribute mspin
    • Example: {{!Opportunity.Multi_Select_Picklist__c mspin="true"}}, which converts multi-select picklists to a format that works with the SOQL IN operator
    • Usage: You can use <soql>... WHERE Order_Number__c IN {{!Opportunity.Multi_Select_Picklist__c mspin="true"}}</soql> and this will evaluate to something like <soql>... WHERE Order_Number__c IN ('1','4','5')</soql> at runtime
  • Support was added for the merge field attribute URLENCODE 
    • Example: {{!Contact.LastName URLENCODE}}

S-Sign 2.78

Major Updates:

Improved Workflows 

  • New functionality has been added to S-Sign enabling users to send an S-Sign Request to multiple potential signers at once, without requiring a signing order. This makes sending S-Sign signature requests even easier.  

Customization Features 

  • We’ve added more customizable email notification templates that are sent when certain actions are taken during the lifecycle of an S-Sign request. These new templates meet the needs of more complex use cases and ensure your branding - logo, text, colors - is consistent across all touchpoints.
    • Templates include confirmation emails, declination emails, and deferral emails.
  • S-Sign now has improved email bounce handling. If your S-Sign signature request bounces, you can now change that recipient's email and resend it without having to generate a new request. This is also useful if you need to update any signer email addresses of an active signature request beyond the first signer.
  • S-Sign now supports Global License Assignment & Removal for large organizations. This cuts down the tedious admin work required during implementation, or upon an influx of new hires or personnel changes.  

Minor Updates:

General

  • Support was added for pre-setting the Signer Name field in the signature pad when available in the Signer Profile 
  • Adds “Email is provided by previous signer if” field on Signer Profiles
    • You can set this field to a RENDER expression (e.g. {{!Opportunity.StageName}} == ‘Closed’) and then if that expression evaluates to true, the signer will be prompted after signing to provide the email address of the signer with the profile where this field is populated (rather than the email being provided by the sender of the request)
  • Adds a variety of new special merge fields for S-Sign templates
  • Adds “Disable System Emails” setting in the S-Sign Template Settings which will disable all confirmation emails, e-signature request emails, etc.
  • Support was added for preventing certain signer profiles from getting audit records
    • Use case: If borrowers don’t need to see Audit records, but lenders should see them.
  • Support was added for default text inputs for Text SSign Fields. There are three options available: 
    • If you want to write back to Salesforce and have a default value upon opening the request 
      • Write back to filled in (Merge Field required) + Text Default filled in (Merge Field or plain text)
    • If you want to write back to Salesforce but not have a default value 
      • Write back to filled in + Text Default not filled in
    • If you don’t want to write back to Salesforce but do want a default value 
      • Write back to not filled in + Text Default filled in

For more information about these fields, click here.

Oct 10
Love0

October 2019

By Release Notes

S-Docs 4.34

Major Updates:

  • Runtime Prompts Writing Back to Salesforce
    • Using S-Docs Runtime prompts? Now you can write the responses logged from those Runtime prompts back to Salesforce. 
      • For example, let’s say you’re generating a contract that changes T&Cs depending on the recipient's state. A Runtime prompt will prompt the user with the question “What state is this T&Cs clause for?” and the user adds their response “California.” This enhanced function will enable that data to be written back to Salesforce.
        • Pro Tip: You can now save those responses and pre-populate them as needed for the next time you generate the document you’re working with. 
  • Box Integration 
    • S-Docs is now fully compatible with Box, a cloud document management and file sharing service. Our integration enables users to automatically store generated documents to their Box account. 
  • Even Faster Processing
    • Our product teams are constantly hard at work to ensure you always get your documents as fast as possible. New optimizations allow up to 10x faster generation for particularly complex files. 

Minor Updates:

  • General
    • Support was added for using Runtime Prompts merge fields in the Document Name field
    • Support was added for merge field attribute nullsub, which will insert a specified value in the event that a merge field returns a null value
      • Example - If you use {{!Opportunity.Quantity nullsub="0"}}, 0 will appear in the place of the merge field if the Quantity field is null
    • Adds field "Email Params" to the S-Docs Job object to accommodate various advanced parameters
      • Usage: you can use this field to add advanced parameters that are not available to access through standard fields on the S-Docs Jobs object. For example: &useExistingNoContactRecord=true&SetOrgWide=example@gmail.com
    • Support was added for RENDER in the <groupbyheader> tag
      • Example: <groupbyheader position="after-group">Product Name,Product Description,[!--RENDER={{!Opportunity.Name}} CONTAINS 'Burlington'--]Qty[!--ENDRENDER--],Unit Price,Total Price</groupbyheader>
  • XLSX
    • Support was added for leveraging the queryname feature in XLSX documents
    • Support was added for [{{!Opportunity.Quantity NUMBER}}] in XLSX documents
      • Use [{{!Opportunity.Quantity}}] to tell Excel to interpret the merge field as plain text, and [{{!Opportunity.Quantity NUMBER}}] to tell Excel to interpret the merge field as a numeric value
      • NUMBER must come at the end of the merge field, e.g. [{{!Opportunity.Quantity nullsub="0" NUMBER}}], rather than [{{!Opportunity.Quantity NUMBER nullsub="0"}}]
  • Related List Column Attributes

    • Support was added for related list <column ...> attribute "showcolumn" allowing you to conditionally hide a column, and <column render…> to conditionally show individual cells from a column
    • Support was added for parameters &attParentId2FilterAtt= and &attParentId2FilterFile= which will add filters to the queries on Attachments and Files whose parent record is specified by &attParentId2=
      • Example: &attParentId2=0066A000002ioH6&attParentId2FilterFile=ContentDocument.FileType=%27PDF%27%20AND%20
        ContentDocument.Title!=%27Contract%27
    • Support was added for related list column attribute replaceall, which supports regexs
      • Standard Syntax: <column replaceall="replaceThis1,replaceWithThis1,replaceThis2,replaceWithThis2,...replaceThisN,replaceWithThisN">
      • Regex Syntax: <column replaceall="[regex]([a-zA-Z]\)),&nbsp;&nbsp;&nbsp;&nbsp;$1">
      • This feature is very similar to the column substitute feature, with the following two exceptions:
        • Substitute matches against (and replaces) the ENTIRE string, whereas replaceall matches against (and replaces) all substring appearances of the specified string. Therefore, if the data value is "Burlington Textiles Corp", then replaceall="Burlington,My" would change the value to "My Textiles Corp".
        • There is no "else" condition in replaceall
    • Support was added for related list column attributes allprefix and allpostfix, which function the same as column attributes prefix and postfix except they are applied on null column values as well
      • This makes maintenance easier on templates that had columns with the same values for prefix and nullprefix

To read the full documentation on these advanced features click here.

  • Noteworthy Bug Fix
    • Fixes bug that temporarily broke <, <=, >, and >= operators in RENDER
      • RENDER would always evaluate to false even if the expression should've been true if any of these operators were used
      • This bug was only around for a brief period in versions 2.911-2.918

S-Sign 2.0

Major Updates:

  • Signing and Sending Multiple Documents
    • New updates have improved the overall signer experience. New signers are now brought directly to the signature page when opening an envelope and are able to see how many pending documents require signature. 
    • The sender experience has also been improved. You can now bundle multiple documents together and send them as one request. In addition, you can see the status and signer queue on the envelope. 
      • For example: Signer 2 of 5 Signed, or Signer 3 of 5 Rejected
  • Text-to-Signature
    • Now signers can choose to customize their signature with different cursive font options. Once selected, the adopted signature can be populated throughout the remaining inputs of the document.  
  • Expiration & Reminder Alerts
    • Reminding signers that their signature is pending is easier than ever. Just update the S-Sign envelope with a reminder alert set for a customized timeframe and an email alert will be sent from S-Sign on your behalf. 
    • Sending out an end of quarter contract? Now you can set an expiration so the S-Sign link expires on your specified date if the signer hasn’t executed as expected. 
  • Sleek new design added to the S-Sign audit trail and enhanced user experience throughout

Minor Updates:

  • Adds field "Active Signer" to S-Sign Envelope object. This field displays the profile name of the person who is currently being waited on to sign the request
  • Improves UI/UX of required input field types by placing red text saying "Required" next to required inputs that have not been provided.
    • Adds better messaging for the remaining input fields that require user attention before submitting the document
  • Support was added for using a custom logo on the S-Sign Verification splash screen
  • Support was added for using org-wide email addresses as the From Email Address in S-Sign requests sent via S-Docs Jobs
Close Menu
Top