Multi-signer web forms

Accounts that use Web Forms now have the ability to allow for multiple external recipients in the signature process.

Additional recipients are defined by the initial signer:

Use Library Templates to create Web Forms

Authors can now use existing Library Templates to create new Web Forms. The file is imported with all fields intact:

"Liquid Mode" enablement for mobile form filling

Liquid Mode is an optional feature for creating a version of your Adobe Sign agreements that is re-formatted for superior mobile viewing and form filling.

The Liquid Mode version of the document exists in parallel with the standard "PDF" version of the document.

Adobe Sign serves the appropriate format depending on the device in use by the recipient.

More details on the Liquid Mode option can be found here >

Lock the Name value for known users when signing via Image or Drawn signature methods

There are situations where the ability to change the name of the recipient during the signing ceremony is undesirable. Adobe Sign has provided flexibility in this regard in deference to the name preference of the Signer.  In more compliant environments this flexibility is unacceptable so there is a new control to lock the names of the recipients to the agreement.

Admins now have the ability to prevent recipients with known Name values from changing those values when they apply a Drawn or Image signature.

Situations where the name value is known:

• When sending to a recipient with an Adobe Sign ID
• When sending the name through the API
• When the Signer Info fields are completed during form filling
• When the name is locked during the completion of a KBA or Government ID authentication

Improvements to Knowledge-based Authentication

Controls have been added to the KBA method of identity authenticaiton that can require the sender to provide a Name for the recipient and that Name value is locked in place through the signature process.

Options for enhanced email security

Two new options are available to improve email security. Both settings are enabled by default:

• Include a link in emails to view the signed agreement
  
  • Enabled by default
  • When enabled, a link to the signed document is provided in the final email sent to the agreement recipients
• Include an image of the first page of the agreement in emails
  • Enabled by default
  • When enabled, an image of the first page of the agreement is visible in some email distribution
    

v6 REST API Updates

Standard Headers in every v6 REST API request

By default, every v6 REST API request now has the below standard headers:

/agreements

• All /agreements endpoints that have an agreement id path now return a 404 AGREEMENT_DESTROYED error code if the agreement has been deleted via GDPR tools.  

Library Templates

• PUT /libraryDocuments/{libraryDocumentId} - Expanded to include the new field ownerId
  

• GET /libraryDocuments - Expanded to include the new field ownerEmail
  

• GET /libraryDocuments/{libraryDocumentId} - Expanded to include the new fields: ownerId, ownerEmail, and ownerName

New fields in LibraryDocumentInfo object:

Fields with updated behaviour:

Web Forms (/widgets)

• POST /widgets - Using a libraryDocumentId to create a web form is now supported with a valid id

Added status code:

• PUT /widgets - Using a libraryDocumentId to create a web form is now supported with a valid id

Added status code:

• PUT /widgets/{widgetId} - Expanded to include the new field ownerId
  

Added status code:

• GET /widgets/{widgetId} - Expanded to include the new fields: ownerId, ownerEmail, ownerName, and creatorName
  

New fields in WidgetInfo object:

Fields with updated behaviour:

/Mega Sign

NEW:

• GET /megaSigns/{megaSignId}/formFields - Retrieves the form field details of a Mega Sign parent agreement

Parameters:

Response object:

• PUT /megaSigns/{megaSignId}/formFields - Updates the form fields of a Mega Sign agreement

Parameters:

Response object:

UPDATED:

• POST /megaSigns - AUTHORING has been added as a state value to support authoring a Mega Sign template
  • Changed Parameter:

• PUT /megaSigns/{megaSignId}/state - AUTHORING has been added as a state value to support authoring a Mega Sign template. As a result, megaSignCancellationInfo is no longer a required field
  

Experience changes for users

The modern Home and Manage page has been enabled for all remaining accounts

All accounts have had their control set updated to enable the modern Home and Manage pages for their users.

The controls in the admin menu remain available for accounts that must revert to the classic experience:

Adobe Sign service level and account ID exposed in Admin menu

Admins can now find their Account ID on the Global Settings page:

The Group ID can be found on the Group Settings page:

Explicit HIPAA configuration

There's a new page available that clearly shows when the account is enabled to manage agreements subject to HIPAA requirements.  

• This control is only exposed at the account level. Group-level admins do not have access
• This control is view only, to clearly indicate when the account is configure
  • Contact your success manager or support to enable HIPAA configuration
  More information on HIPAA settings can be found here >
  

Delegation of agreements with digital signatures

The ability to delegate an agreement with digital signatures affixed has been improved to allow delegation from the original email notification to the recipient, through automatic delegation when configured by a user, and through the Replace Current Signer action on the Manage page.

Updated interface for the Payments integration

The Payments interface has been updated to have the authenticating controls better exposed, creating an easier configuration process.

The maximum value for Data Governance has been increased to 5475 days (15 years)

Customers that use data governance rules to automatically delete agreements form the Adobe Sign system can now set that deletion date to a maximum of 15 years (up form ten).

The field level text label for validating the US Social Security Number has been updated:

The field level text label for validating the US Social Security Number has been updated to calrify the SSN is US predicated:

Reminder: Social Authentication has been removed

As announced in November, the authentication method using social identity has been removed from the list of authenticaiton methods in the Admin menu.

Reminder: Personal Twitter integration has been removed

As announced in December, the Users' ability to make personal authenticated connections to Twitter has been removed.

Account and group level Twitter features remain unchanged.

Inactive users will receive an email notification when included in an agreement

Users that are set to an Inactive status now receive an email notification instructing the recipient to delegate the agreement to another user.

Resolved Issues

Improved Functionality

Lock the Namevalue for known users when signing via Image or Drawn signature methods

There are situations where the ability to change the name of the recipient during the signing ceremony is undesirable. Adobe Sign has provided flexibility in this regard in deference to name preference by the Signer.  In more compliant environments this flexibility is unacceptable so there is a new control to lock the name to the agreement.

Admins now have the ability to prevent recipients with known Name values from changing those values when they apply a Drawn or Image signature.

Situations where the name value is known:

• When sending to a recipient with an Adobe Sign ID
• When sending the name through the API
• When the Signer Info fields are completed during form filling
• When name is locked during the completion of a KBA authentication or Government ID authentication

Experience changes for users

The text for agreement alerts on the post-send has been clarified to better articulate when alerts will trigger:

The new text aligns with the lauguage used in the configuration controls:

Resolved Issues

Configure data governance rules to automatically delete agreements

Customers that prefer to store their agreement records in their own systems, and want to delete the original documents from the Adobe Sign systems, can install a “retention policy” that asserts how long Adobe Sign should retain the transaction, and automatically delete the agreement (and optionally the supporting audit/personal data) from Adobe Sign after that timespan.

Retention rules are defined by an account-level admin in the Data Governance section of the admin menu.

Improved Signer Identity Report

The signer identity report (SIR) generated with the government ID authentication method is being improved to allow access to an interim version while the agreement is in progress.

Access the SIR from the Manage page by selecting the agreement (to open the Action rail on the right) and selecting the Download Identity Report action.

Setting a password is required to download the SIR, and that same password is required to view the resultant PDF:

The SIR clearly indicates if the report is interim or final:

Delegation of agreements with digital signatures

The ability to delegate an agreement with digital signatures affixed has been added to the recipient   e-sign page.

Suppress the Send page / Send from Workflows only

Accounts can suppress the Send page and route all agreements through controlled workflows designed by the administrators.

The Replace Recipient feature now applies to the Form Filler role

The ability to replace the current recipient now includes the Form Filler recipient role:

Expanded reason field for decline reason

The field user to provide the reason for declining an agreement has increased the number of characters that can be entered to 1000 (up from 255).

Improved authentication for Mobile Signature Capture

The mandatory mobile signature capture feature has been improved to detect if the supplied phone number is likely to be reachable. If it is detected that the number may be inappropriate to capture a text message, a warning is displayed. The user has the option to cancel or proceed:

The in product help feature has been updated

The in product help system has been updated in this release with an improved experience that works on the new Home and Manage page interface.

Accounts that have the feature enabled will see that the Guided Help tab floating on the right edge of the window has been replaced with a less obstructive question mark icon:

Admins can enabled or disable the in-app help system at the account and group level:

Experience changes for users

Customer-facing emails have removed the email link to support@echosign.com

The email notifications to users (eg: password reset emails) have removed the link to the legacy email address of the support team to promote the current contact policy

The Cancelation email has been clarified with regard to who is notified about the cancelation

The language in all cancelation templates has been improved to clarify that only the parties that have participated thus far in the agreement will be notified of the cancelation:

The Payments page has updated the user interface

Minor text and layout edits have been done to the Payments Integration page:

Resolved Issues

Multi-select action on the Manage page: Hide/Unhide

The new Manage page now allows the option to select multiple Agreement, Web Form, and Mega Sign records.

• When one record is selected, the right rail opens to show all actions that are available for the record
• If multiple records are selected, then the right rail is filtered to show only those actions that can be applied to all selected records

Default post-signing page (for unregistered recipients) has been updated to remove marketing content

All accounts have a new default post-signing page for recipients that are not registered Adobe Sign users.

The success message and a link to download a copy of what was just signed remain to inform the recipient and provide access to the agreement.

All marketing content and links to register for an active account have been removed.

Custom post-sign redirect URL

Admins have the option to define the URL their recipients are routed to once they have completed their actions with the agreement.

The post-signing URL can be configured at the account or group level.

• Group-level settings override the account-level settings
• API call parameters over-ride group/account-level settings
  

Post-sign redirect set to zero seconds by default

As of this release, all redirects have a default 0-second delay to redirect to a new page.

• This applies to automatic redirects (eg: the post-signing page; integrations) and API calls
• API calls can configure redirect delay in the API call if a greater delay is desired
  

Post-sign redirect message added to the esigning page footer

If a redirect is configured for an agreement (via UI or API), a message is added to the Click to Sign footer of the esigning page to alert the recipient that they are going to be redirected after signing.

• The redirect message: "Upon signing, sender requests you be redirected to domain.com"
  • domain.com is the domain name supplied in the specific URL redirect

Government ID authentication improvements

The Government ID authentication option has been improved with additional capabilities:

• Government ID authentication is now available to customer accounts based on Microsoft Azure cloud (EU2 and NA3)
• German National ID Card and Residence Permit have been added to the list of supported documents for identification

Improved reporting for the Hyperlink field

When pulling the .csv report for an agreement or template, the value in the Hyperlink field will now reflect the URL that the link delivered for the recipient, for external pointing links, and the page number for internal pointing links.

If the link is not clicked, the field remains empty.

• This replaces the previous convention of using the value "TRUE" if the field was clicked
  

New REST v6 API methods

Two new methods have been added to the REST v6 API:

• GET /libraryDocuments/{libraryDocumentId}/formFields -  Used to retrieve the details of the form fields on a library template
• PUT /libraryDocuments/{libraryDocumentId}/formFields - Used to update the details of form fields on a library template

REST v5 API update for replacing signer

The REST v5 API has been updated to ensure that only the sender of an agreement can replace the recipients. This may represent a significant change for customers accustomed to replacing recipients for other users.

This is particularly impactful for integrations that leverage the REST v5 API (eg: Salesforce).

Note: Advanced Account Sharing can be leveraged to overcome this new restriction (with Modify enabled).

Resolved Issues

Improved Functionality

Edit agreement elements after entering Authoring

The authoring environment has added a Back button, allowing the user to navigate back to the Compose page to make edits.

Elements that can be edited include:

• the agreement Name and Message
• the recipient email addresses
• the files attached to the agreement (add, delete, and reorder)

Once the edits are complete, the user clicks the Next button, and is returned to the authoring environment (with the updates in place).

Previously placed fields retain their configured values and Assigned to value (ie: Participant 1). 

• If the email address of any participant has changed, the new email value is substituted in without disrupting the field configuration
• Swapping out files will strip out any field placment for those removed files
  

Required Hyperlink fields

Hyperlink fields can now be configured as a Required field during the signature cycle.

When the Required option is checked, two new parameters are added to the properties of the field:

• Assigned to - Defines which recipient is required to click the field during their action for the agreement
  • One recipient can be explicitly required, forcing only that recipient to click the field before completing their action for the agreement
    • The link remains clickable for all recipients that are not required to click the link
  • Everyone is a new role available exclusively to the Hyperlink field, requiring all recipients to click the link before completing their action
    
• Tooltip - Provides for a text tooltip for the recipient when the field gains focus
  

Calculated Fields improvement with Currency formatting

Calculated fields that display their values formatted as Currency have new rules that dictate which currency symbol is displayed in the calculated value.

Note that calculated currency values can be derived from one or more source fields that validate their values as Number or Currency.

• If the source fields contain a currency validation for the US, the calculated value displays the US Dollar symbol: $
• If the source fields contain a currency validation for the UK, the calculated value displays the Pound sterling symbol: £

Improved Decline options for recipients

The option to allow a recipient to decline an agreement has been expanded to:

• expose the Decline button in the footer if the esigning page for all recipients assigned the Acceptor role

• allow the group and account-level admins to explicitly define a list of reasons the recipient can select from when declining the agreement

Read more about Decline options >

Advanced Account Sharing allows the Hide action for shared agreements with Modify permissions

Accounts that have enabled Advanced Account Sharing with Modify permissions will now see the option to Hide/Unhide agreements on shared accounts.

• This action is taken on behalf of the owner, meaning the hidden agreements are hidden in the owner's (and everyone else's) view.
  

REST v6 Updates

Define the lifespan of a signing URL

The GET /agreements/{agreementId}/signingUrls REST v6 API call added a new parameter: expiry.

• This parameter accepts a value between 30 and 315360000 seconds (~10 years)
• The default expiry time span for new customers is 1209600 seconds (14 days)
  
  • Existing customers will have the default value grandfathered to 3650 days
    • Existing customers that would like to have their default value reduced should contact their Success manager or Support to have the setting updated
      

Relative field positioning via REST v6

The POST /agreements REST v6 API call has been expanded to include a new optional attribute: formFieldGenerators. This allows fields to be programmatically positioned relative to specified strings found in the uploaded PDF document.

Personal Web Form API call

The existing REST v6 API call POST /widgets/{widgetId}/views API call has been expanded to include a new parameter: personalizedSigningViewConfiguration.

This parameter allows for personalized web forms.

Create/Rename/Delete Groups

Three new REST v6 API calls have been added to help manage groups via REST v6:

• Create a group: POST /groups - Create a new group in an account
  
• Rename a group: PUT /groups/{groupId} - Update an existing group
  
• Delete a group: DELETE /groups/{groupId} - Delete an existing group
  

Experience changes for users

API: Improved REST v6 DELETE calls for Privacy Administrators

Privacy Administrators can now call DELETE /agreements/{agreementId}/documents without the x-api-user header when using an account scoped token.

Audit Report text changed for final entry

The audit report no longer explicitly enumerates the list of participants (and their email addresses) in the last record.

The final event of the audit report now displays Agreement completed. with the time/date stamp of the event (in GMT):

Calculated Fields improvement with Currency formatting

Calculated fields that display their values formatted as Currency have new rules that dictate which currency symbol is displayed in the calculated value.

Note that calculated currency values can be derived from one or more source fields that validate their values as Number or Currency.

• If the source fields contain a currency validation for the US, the calculated value displays the US Dollar symbol: $
• If the source fields contain a currency validation for the UK, the calculated value displays the Pound sterling symbol: £

Mega Sign expiration dates

Mega Sign agreements will now honor the account/group level defaults for the automatic agreement expiration.

If there is a default value set at the account or group level, that value is imported into the Mega Sign creation process, and conferred to the child agreements:

Editing the expiration date of the (parent) Mega Sign object updates the expiration date of all remaining child agreements (that are still in-progress) to reflect the same expiration date.

• Editing a child agreement's expiration date is allowed, and is done by directly editing the child agreement
• Editing the parent Mega Sign object after editing a child agreement will align the child agreement to the new date set on the parent Mega Sign object
  

Searching agreements now returns records sorted by relevance

Searching in Adobe Sign now returns records with the most relevant results at the top, with the last date modified value being the last sorting criteria.

This adjustment improves the result of searching with multiple terms by elevating the agreements that match more terms to the top of the returned list of records.

Workflow Designer producing error messages

Due to improved security around the sharing of library assets, some workflows may start throwing a Server error message when editing the workflow after the September update:

Senders attempting to use a workflow with this problem are provided an error message that indicates the workflow contains documents that are our of scope:

This error means the workflow has lost the authority to use one or more of the attached library templates. Most commonly this happens when the template access permissions are changed from allowing the account/group access to limiting access to the owner.  

Admins should cancel out of this error message rather than reload the page.

To correct the error:

• The owner of the template should edit the template permissions to be available to the account/group that the workflow is bound to
• The owner of the workflow can replace the template with one with the appropriate permissions.  To do this cancel out of the error condition above and proceed to edit the workflow and replace the document

Resolved Issues