Release Oct 17, 2021

What's New

This release includes the following new features:

Conditional Signatures

Signatures, initials, and corporate stamps are not always required to be signed by the customer. For that, the business user can set a property for optional. However, what if the signature is required only in a specific case? For example, when the signer is over 18, or if the marital status is married? For these types of cases, we added the ability for the business user to add a visibility condition based on attributes. In case that the condition is met, the signature will be visible to the customer, else it won't be visible.

Fixes and Improvements

• [Document] Signatures appeared stretched in preview mode, this is now fixed.
• [Document] When an agent side required radio button was configured in a document, agents were unable to sign. This is now fixed.
• [Document] Cross-accounts documents were displayed as blank to customers. This is now fixed.
• [Document] % sign is displaying on the wrong side of the digit field in the completed document. This is now fixed.
• [Document] When force review is configured, the previous button sometimes appeared on the first page. This is now fixed.
• [Session] When customer name included an apostrophe (') character, cosigners received a new session for each document. This is now resolved.
• [Workflows] An agent side required attribute, nested under a radio button or checkbox, will now display a validation message when applicable.
• [Workflows] Sometimes a date in a form got displayed as the next day in the final document.
• [Workflows] In the Form designer, the "Cascade by" setting will now be saved.
• [Workflows] When editing the HTML in HTML designer, an empty line was added. This is now resolved.
• [Workflows] In a visual basket configuration, multiple elements under a radio button or checkbox are now displaying as expected.
• [BCP] BCP import now matches a phone number considering the configured prefix. 
• [API] Cosigner’s would not receive an invitation to join a session when using the CustomerID option via the Add Esign API.  This is now resolved.

Release timeline