April '24 Generally Available Release

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

S-Docs Updates

Supercharge Your Workflow With Batch Generation

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

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

Streamline Document Storage

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

Get Enhanced LWC Compatibility With Legacy Support

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

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

S-Sign Updates

Sign Once To Seal The Deal

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

Simplify User Authentication

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