All Posts By

Admin

S-Sign Security Update – April 2021

By Documentation, S-Sign No Comments

Note: These updates are required for all customers upgrading to S-Sign version 2.178+
S-Docs version 4.400 is required for S-Sign version 2.178+

Introduction

The S-Docs Development team is continuously striving to ensure our 100% native e-signature solution, S-Sign, employs the highest level of security. The S-Sign configuration steps have been slightly changed to align with Salesforce’s newest security recommendations. This article details the steps that you need to take to align with the latest updates.

Note: This article makes several references to your S-Sign Internal User. Your S-Sign Internal User is any licensed Salesforce user of your choosing. S-Sign operations that require internal data access will be conducted through this user's profile using the secure S-Docs Connected App. We recommend choosing a Salesforce Administrator.

Step 1. Create an S-Docs Connected App

The S-Sign security upgrades leverage Salesforce’s secure Connected Apps integration. If you are familiar with the S-Docs Run As User feature with the S-Doc Jobs object, you may have already created your S-Docs Connected App. If not, please navigate to this documentation article and follow the steps to create your S-Docs Connected App.

Note: For help troubleshooting your S-Docs Connected App configuration, please click here.

Step 2: Update Your S-Sign Site

Navigate to your S-Sign Site detail page. From the Setup menu, type "Sites" into the Quick Find bar, click Sites in the dropdown menu, and then click your S-Sign Site Label.

Click Edit to edit your Site, then uncheck the Lightning Features For Guest Users checkbox. Click Save.

Step 3: Remove Your S-Sign Sharing Settings

In previous versions of S-Sign, you may have configured Sharing Settings for the S-Sign Site Guest User. This security upgrade removes this requirement; therefore, these Sharing Settings should be removed.

From the Setup menu, type "Sharing" into the Quick Find bar, then click Sharing Settings in the dropdown menu.

From here, confirm for each S-Docs and S-Sign object that Default External Access is set to Private/Controlled by Parent. In addition, ensure that the Secure guest user record access checkbox is checked for each object.

Finally, remove any Sharing Rules created for the S-Sign Site Guest User (likely created on the S-Sign Envelope and SDoc Template objects). Be sure that the Sharing Rules you remove are specifically set for the S-Sign Site Guest User to prevent any issues outside of the S-Docs and S-Sign packages. Your Sharing Settings might look similar to the following:

Step 4: Set Your S-Sign Internal User and Assign Permissions

The S-Sign Internal User is a Salesforce user which all S-Sign operations are conducted by. All steps requiring internal data access will be performed by your S-Sign Internal User through the secure S-Docs Connected App. This was previously conducted by the S-Sign Site Guest User, which will no longer have access to any data in your internal org.

You likely set the username of your S-Sign Internal User when you completed Step 4 of the Connected App configuration guide. If you did not complete this step, navigate to Setup > Custom Settings > SDocsSettings, and enter the username of your chosen S-Sign Internal User into the ConnectedAppUserName field.

Note: We recommend using an administrator's username for the S-Sign Internal User.

After setting this Salesforce username, you need to assign the S-Sign Site Internal User Permission Set to said user. This is required for the S-Sign managed package processes.

From the Setup menu, type "Permission" into the Quick Find bar, click Permission Sets in the dropdown menu, then click on the S-Sign Site Internal User permission set.

Next, click Manage Assignments.

Then, click Add Assignments.

From there, choose the username that you specified as the S-Sign Internal User.

Once these steps are completed, you are ready to continue securely signing documents!


STAGING – S-Docs Documentation

By Staging No Comments


What is an S-Doc Job?

An S-Doc Job is a simple, intuitive Salesforce object designed for automatically generating (and optionally emailing) documents. S-Doc Jobs work in conjunction with Salesforce Process Builder, Apex triggers, or Flows.

Once a custom process, trigger, or flow creates the S-Doc Job record and populates its fields, S-Docs will begin generating documents. Certain fields will tell the Job which templates to generate, which object record to pull data from, whether or not the generated documents should be emailed, and much more.

S-Doc Job records contain three sections:

[1] Required fields that always need to be populated when a record is created
[2] Optional fields that allow you to customize the document automation process
[3] Job execution details that provide you with information about in-progress and finished jobs

This article will go through each section of an S-Doc Job record in detail.

Note: For instructions on setting up your process, trigger, or flow, please visit this article.

Access S-Doc Job Records

To access S-Doc Job records in your org, click the App Launcher in the upper left corner, type "S-Docs Jobs" into the search field, and click S-Docs Jobs.

This will take you to a list of all S-Doc Jobs that have been run recently in your org.

You can [1] click the SDJob Number to view individual S-Doc Job records, which we'll go over in the next section. You can also select multiple jobs and then [2] click Delete Logs to clear old S-Doc Jobs from this list. Clearing old records will have no effect on the S-Docs that they generated.

Required Fields

S-Doc Job records begin with the 5 fields that your custom process is required to populate. It appears as follows:

[1] Object ID: The ID of the base record that your documents will pull data from
[2] Object API Name: The API name of the base object
[3] Doclist: A comma-delimited list of S-Doc template names that the S-Doc Job will generate
[4] Send Email: Denotes whether or not the S-Doc Job should email the documents that it generates; 1 will email them, 0 will not

Note: An HTML email template should be included in the Doclist field if the Send Email field will be populated with "1."

[5] Start Job: A Boolean field that must be set to "true" for the S-Doc Job to begin generating documents

Note: The SDJob Number field auto-populates and does not need to be set.

As a reminder, these fields will all be set by a custom process, Apex trigger, or Flow -- not a Salesforce user. For reference, the process that created the above S-Doc Job record looks like this:

Optional Fields

Beyond the 5 required fields, your process, Apex trigger, or Flow can also set several optional fields. A subset of these fields can be found in the next section of the S-Doc Job record:

[1] Incl. Attachments with Email: Allows you to specify a comma-delimited list of Salesforce Attachment IDs to be included in the email sent out by the S-Docs Job
[2] Incl. Documents with Email: Allows you to specify a comma-delimited list of Salesforce Document IDs to be included in the email sent out by the S-Docs Job
[3] Incl. Files with Email: Allows you to specify a comma-delimited list of Salesforce File IDs to be included in the email sent out by the S-Docs Job
[4] Email From: Allows you to set an org-wide email address as the From address when your S-Docs Job process includes emailing a document
[5] Email Params: Allows you to add advanced email parameters to your process that are not available to access through standard fields on the S-Docs Job object, such as useExistingNoContactRecord=true

Note: The layout of the Optional Job Parameters section may look different based on the version of S-Docs that you're using. For a full list of S-Doc Job fields that can be populated, navigate to Setup > Object Manager > SDoc Job > Fields & Relationships.

S-Doc Job Execution Details

The final section of S-Doc job records includes execution details about the job. These fields aren't populated by a custom process, apex trigger, or flow; instead, they're filled in as the Job progresses. Let's take a look at the status fields before moving on to the other execution details.

S-Doc Job Status

The three S-Doc Job status fields are Status, Status Link, and Status Details.

[1] Status: Indicates Job percentage completed. The following table lists all possible S-Doc Job statuses and what they mean:

Status Meaning
Selected This only occurs on Jobs used with the Mass Merge feature when records are added to the Mass Merge list.
Queued This job is waiting on another job to be completed. By default, 45 jobs are processed at a time.
0 The S-Doc Job record was just created and is beginning to process.
10 The Run As User callout is in progress.
20 The Run As User callout is completed.
35 The S-Doc record was created and concurrent job splitter jobs are currently being processed (this only applies to Job Splitter templates in orgs with Concurrent Job Splitters enabled).
40 The S-Doc record(s) is being created.
60 The S-Doc record(s) was created successfully.
80 The Attachment or File is being created (if applicable) and the email is being sent (if applicable, and the email is non-S-Sign).
Pending File Creation All job processing is complete apart from File creation. This is only applicable for batches of File-enabled S-Docs created by the same user in a single transaction.
90 The Attachment or File was created successfully. If the templates are S-Sign-enabled, the S-Sign Envelope and S-Sign Envelope Documents are being created and emailed.
Completed The Job was completed successfully.
Retry Attempting to re-run a failed job (S-Docs may try to re-run a failed job up to 3 times depending on the cause of error).
Error The Job failed. Check the Status Details field for more information.
Error (Run As User Failed) The Run As User callout failed. Check the Status Details field for more info.

[2] Status Link: Provides a visual representation of Job percentage completed, as well as links to view the generated documents when it reaches 100%
[3] Status Details: Provides in-depth details about each stage of the S-Doc Job's status. This field can be consulted to find out more information about Job errors

Other S-Doc Job Execution Details

A few other notable fields in the Job Execution Details section include the following:

[1] SDoc1 View: Contains a link (document icon) to view the first document generated by the S-Doc Job
[2] SDoc1: Contains a link to the S-Doc record for the first document generated by the S-Doc Job
[3] SDoc2 View: Contains a link (document icon) to view the second document generated by the S-Doc Job
[4] SDoc2: Contains a link to the S-Doc record for the second document generated by the S-Doc Job

Additional Resources

To learn about setting up document automation with S-Docs Jobs in conjunction Salesforce Process Builder, Apex triggers, or Flows, please visit the following articles.

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

The S-Docs Setup Tab

By Documentation, S-Docs Install Config and Upgrade No Comments

Introduction

The S-Docs Setup page provides quick access to a number of different S-Docs administrative settings. This article will describe the functionality of each section on this page.

Locate S-Docs Setup

To navigate to the S-Docs Setup page, click the App Launcher in the upper left corner, type "S-Docs" into the search field, then click S-Docs Setup.

S-Docs Setup Sections

This article will now go over each section of the S-Docs setup page in detail.

S-Sign Setup

The S-Sign Setup section appears as follows.

[1] Go To S-Sign Setup Page: This button routes to the S-Sign Configuration Page, which contains a number of administrative configuration options for S-Sign including Salesforce Site information, email notification options, Guest User licensing, and more. Click here to learn more about the S-Sign Configuration Page.

[2] Go To S-Sign License Key Page: This button routes to the S-Sign License Key Page, where you can input and update your S-Sign license key and assign/remove user licenses. Click here to learn more about the S-Sign License Key Page.

S-Docs License Key

The S-Docs License Key section appears as follows.

Go To S-Docs License Key Page: This buttons routes to the S-Docs License Key Page, where you can input and update your S-Docs license key. Click here to learn more about installing S-Docs license keys and assigning licenses.

Migrate S-Docs & S-Sign Templates

The Migrate S-Docs & S-Sign Templates section appears as follows.

Go To S-Docs Migration Page: This button routes to the S-Docs Template Migrator, which allows you to import or export S-Docs templates between different Salesforce orgs. Click here to learn more about the S-Docs Template Migrator.

Translate UI

The Translate UI section appears as follows.

[1] Go To S-Docs UI Translation Page: This button routes to the S-Docs UI Translation Page, which allows you to create your own translations for the S-Docs end-user experience. Click here to learn more about the S-Docs UI Translation Page.

Note: For more information about translation options for S-Docs, click here.

[2] Go To S-Sign UI Translation Page: This button routes to the S-Sign UI Translation Page, which allows you to translate the S-Sign end-user experience. Click here to learn more about the S-Sign UI Translation Page.

Other Pages

The Other Pages section appears as follows.

[1] Go To Google Drive Integration Page: This button routes to the Google Drive Authentication Page. For full instructions on configuring the S-Docs & Google Drive integration, click here.

[2] Go To AWS S3 Integration Page: This button routes to the Amazon S3 Configuration Page. For full instructions on configuring the S-Docs & AWS integration, click here.

[3] Go To SendGrid Integration Page: This button routes to the SendGrid Configuration Page. This page allows you to enter your SendGrid API key for secure emailing.

[4] Go To Bulk DOCX Upload Page: This button routes to the Bulk DOCX Upload Page, which allows you to bulk-upload DOCX files and create an S-Docs template for each file. To learn more about the Bulk DOCX Upload page, click here.

Other Settings

The Other Settings section appears as follows.

[1] Whitelisted Profiles for Document Editing: This field allows you to list user profiles that should have access to the Live Edit feature (enabled for all users by default). Click here to learn more about this field.

[2] Do Not Include Extensions in File Names: When you check this box, S-Docs saved as Salesforce Files will not include the file extension name in the File's Title field.

[3] Update Settings: Click this button to update the settings in this section.


S-Doc Jobs

By Documentation, S-Docs One-Click and Zero-Click No Comments

What is an S-Doc Job?

An S-Doc Job is a simple, intuitive Salesforce object designed for automatically generating (and optionally emailing) documents. S-Doc Jobs work in conjunction with Salesforce Process Builder, Apex triggers, or Flows.

Once a custom process, trigger, or flow creates the S-Doc Job record and populates its fields, S-Docs will begin generating documents. Certain fields will tell the Job which templates to generate, which object record to pull data from, whether or not the generated documents should be emailed, and much more.

S-Doc Job records contain three sections:

[1] Required fields that always need to be populated when a record is created
[2] Optional fields that allow you to customize the document automation process
[3] Job execution details that provide you with information about in-progress and finished jobs

This article will go through each section of an S-Doc Job record in detail.

Note: For instructions on setting up your process, trigger, or flow, please visit this article.

Access S-Doc Job Records

To access S-Doc Job records in your org, click the App Launcher in the upper left corner, type "S-Docs Jobs" into the search field, and click S-Docs Jobs.

This will take you to a list of all S-Doc Jobs that have been run recently in your org.

You can [1] click the SDJob Number to view individual S-Doc Job records, which we'll go over in the next section. You can also select multiple jobs and then [2] click Delete Logs to clear old S-Doc Jobs from this list. Clearing old records will have no effect on the S-Docs that they generated.

Required Fields

S-Doc Job records begin with the 5 fields that your custom process is required to populate. It appears as follows:

[1] Object ID: The ID of the base record that your documents will pull data from
[2] Object API Name: The API name of the base object
[3] Doclist: A comma-delimited list of S-Doc template names that the S-Doc Job will generate
[4] Send Email: Denotes whether or not the S-Doc Job should email the documents that it generates; 1 will email them, 0 will not

Note: An HTML email template should be included in the Doclist field if the Send Email field will be populated with "1."

[5] Start Job: A Boolean field that must be set to "true" for the S-Doc Job to begin generating documents

Note: The SDJob Number field auto-populates and does not need to be set.

As a reminder, these fields will all be set by a custom process, Apex trigger, or Flow -- not a Salesforce user. For reference, the process that created the above S-Doc Job record looks like this:

Optional Fields

Beyond the 5 required fields, your process, Apex trigger, or Flow can also set several optional fields. A subset of these fields can be found in the next section of the S-Doc Job record:

[1] Incl. Attachments with Email: Allows you to specify a comma-delimited list of Salesforce Attachment IDs to be included in the email sent out by the S-Docs Job
[2] Incl. Documents with Email: Allows you to specify a comma-delimited list of Salesforce Document IDs to be included in the email sent out by the S-Docs Job
[3] Incl. Files with Email: Allows you to specify a comma-delimited list of Salesforce File IDs to be included in the email sent out by the S-Docs Job
[4] Include All Related Files: If checked, automatically attaches all files related to the base record to the email
[5] Email From: Allows you to set an org-wide email address as the From address when your S-Docs Job process includes emailing a document
[6] Email Params: Allows you to add advanced email parameters to your process that are not available to access through standard fields on the S-Docs Job object, such as useExistingNoContactRecord=true

Note: The layout of the Optional Job Parameters section may look different based on the version of S-Docs that you're using. For a full list of S-Doc Job fields that can be populated, navigate to Setup > Object Manager > SDoc Job > Fields & Relationships.

S-Doc Job Execution Details

The final section of S-Doc job records includes execution details about the job. These fields aren't populated by a custom process, apex trigger, or flow; instead, they're filled in as the Job progresses. Let's take a look at the status fields before moving on to the other execution details.

S-Doc Job Status

The three S-Doc Job status fields are Status, Status Link, and Status Details.

[1] Status: Indicates Job percentage completed. The following table lists all possible S-Doc Job statuses and what they mean:

Status Meaning
Selected This only occurs on Jobs used with the Mass Merge feature when records are added to the Mass Merge list.
Queued This job is waiting on another job to be completed. By default, 45 jobs are processed at a time.
0 The S-Doc Job record was just created and is beginning to process.
10 The Run As User callout is in progress.
20 The Run As User callout is completed.
35 The S-Doc record was created and concurrent job splitter jobs are currently being processed (this only applies to Job Splitter templates in orgs with Concurrent Job Splitters enabled).
40 The S-Doc record(s) is being created.
60 The S-Doc record(s) was created successfully.
80 The Attachment or File is being created (if applicable) and the email is being sent (if applicable, and the email is non-S-Sign).
Pending File Creation All job processing is complete apart from File creation. This is only applicable for batches of File-enabled S-Docs created by the same user in a single transaction.
90 The Attachment or File was created successfully. If the templates are S-Sign-enabled, the S-Sign Envelope and S-Sign Envelope Documents are being created and emailed.
Completed The Job was completed successfully.
Retry Attempting to re-run a failed job (S-Docs may try to re-run a failed job up to 3 times depending on the cause of error).
Error The Job failed. Check the Status Details field for more information.
Error (Run As User Failed) The Run As User callout failed. Check the Status Details field for more info.

[2] Status Link: Provides a visual representation of Job percentage completed, as well as links to view the generated documents when it reaches 100%
[3] Status Details: Provides in-depth details about each stage of the S-Doc Job's status. This field can be consulted to find out more information about Job errors

Other S-Doc Job Execution Details

A few other notable fields in the Job Execution Details section include the following:

[1] SDoc1 View: Contains a link (document icon) to view the first document generated by the S-Doc Job
[2] SDoc1: Contains a link to the S-Doc record for the first document generated by the S-Doc Job
[3] SDoc2 View: Contains a link (document icon) to view the second document generated by the S-Doc Job
[4] SDoc2: Contains a link to the S-Doc record for the second document generated by the S-Doc Job

Additional Resources

To learn about setting up document automation with S-Docs Jobs in conjunction Salesforce Process Builder, Apex triggers, or Flows, please visit the following articles.


S-Docs Concludes Record Year in 2020

By Press Release No Comments

Thursday, December 31, 2020

At the risk of using the most cliché word of the year, we’ll say it: 2020 was unprecedented. Change was on everyone’s docket on January 1st, but nobody foresaw the events that would upend the world in a matter of months.

For S-Docs, the pandemic meant office shutdowns, video calls, and lots of virtual team lunches. Yet despite the challenges of the year, 2020 saw us helping more customers streamline their Salesforce document and e-signature workflows than ever before. The year was packed with new product innovations, UI upgrades, record-breaking growth, and giving back to the community. 

As the year draws to a close, we’re reflecting on S-Docs’s leading highlights for 2020. Let’s see how our product’s strength and our team’s resilience enabled us to support our customers through adversity and continue giving back to the amazing Trailblazer community surrounding us. 

A Record-Breaking Year (In More Ways Than One)

Above all else, S-Docs is committed to trust, transparency, and first-rate security. Although the pandemic has turned the idea of long-term planning upside down, S-Docs was able to drive growth and support our customers this year through our unwavering commitment to our values. We are thrilled to report that we were able to shatter growth records every quarter, meaning that 2020 is our most successful year to date. This is a testament to our customers’ trust in the security, speed, and ease of use of our 100% native solutions.

As the pandemic has shown, broken records aren’t always a good thing. This year has also seen record high numbers of unemployment, virus cases, and businesses struggling to convert to remote work. That’s why S-Docs has also taken 2020 to ensure that our resources are helping wherever they can. 

For one, our document generation and e-signature solutions are built to facilitate working from anywhere. These vital functions have helped our customers maintain “business as usual” throughout the turbulent year. Additionally, our many partners in the healthcare industry have made use of S-Docs for safe contactless document processing.

S-Docs is also committed to the health and safety of every employee. That’s why we implemented a wellness program that ensures the team is equipped with the necessary resources to stay active and maintain optimum health while working from home. 

Finally, we’ve also pledged to match employee donations to nonprofit organizations throughout the world in an effort to give back to the community, both during this trying year and in years to come.

Welcoming New Customers and Partners

From continuous product improvement to giving back through the Pledge 1% program, none of our successes in 2020 would have been possible without our incredible customers. We had the opportunity to partner with new organizations in industries across the board this year, and saw massive developments in the government, healthcare, and financial service industries. Our native Salesforce architecture makes us a trusted solution for businesses that value data security highly, since S-Docs never sends data outside of the Salesforce cloud.

As we onboarded new customers, we also saw many existing S-Docs users expand their accounts as the ROI that document automation and e-signature achieved spoke for itself. S-Docs is able to create and e-sign any type of business document you can think of, meaning that multiple departments across an organization can benefit from its abilities.

In addition, we brought on several new partners this year, allowing us to expand our resources and help even more businesses with their Salesforce document and e-signature needs.

Introducing New Product Innovations

As we continue to grow, our products continue to get better and better. Our product teams were hard at work this year on optimizations, improvements, and new functionality aimed at satisfying our customers’ current needs and adapting to their unmet and emerging challenges.

You can read a full list of changes in our quarterly release notes, but here are a few of our favorite updates:

  • Revamped User Interface: We dove into the UI of our template editor and gave it a fresh coat of paint, making it easier to use while preserving the workflows that customers are used to. Take a look at more details in this blog post!
  • Drag & Drop: You can now upload any PDF to the S-Docs template editor and drag & drop merge fields and signature tags onto the document. This adds even more flexibility to the template-building experience.
  • Heightened Security: Security is our top priority at S-Docs. We put our application through rigorous testing to ensure it’s always employing first-rate data security standards on top of its secure native architecture. This has resulted in improved app functionality and continues to differentiate S-Docs as the most secure solution for document generation & e-signature for Salesforce. 

These are just a few of the exciting updates from 2020, and we’re not losing steam now. There’s plenty more to come in 2021, including further UI enhancements and lots of great new features, so stay tuned!

Growing Our Team & Getting Involved In The Community

Ensuring the success of our customers is only possible with a strong team of passionate individuals who champion our values. That’s why we expanded nearly every department around the globe with talented individuals committed to perfecting our product offerings and continually improving the customer experience. 

Although it wasn’t the year for in-person events, we still found ways to get involved in the Salesforce Trailblazer community. We started the year by collecting the expert advice of Salesforce MVPs and publishing their tips for the community on Salesforce best practices, productivity, and career growth. We also hosted several lunch & learns aimed at educating businesses on how to navigate remote work and get connected to the right solutions to help with business continuity.

As a proud member of the Pledge 1% program, we also sought to help and give back to the community wherever we could. Along with matching employee donations to nonprofit organizations, S-Docs organized a toy drive this holiday season to help families in need. We look forward to continuously doing our part as we move into the new year.

Get In Contact In 2021!

After a year like 2020, one thing’s become clear: no matter what 2021 has in store for us, we’re ready to meet those challenges head on and continue helping businesses digitalize, automate, and e-sign their Salesforce documents faster & more securely. Don’t want to miss out on the exciting innovations to come? Reach out to us! You can always leave us a message or contact sales@sdocs.com

For product updates, news, and leading developments in the document automation and e-signature worlds, you can also follow us on Twitter or LinkedIn. We’ll see you in 2021!

Headquarters

521 Fifth Ave
New York City, NY 10175

800-519-DOCS
       

S-Docs 2020 Year In Review

By Blog No Comments

At the risk of using the most cliché word of the year, we’ll say it: 2020 was unprecedented. Change was on everyone’s docket on January 1st, but nobody foresaw the events that would upend the world in a matter of months.

For S-Docs, the pandemic meant office shutdowns, video calls, and lots of virtual team lunches. Yet despite the challenges of the year, 2020 saw us helping more customers streamline their Salesforce document and e-signature workflows than ever before. The year was packed with new product innovations, UI upgrades, record-breaking growth, and giving back to the community.

As the year draws to a close, we’re reflecting on S-Docs’s leading highlights for 2020. Let’s see how our product’s strength and our team’s resilience enabled us to support our customers through adversity and continue giving back to the amazing Trailblazer community surrounding us.

A Record-Breaking Year (In More Ways Than One)

Above all else, S-Docs is committed to trust, transparency, and first-rate security. Although the pandemic has turned the idea of long-term planning upside down, S-Docs was able to drive growth and support our customers this year through our unwavering commitment to our values. We are thrilled to report that we were able to shatter growth records every quarter, meaning that 2020 is our most successful year to date. This is a testament to our customers’ trust in the security, speed, and ease of use of our 100% native solutions.

As the pandemic has shown, broken records aren’t always a good thing. This year has also seen record high numbers of unemployment, virus cases, and businesses struggling to convert to remote work. That’s why S-Docs has also taken 2020 to ensure that our resources are helping wherever they can.

For one, our document generation and e-signature solutions are built to facilitate working from anywhere. These vital functions have helped our customers maintain “business as usual” throughout the turbulent year. Additionally, our many partners in the healthcare industry have made use of S-Docs for safe contactless document processing.

S-Docs is also committed to the health and safety of every employee. That’s why we implemented a wellness program that ensures the team is equipped with the necessary resources to stay active and maintain optimum health while working from home.

Finally, we’ve also pledged to match employee donations to nonprofit organizations throughout the world in an effort to give back to the community, both during this trying year and in years to come.

Welcoming New Customers and Partners

From continuous product improvement to giving back through the Pledge 1% program, none of our successes in 2020 would have been possible without our incredible customers. We had the opportunity to partner with new organizations in industries across the board this year, and saw massive developments in the government, healthcare, and financial service industries. Our native Salesforce architecture makes us a trusted solution for businesses that value data security highly, since S-Docs never sends data outside of the Salesforce cloud.

As we onboarded new customers, we also saw many existing S-Docs users expand their accounts as the ROI that document automation and e-signature achieved spoke for itself. S-Docs is able to create and e-sign any type of business document you can think of, meaning that multiple departments across an organization can benefit from its abilities.

In addition, we brought on several new partners this year, allowing us to expand our resources and help even more businesses with their Salesforce document and e-signature needs.

Introducing New Product Innovations

As we continue to grow, our products continue to get better and better. Our product teams were hard at work this year on optimizations, improvements, and new functionality aimed at satisfying our customers’ current needs and adapting to their unmet and emerging challenges.

You can read a full list of changes in our quarterly release notes, but here are a few of our favorite updates:

  • Revamped User Interface: We dove into the UI of our template editor and gave it a fresh coat of paint, making it easier to use while preserving the workflows that customers are used to. Take a look at more details in this blog post!
  • Drag & Drop: You can now upload any PDF to the S-Docs template editor and drag & drop merge fields and signature tags onto the document. This adds even more flexibility to the template-building experience.
  • Heightened Security: Security is our top priority at S-Docs. We put our application through rigorous testing to ensure it’s always employing first-rate data security standards on top of its secure native architecture. This has resulted in improved app functionality and continues to differentiate S-Docs as the most secure solution for document generation & e-signature for Salesforce.

These are just a few of the exciting updates from 2020, and we’re not losing steam now. There’s plenty more to come in 2021, including further UI enhancements and lots of great new features, so stay tuned!

Growing Our Team & Getting Involved In The Community

Ensuring the success of our customers is only possible with a strong team of passionate individuals who champion our values. That’s why we expanded nearly every department around the globe with talented individuals committed to perfecting our product offerings and continually improving the customer experience.

Although it wasn’t the year for in-person events, we still found ways to get involved in the Salesforce Trailblazer community. We started the year by collecting the expert advice of Salesforce MVPs and publishing their tips for the community on Salesforce best practices, productivity, and career growth. We also hosted several lunch & learns aimed at educating businesses on how to navigate remote work and get connected to the right solutions to help with business continuity.

As a proud member of the Pledge 1% program, we also sought to help and give back to the community wherever we could. Along with matching employee donations to nonprofit organizations, S-Docs organized a toy drive this holiday season to help families in need. We look forward to continuously doing our part as we move into the new year.

Get In Contact In 2021!

After a year like 2020, one thing’s become clear: no matter what 2021 has in store for us, we’re ready to meet those challenges head on and continue helping businesses digitalize, automate, and e-sign their Salesforce documents faster & more securely. Don’t want to miss out on the exciting innovations to come? Reach out to us! You can always request a demo or contact sales@sdocs.com.

For product updates, news, and leading developments in the document automation and e-signature worlds, you can also follow us on Twitter or LinkedIn. We’ll see you in 2021!

See S-Docs In Action

Leave your Salesforce document workflow worries behind.

Request Demo

Enjoying our blog?

Subscribe now and we'll make sure to send you the latest as we publish new content!

Connect With Us!

For Salesforce news, digital document & e-signature insights, or just for fun.

        

Read More

Blog
April 3, 2024

Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions

  Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions Healthcare requires a lot of paperwork, from forms to letters to patient charts and treatment plans. Since much of the…
Blog
March 28, 2024

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation Government agencies have come a long way in the last few decades. Operations that used to be drowning in…
Blog
March 13, 2024

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty Picture this: You're strolling through a big box store and find yourself in the paper products section. As you…

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

How Native Salesforce Apps Reduce Total Cost of Ownership

By Blog No Comments

How much did the device you’re using to read these words cost? Seems like a simple question -- just dig up the receipt and you have your answer.

The thing is, the price you paid for the desktop, laptop, or mobile device that’s displaying this article probably isn’t equal to what it actually costs in the long run.

Sure, you might’ve taken home your laptop for $1000. But what about the time you spent setting it up, transferring files, and maybe even learning a new system? What if you run out of storage space and need an external hard drive? What happens when it requires repair after a hardware malfunction?

All of these are examples of additional costs taken on after you purchased your device, which can be factored into its total cost of ownership (TCO). TCO is an important consideration when making any type of business asset investment, from laptops to AppExchange solutions.

What is Total Cost of Ownership?

Total cost of ownership, sometimes called total lifecycle cost, is the total cost incurred during the useful life of an asset. The most obvious of these costs is purchase price -- the hard number listed on your invoice. But depending on the product or service that you’re evaluating, the purchase price is just the tip of the iceberg. Underneath are the hidden costs that aren’t always tangible from the get-go, but ultimately reveal themselves as you begin using the product.

Overall, the total cost of ownership covers short and long term costs of using a particular product. If you can find a product with a lower total cost of ownership, you’ll get more value and higher ROI out of that product in the long-run.

You Might Also Like: How Native Salesforce Apps Drive Innovation

How Do Native Salesforce Apps Reduce Total Cost of Ownership?

Total cost of ownership is especially important when it comes to evaluating different Salesforce AppExchange apps. Salesforce is a complex and incredibly powerful tool. The solutions you choose to extend and enhance its functionality should increase the ROI you already get from it -- in other words, you don’t want to commit to an app that ends up being more of a burden than a solution.

Luckily, native Salesforce apps like S-Docs are in the best position to minimize your total cost of ownership since they’re built directly on the Salesforce platform. Because of this, most traditional TCO considerations are shared with Salesforce and don’t apply to native apps like they would to off-platform solutions.

Let’s examine why native apps are the smart choice when it comes to maximizing value and minimizing the hidden costs underneath the iceberg.

Pre-Acquisition Costs

Total cost of ownership starts accumulating before you even sign an agreement. Time spent on research, security analysis, and trials must all be factored into the total cost of ownership for any solution. For larger enterprises, this process can take months and consume thousands of valuable hours.

When a business evaluates a native app, however, things can be expedited significantly. Native apps are architected on the Salesforce Lightning platform, meaning that they’re built on a platform that anyone using Salesforce has already approved. They automatically inherit Salesforce’s first-class data security standards.

There’s no need to pour months of time into evaluating whether or not a native app will keep your company’s data safe -- you can be sure from the beginning that your data will remain within the Salesforce cloud. However, be on the lookout for apps that claim to be native because their user interface lives in Salesforce -- oftentimes, they still send data outside of Salesforce on the backend for processing. Ensure you have the facts on what being native really means.

Setup and Deployment

The implementation process for native Salesforce applications is typically much quicker and easier than that for off-platform solutions, saving time for admins and avoiding disrupting production.

Since native solutions are really just an extension of your existing Salesforce setup, they blend more seamlessly with your environment -- no matter how many custom configurations you have. Setting them up is easier because they’re built using the tools that you’re already familiar with, as well as the same nomenclature and styling as Salesforce.

You Might Also Like: 4 Ways Native Salesforce Apps Are Transforming The Healthcare Industry

Training and User Adoption

Training and user adoption are important factors to consider when calculating your app’s total cost of ownership. How long will it take to skill up your users on the new application? Once they’ve been trained, will the application fit into their workflows, or will adoption be a constant struggle?

Like we said before, native apps are built to be an extension of your org, not a clunky integration. There’s no foreign system or syntax to learn. Users that already understand Salesforce will have a much easier time learning and using a native application over a non-native one.

Maintenance

Any business solution will require maintenance from time to time, whether due to minor issues or adapting to application upgrades. This can affect the total cost of ownership in the long run if time spent maintaining an app is exceeding the ROI gained from it.

Native apps are engineered by Salesforce experts who know how to optimize their solution to work with your favorite CRM. In other words, when you invest in a native app, you’re receiving a solution that’s tailored to the platform you use to carry out fundamental business activities. As a result, maintenance is required less frequently, and can often be carried out in-house. And if you ever get stuck, native apps provide support teams that are trained to work with Salesforce.

This also means that your native app will adapt as Salesforce does, and stay on top of its updates and latest features.

Licensing

By now, you know that native Salesforce apps are built on the Salesforce platform, run on Salesforce servers, and don’t work without Salesforce. So how does this relate to licensing costs?

Since native app providers aren’t paying for their own infrastructure to host and maintain their applications, they’re able to pass those savings along to their customers. You can be confident that you aren’t paying twice for infrastructure when you purchase a native app.

Data Security

When you hire a new employee and give them access to your company data, you’re taking on some level of risk. That’s why you use permission sets and sharing rules to control what different users can see and interact with.

Implementing a new application into your Salesforce org is no different. You’re bringing on a system that interacts with your data, meaning you’re taking on similar data security risks. Depending on your industry, the cost of a data breach could skyrocket your total cost of ownership and nullify any ROI achieved.

Native Salesforce applications process your data entirely on Salesforce servers. Your data is never required to leave your org, and native app providers aren’t able to see it. Your existing Salesforce security setup applies even when your data is being processed by a native app. And since data is never in transit between clouds, the surface area for breaches is greatly diminished.

You Might Also Like: How to Evaluate The Security of AppExchange Apps

Downtime

When you invest in a new business solution, you expect it to be up and running when you need it. Downtime can cause anything from a day of unnecessary manual work to thousands of dollars in lost productivity. And when you rely on applications hosted on other clouds, downtime can be unpredictable.

Understanding downtime for native Salesforce apps is much simpler: if Salesforce is up and running, so is your native app. And because Salesforce publishes their system performance and security status in real time, you’ll never be left guessing.

Scalability

Any good business solution will add value to your company and help you grow and meet your goals. But if your solutions can’t scale with your business, they may hinder you in the long run and increase the total cost of ownership.

As your Salesforce system grows and increases in complexity, native apps are ready to scale alongside your business. They’re made for the Salesforce platform and match Salesforce’s platform elasticity. Adding thousands of additional users won’t hamper any existing workflow -- the Salesforce Lightning platform infrastructure can handle it all.

In addition, native apps don’t count against your Salesforce org’s daily API limits, meaning that increased utilization of your native app won’t affect other processes in your org, or require purchasing additional API calls. By contrast, non-native applications may require multiple calls per invocation.

You Might Also Like: E-Signature For Salesforce: 3 Reasons Native Apps Are Better

Choose Native Salesforce Apps First

Native Salesforce applications are not a cure-all for every business challenge, but when you do find a fit, you’re likely to achieve a vastly higher ROI because your total cost of ownership will be lowered in so many areas. Native apps are generally faster, more scalable, and much more secure than their alternatives. In short, they’re built to be partners in growth and innovation with the businesses that use them.

Get Started with 100% Native Document Generation & E-Signature Today

S-Docs is the only 100% native document generation and e-signature solution available on the Salesforce AppExchange. S-Docs allows you to generate and e-sign sophisticated documents in seconds, with data merged in from anywhere in Salesforce. Since it’s built and hosted on the Salesforce Lightning platform, that data is processed entirely within Salesforce -- no whitelisting external IPs, approving third-party web connectors, or API calls involved.

When it comes to total cost of ownership, S-Docs is here to help you skyrocket your ROI and reduce lifetime expenses. In just a few minutes, you can download S-Docs from the AppExchange and build your first template. And if you’re itching to get started immediately, we’ve got you covered -- you can download premade templates from our extensive library and begin generating documents right away. S-Docs doesn’t charge fees per document or e-signature request, reducing your TCO even more and maximizing your lifetime value.

To find out more about what S-Docs can do for your business, get in touch with us! Our product experts would love to hear from you. Request a demo today or contact sales@sdocs.com

See S-Docs In Action

Leave your Salesforce document workflow worries behind.

Request Demo

Enjoying our blog?

Subscribe now and we'll make sure to send you the latest as we publish new content!

Connect With Us!

For Salesforce news, digital document & e-signature insights, or just for fun.

        

Read More

Blog
April 3, 2024

Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions

  Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions Healthcare requires a lot of paperwork, from forms to letters to patient charts and treatment plans. Since much of the…
Blog
March 28, 2024

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation Government agencies have come a long way in the last few decades. Operations that used to be drowning in…
Blog
March 13, 2024

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty Picture this: You're strolling through a big box store and find yourself in the paper products section. As you…

6 Key Business Documents You Should Be Automating [Part 2]

By Blog No Comments

A good document automation strategy is crucial for scalable business operations. But you can't automate everything - so what documents should you really be focusing on? Great candidates for automation meet four key criteria. These documents:

  • Are created frequently on a regular schedule
  • Take lots of time to put together manually
  • Require little to medium amounts of customization
  • Use data housed in a single source of truth (like Salesforce)

Now it’s time to look at three key documents that you can start automating today to increase efficiency, reduce errors, and make your business processes more secure:

  1. Invoices
  2. Customer Correspondence
  3. Account & Opportunity Summaries

Click here if you missed part one - and learn about 3 more key business documents to automate in Salesforce today.

Invoices

Once proposals are sent, quotes approved, and contracts signed, invoices ensure that you get rewarded for your efforts. All you have to do is put together a list of prices and payment terms, then send out the document and wait for the money to roll in...right?

If you’ve already read part 1 of this series, you’re probably picking up a pattern here -- creating these common documents is never as simple as it sounds, and invoices are no exception. Manually created invoices are prone to errors and tedious to get right (who would’ve guessed?), especially if there are multiple different ones to keep track of. It’s also difficult to maintain the same branding and style across multiple invoices, which can make you look unprofessional. Furthermore, invoices themselves aren’t the only problem -- when you leave payment reminders up to memory, you open the door to missed payments and much more work for your team.

Luckily, automation can save the day when it comes to invoices, too. Automating your invoice process is a step towards faster revenue attainment and a much smoother prospect-customer transition. When you generate your invoices with the click of a button or a field change, you ensure that the data is correct and the customer receives it as soon as it’s necessary, upping the chances of fast payment.

You May Also Like: 5 Security and Compliance Benefits of Salesforce Document Automation

If your new customers aren’t exactly jumping at the opportunity to respond to your invoices, document automation solutions have you covered there, too. You can configure payment reminders to be automatically sent at regular intervals or when deadlines approach, freeing up valuable time for sales and accounting. If you need to set up recurring invoices, that’s no problem, either.

With automated invoices, you’ll get paid faster, make your customers happier, and be confident that you are always sending polished, error-free documents. No matter where your team is, invoice automation ensures you’re running “business as usual” no matter how unusual things may get. Check out the S-Docs template library for pre-built invoices and other finance templates to start using today.

Customer Correspondence

Regular communication with your customers lets them know that they are valued by your organization, which increases their chances of renewing their account or recommending your products or services to others. Customer correspondence is key to maintaining positive customer relationships and a good reputation in your industry.

Creating personalized assets to send to customers is incredibly important, but it’s also extremely time consuming -- and when you have thousands of customers to communicate with, it quickly becomes impossible to handle manually.

Automating your customer correspondence documents -- whether it’s account welcome letters, Thank-Yous, invitations, vouchers, or anything else -- can be a lifesaver for small and large teams alike. The word “automation” might not immediately make you think “personalized,” but don’t let it fool you -- using templates that pull data from Salesforce and leverage the power of conditional logic, document automation solutions can create complex, highly personalized documents that make your customers feel valued.

You May Also Like: How to Design a Beautiful Document

We’re not the only ones who think you should be automating customer correspondence. Nestle, the world’s largest food and beverage company, sends and receives millions of types of customer correspondence on a daily basis -- think coupons, vouchers, giveaways, discounts, and more. When their initial automation system relied too much on manual efforts, they turned to S-Docs to fully automate the creation and execution of all customer communication. With the help of S-Docs, they’re now able to generate, print, and fulfill customer letters using a vastly improved workflow. Along with saved time and energy, S-Docs enables Nestle to maintain their brand promise and keep millions of customers happy.

Download these customer correspondence templates from our library to get started and spark your own automation ideas.

Account & Opportunity Summaries

Account and opportunity summary documents provide valuable information about the state of new business, current customers, and opportunities for expansion. Sales managers and executives often need the insights that these documents provide to make operational decisions and ensure goals are being met.

The problem with account and opportunity summaries is that getting them right requires digging up lots of data and then making it easy to understand. In an ideal world, all of the necessary information would reside on individual account or opportunity records, but this isn’t usually the case. Data is often scattered across objects, meaning that tracking it down can waste valuable time. And once you have it, it needs to be cleanly formatted, which can eat up just as much time.

Here’s the solution: build your account and opportunity summary documents with a document automation app, and never worry about getting them right again. Let’s say a sales manager requests an opportunity summary once opportunities reach a certain stage -- this is no problem with a document automation solution. Once a few pre-built templates are set up and automated, everything is done in the background.

You Might Also Like: 3 Tricks to Impressing Your Team and Consistently Over-Delivering

What’s more, document automation solutions that are built specifically for Salesforce don’t limit you to gathering data from one record, or even related records. Using a native solution like S-Docs, you can build powerful documents that query information across your entire Salesforce org and merge in things like Dashboards charts to provide clean, actionable insights in seconds.

You can also easily aggregate data to create sophisticated pipeline reports that go far beyond out-of-box Salesforce functionality. As long as the information is in Salesforce, it can be pulled together and customized to fit your business needs. Experience the power of document automation for reporting with these free templates.

Optimize Efficiency with Document Automation

The business landscape has been changing for quite some time, and if you’re aiming to gain an edge over the competition, slow and manual workflows just don’t cut it anymore.

The benefits of automating your documents are clear: productivity spikes, errors take a nosedive, and both employees and customers are happier as a result. Your team will be afforded the time to focus on higher-value work, which will translate to innumerable advantages down the road.

Document automation may not be the first thing that comes to mind when you think “digital transformation,” but it’s key to modernizing traditional business processes. The sooner it’s implemented, the sooner you’ll be set up for long-term business success, no matter what the world throws at you.

Get Started Today

S-Docs is the only 100% native document automation and e-signature solution available for the Salesforce platform. For over ten years, S-Docs has been helping businesses around the world automate their mission-critical documents and save thousands of hours of productivity.

It’s built entirely on the Salesforce platform -- that means no API calls, no network traffic between clouds, and no transporting your data anywhere. When you automate your documents with S-Docs, everything is 100% generated, delivered, and stored on Salesforce servers. Because of this, S-Docs is faster, much more secure, and easier to use than non-native alternatives.

Being native also means that S-Docs is powerful -- generate complex documents with data merged in from anywhere in Salesforce, multiple SOQL queries, conditional logic, nested templates, and much, much more.

Thousands of businesses rely on S-Docs every day to accomplish the tedious work in the background while they focus on what matters most. If you’re ready to join leading businesses around the world in automating and e-signing documents with S-Docs, request a demo today, or email us at sales@sdocs.com.

See S-Docs In Action

Leave your Salesforce document workflow worries behind.

Request Demo

Enjoying our blog?

Subscribe now and we'll make sure to send you the latest as we publish new content!

Connect With Us!

For Salesforce news, digital document & e-signature insights, or just for fun.

        

Read More

Blog
April 3, 2024

Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions

  Harmonizing Compliance and Operational Efficiency with Healthcare Automation Solutions Healthcare requires a lot of paperwork, from forms to letters to patient charts and treatment plans. Since much of the…
Blog
March 28, 2024

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation

Transforming the Federal Employee Experience with Salesforce and Government Digital Transformation Government agencies have come a long way in the last few decades. Operations that used to be drowning in…
Blog
March 13, 2024

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty

How Customer Communication Tools Help Consumer Goods Companies Build Brand Loyalty Picture this: You're strolling through a big box store and find yourself in the paper products section. As you…
Top