-
Notifications
You must be signed in to change notification settings - Fork 7
v4 Release Notes
(3.139.x pre-release version)
After many delays this year, due to a new security review automatically scheduled by Salesforce after 5 years on the AppExchange, and exciting new features, we are finally pushing out version 4.0 of Simple Signature. This update is mandatory for all customers due to new security updates being released in Salesforce's Winter '21 update on, or around 10/17/2020 (the time and date for your organization's five-minute upgrade window is listed on status.salesforce.com).
- Mandatory
- Wednesday 09/30/2020 - 11:00 pm EST - 4.0 pre-release (3.139.x) available on the AppExchange for install
- Friday 10/02/2020 - 11:00 pm EST - 4.0 pre-release (3.139.x) update Pushed to all Sandboxes
- Friday 10/16/2020 - 11:00 pm EST - New 4.0 Update Pushed to All orgs (Production, Dev, Sandbox)
Please note that these dates do not apply if you are on an exclusion list.
This update bundles a large number of fixes and improvements in multiple areas. Below are a few new notable features since the last major version on the AppExchange. (For all updates, see our Change Log.)
DOCUMENTATION PAGE NUMBERS COMING BEFORE 4.0 RELEASE
Our new integration with Google Docs allows an admin to connect to a company (or personal) Google Docs account and build templates in Google Docs that then can be used to merge with Salesforce data. These documents can then be automatically sent via email for signature, and re-generated once a signature is collected. This feature is designed to augment the existing ability to generate PDFs using Visualforce or another document generator (sDocs, Conga, etc.).
This new Lightning page is faster and features improved design.
Due to security updates currently in many sandboxes and due to push to all orgs around October 17th, 2020, our Signature Request security has been completely rewritten to use a connected app which admins give access to in order to collect signature requests.
Lightning Web Signature forms are available in Actions for Lightning or Mobile, as well as embedded in Visualforce pages for Classic or for Signature Requests on Salesforce Sites (which use Visualforce pages only).
Previously, if you wanted a PDF to show up on a Signature Request page, it needed to be written into the Visualforce page. Now, simply setting the EmbedPDF field to TRUE will do the trick. It will take the document to be signed, generate it and attach it to Files or Attachments and then display it in the Signature Form.
Security has been improved with signature requests. We now collect information such as the IP Address, Lat/Long Geo Coordinates, and a Digital Signature, which indicates the device that was used to sign the form. In addition, we have signature expiration and passwords, which reduce the ability for the wrong person to sign a document. Finally, we have the option of signee acceptance of e-Signature usage.
Org-Wide Email addresses can now be set up so that a particular user can send out signature requests, rather than the user who creates the request. This enables a single person to be responsible for electronic signatures.
A plugin for Flows has been created which works as a node which can be attached anywhere in a flow that a signature needs to be collected.
SDocs is now fully supported in Classic as well as in Lightning. (Of course, we prefer that you use the new Google Docs integration!)
Rather than embedding multiple parameters in the URL of the Signature Form, you are now able to add a single parameter for an ExperienceID and then build out the Experience in our configuration page.
A new Lightning Page collects user signatures that can then be attached to a signature process so that after a Signature Requests is signed by the client, the Salesforce user's signature can be automatically added to the document before the final PDF is generated and attached to Salesforce and/or sent back to the client.
Signature Requests from multiple people are not available by simply marking a Signature Request as being a using Multiple Steps. The first Step is created automatically, and additional "Step" records can be created via Process Builder, each one either firing immediately, or waiting for prior signatures to be processed before being sent.