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

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
  • For more information, click here.
• 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.

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

S-Docs 2.910

Major Updates:

• Live Edit
  • This feature allows end-users to live-edit PDF documents in their browser. This improves flexibility without impacting compliance risk because the document never leaves Salesforce.
• Runtime Prompts with Decision Trees
  • Previously Runtime Prompts allowed you to prompt end-users to fill out information at run-time so the information would be dynamically inserted into the document. Now, with decision trees you can take this one step further by adding logic to prompt additional questions based off an end user's response.
    • Consider the following use case: A user needs to select which clause their contract should have: clause A or clause B. Then, if the user chooses clause A, the user should be prompted with questions 1, 2, and 3. Conversely, if the user chooses clause B, the user should be prompted with questions 4, 5, 6. Finally, with this new update, all the input provided by the user can be merged into the generated document. 
• Related List Render
  • Enhance your automation capabilities with Related List Render. For each column on each record in a related list, you can conditionally display anything you'd like based on the value of the data in that column.
    • Consider the following use case: your template has a related list of Opportunity Products, and for products that have a Quantity of 0, you need to display --NONE-- instead of 0 in the Quantity column. 
• Multi-Language User Experience
  • Users can now interact with S-Docs in their native language when creating and sending documents.
• Product Enhancements: 
  • We've implemented performance optimizations that improve S-Docs speed and power, allowing you to take on more complex projects.

S-Sign 1.934

Major Updates:

• Multi-Signer 
  • Now you have the ability to send a document to multiple people for signature. Here is detailed documentation: Multi-Sign How-to
• Multi-Language User Experience
  • Users can now interact with S-Sign in their native language when creating, sending and signing documents.
• Product Enhancements:
  • Enjoy a better user interface that makes S-Sign seamless and easy to use with Salesforce Lightning and the Salesforce Mobile App.