Release February 27, 2022

What's New

This release includes the following new features:

Session Access Code

This authentication method requires the agent to define an access PIN before starting the session with the customer. The PIN is a string of between 4 and 20 letters, numbers, and/or special characters (for example, ID/Social Security number, last digits of payment method, or spouse's name). The customer must enter the PIN to authenticate his identity and start the session. You can also create a custom opening screen for this type of authentication that provides a hint to what number the customer should enter.

Fixes and Improvements

• [Document] When using a right to left language configuration, a multi-line text field would cause inability to complete the document. This is now fixed.
• [Document] When a payment entity type attribute was configured on a PDF, values were not passing to the completed document. This is now fixed.
• [Workflows] A radio button field set as required can be passed. This is now fixed.
• [Admin Console] Sometimes OTP pin wasn't sent for an admin trying to access the Administration console. This is now fixed.
• [Configuration] Exported mapping required re-bind of attributes. This is now fixed.
• [Integrations] Sometimes, the workflowCompleted event was sent multiple times for the same content. This is now fixed.
• [API] Add esign v21.3 and v21.2 can now be used overlayTemplateId as described in the documentation.
• [Accessibility] When screen reader profile is activated, some visual elements were missing from the customer view. This is now fixed.
• [Salesforce] Authorize.net additional parameters (Transaction status, Transaction Description) were added to be sent back to salesforce 

Release timeline