Adobe Sign release notes

The Adobe Sign release notes are ordered below with the current release at the top, and rolling back in time as you scroll down the page.

Release Highlights - May 2021

Improved Functionality

Transfer the ownership of library templates and web forms to a different user

Changing the owner of an asset can now be done by any administrator in the account that has access to the asset.

The administrator can assign the asset ownership to any user under their authority.

  • Account admins have access to all shared assets and all users. Therefore, account-level admins can reassign the ownership of any library template or web form to any other user in their account
    • If the asset is configured to only be available to one user (the owner), it is not shared and therefore unavailable to reassign to a new owner
  • Group administrators can only access library templates and web forms within the groups where they have administrator authority
  • Group administratorss can only reassign an asset to a user whose primary group falls under their administrative authority

More details can be found here >

Navigate to New Owner action


Updated API endpoints supporting asset transfer

The endpoints described below are only available in the v6 REST API.

PUT /libraryDocuments/{libraryDocumentId}

Extended to support update of library document owner.

LibraryDocumentInfo:

New Field

Type Required

Description

Action
ownerId String No Id of the library document owner. Will be ignored in POST requests. Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

PUT /widgets/{widgetId}

Extended to support update of widget owner.

WidgetInfo:

New Field

Type

Required

Description

Action

ownerId

String

No

Id of web form owner. Will be ignored in POST requests.

Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

GET /libraryDocuments

New fields in LibraryDocument object:

Name Type Description Note
ownerEmail

String Email address of the library document owner.
This field will be populated from Form.user_id.

 

GET /libraryDocuments/{libraryDocumentId}

New fields in LibraryDocumentInfo object:

Name Type Description Note
ownerId String Id of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email address of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of the library document owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.

 

Fields with updated behavior:

Name Type Description Current behavior New behavior
creatorEmail String Email address of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.
creatorName String Name of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.

 

GET /widgets/{widgetId}

New fields in WidgetInfo object:

Name

Type

Description

Note

ownerId

String

Id of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerEmail

String

Email of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerName

String

Name of web form owner. Will be ignored in POST/PUT requests.

This field will be populated from Form.user_id.

creatorName

String

Name of the web form creator. Will be ignored in POST/PUT requests.

This field will be populated from the Participation table.

 

Fields with updated behavior:

Name

Type

Description

Current behavior

New behavior

creatorEmail

String

Email of the web form creator. Will be ignored in POST/PUT requests.

Value from Form.user_id

This field will be populated from the Participation table.


Experience changes for users

The default v6 REST GET /workflows{workflowId} return value has changed

The v6 REST GET /workflows{workflowId} API call has been updated to return the current version of the WorkflowID (vs. the original version ID, which was the returned value prior to the May release)

This update aligns the default API experience with the Webhook experience, providing the same WorkflowID, which should improve the development and management of applications.

If, for any reason, your account requires the API to return the original ID (as it did prior to the May release), contact support to request that your account return the base version IDs for workflows.


Resolved Issues

Issue ID

Description

4283495 Updated the v6 REST GET /workflows{workflowId} API call to return the current version ID for the workflow instead of the original version ID
4296254 Corrected an issue where parallel recipients using the same email would not generate correct signing URLs when queried via API
4296987 Fixed an issue that could cause a recalled agreement to still show as in progress for the sender
4297040 Fixed a caching that could cause template reports to not update from the Manage page as expected
4300974 Fixed an issue where bulk uploading user changes would not change all values.
4301040 Fixed an issue where placing ※at the beginning of an agreement name would corrupt the rest of the name-value
4301913 Corrected an issue where the displayed number of admins in a group was incorrect
4302518 Fixed an issue where placing roman numerals at the beginning of an agreement name would corrupt the rest of the name-value
4302921 Corrected an issue that would strip commas out of the agreement name
4303402/4304263 Improved the read content for the "Read Agreement" control for screen readers
4303432 Updated the Signer role to import the recipient's name value when replacing a Stamp signature (instead of the initials)
4304096 Improved the Stamp image field size when using a docURL
4304679 Improved the read content for the "Download PDF" control for screen readers
4305532 Fixed an issue where agreements that enabled digital signatures with only one allowed provider would not pop up the signature login screen
4306073 Fixed an issue where group admins would not have access to contact Support
4307016 Fixed an issue where the dropdown menus were not visible on iPad devices

 

Release Highlights - March 2021

Improved Functionality


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:

12.0 Multi-signer web form


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:

Templates used fopr web forms


"Liquid Mode" in Adobe Sign for Mobile Viewing

Liquid Mode is an optional feature for generating a responsive view so you can improve the display of your documents based on the signer's device type.

The signed document is stored in the standard "PDF" version while the recipients can see the Liquid Mode on mobile phones and can toggle to view the original document.

You can now upload your HTML document and generate a Liquid Mode view for mobile phones.

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

Liquid Mode


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
More details on this feature can be found here >
Lock name values

Note:

This feature was reported in the February release, and is being re-announced for awareness.


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.

Lock KBA name


Options for enhanced email security

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

Email security options

Email template with options enabled


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:

Header Name Description
x-on-behalf-of-user The userId or email in the format userid:{userId} OR email:{email} of the user that has shared his/her account.

x-api-user

The userId or email of API caller using the account or group token in the format  userid:{userId} OR email:{email}.  If it is not specified, then the caller is inferred from the token.

If-None-Match Pass the value of the e-tag header obtained from the previous response to the same request to get a RESOURCE_NOT_MODIFIED(304) if the resource hasn't changed.

Authorization

An OAuth access token with correct scopes

Note:

Only the v6 REST API is impacted.

Any v6 REST API call that does not include these headers will explicitly document that absence.


/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

New Field

Type Required

Description

Action
ownerId String No Id of the library document owner. Will be ignored in POST requests. Updates form and origin participation.
HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.
Name Type Description Note
ownerEmail String Email address of the library document owner. This field will be populated from Form.user_id.

New fields in LibraryDocumentInfo object:

Name Type Description Note
ownerId String Id of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email address of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of the library document owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.

Fields with updated behaviour:

Name Type Description Current behaviour New behaviour
creatorEmail String Email address of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.
creatorName String Name of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.


Web Forms (/widgets)

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

Added status code:

Status Code ErrorCode Message
404 INVALID_LIBRARYDOCUMENT_ID-404 The Library Document ID specified is invalid
  • PUT /widgets - Using a libraryDocumentId to create a web form is now supported with a valid id

Added status code:

Status Code ErrorCode Message
404 INVALID_LIBRARYDOCUMENT_ID-404 The Library Document ID specified is invalid
New Field Type Required Description Action
ownerId String No Id of web form owner. Will be ignored in POST requests. Updates form and origin participation.

Added status code:

Code

ErrorCode

Message

400  

INVALID_NEW_OWNER

User-specified as a new owner is invalid.

403

INVALID_ASSET_OWNERSHIP_CHANGE

Ownership change cannot be made because the new owner is not a member of a group that the asset belongs to.

New fields in WidgetInfo object:

Name Type Description Note
ownerId String Id of web form owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email of web form owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of web form owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.
creatorName String Name of web form creator. Will be ignored in POST/PUT requests. This field will be populated from Participation table.

Fields with updated behaviour:

Name Type Description Current behaviour New behaviour
creatorEmail String Email of web form creator. Will be ignored in POST/PUT requests. Value from Form.user_id This field will be populated from Participation table.


/Mega Sign

NEW:

Entity

Value

Endpoint Operation /megaSigns/{megaSignid}/formFields
OAuth Scopes agreement_read
Request Header standard headers
Request Object empty
Parameters parameters (see below)
Response Object MegaSignFormFields
HTTP Status Code 200
Error Code error codes (no new error codes are being introduced)

Parameters:

Parameter

Description

Specify As

Required

megaSignId The Mega Sign identifier, as retrieved from the API to fetch Mega Sign documents. path Yes

Response object:

REST Object

Description

Comment

MegaSignFormFields List of the form fields in a MegaSign parent. Object that contains same fields as AgreementFormFields, response object in  PUT /agreements/{agreementId}/formFields 

 

Entity

Value

Endpoint Operation /megaSigns/{megaSignid}/formFields
OAuth Scopes agreement_write
Request Header standard headers
Request Object FormFieldPutInfo
Parameters parameters (see below)
Response Object MegaSignFormFields
HTTP Status Code 204
Error Code error codes (no new error codes are being introduced)

Parameters:

Parameter

Description

Specify As

Required

megaSignId The Mega Sign identifier, as retrieved from the API to fetch Mega Sign documents. path Yes
FormFieldPutInfo Existing model, used in  PUT agreements/{agreementId}/formFields body Yes

Response object:

REST Object

Description

Comment

MegaSignFormFields List of the form fields in a MegaSign parent. Object that contains same fields as AgreementFormFields, response object in  PUT /agreements/{agreementId}/formFields 

 

UPDATED:

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

Parameter

REST Object

Default

Description

Required

state

String

  • IN_PROCESS
  • AUTHORING  
None State of the Mega Sign Yes

 

  • 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

Parameter

REST Object

Default

Description

Required

state

String:

  • AUTHORING
  • IN_PROCESS
  • CANCELLED
None State of the Mega Sign Yes
megaSignCancellationInfo

megaSignCancellationInfo

None Cancellation information for the agreement. Mandatory while canceling a Mega Sign No


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:

v4 Home and Manage controls


Adobe Sign service level and account ID exposed in Admin menu

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

Account ID

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

Group ID


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
HIPAA page


The "Call to action" button has changed for customers using the Outlook Desktop application on Windows systems

Recipients that use an Outlook Desktop email client will see a change in the "call to action" button on Adobe Sign emails.

The new experience removes the blue HTML button, and instead supplies a clickable text link:

Office Desktop email change

Note:

This change only impacts Outlook Desktop apps on Windows systems. Other email clients and operating systems continue to receive the template with the blue button.


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.

Payment page


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:

US SSN label update


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.

Retire Social Identity


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.

Retire personal Twitter


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

Issue ID

Description

4271439 Corrected an issue where screen readers would not read the full error message
4271477 Fixed an issue where the Actions panel on the Manage page would not be visible in Portrait mode
4272437 Fixed an issue where the Authoring alignment control were not showing in portrait mode
4272439 Fixed an issue where the Authoring field property panel was not showing in portrait mode
4276305 Fixed a search issue on the new Manage page that would not return stemmed search patterns
4282423 Fixed an issue that would prevent page progression when using  pageSize in the GET /agreements and GET /libraryDocuments API call
4282983 Improved the US Social Security Number validation text to identify the format is for US  numbers only
4284071 Fixed an issue where the signature style would not fully disable when Bio-pharma settings are disabled
4284266 Corrected an issue where searching content in the Archive folder would not return all expected results
4284569 Corrected a localization error where English was being used  instead of the localized string when appending status to the end of a file name in the Signed and Filed email
4287513 Corrected an issue where a Checkbox inserted via Text Tag would still show the tick box after being hidden
4291368 Corrected an issue that could prevent the Upload Document option on the Manage page when a recipient delegates their signature in a workflow signature process
4291409 Improved error messaging when using Self-Sign and non-email authentication
4291503 Fixed an issue with the "Review and sign" link for Signature Requested emails in Outlook
4293239 Corrected the behavior of Mega Sign transactions when they are in a prefill or Sender signs first status to auto-expire after 24 hours
4293488 Corrected an issue where a completed document could show a "DOCUMENTS_NOT_YET_PROCESSED" status in the webhook payload
4293590 Fixed a state where users would see a bogus "Operation not allowed due account migration" error message
4294209 Corrected an issue where the Country dropdown for phone numbers was not exposed to screen readers
4294681 Fixed an issue on the JP1 shard that could cause Timestamp failures
4295459 Fixed a problem where the Signature button in an open agreement could not be tabbed to
4296379 Fixed an issue where an uploaded signature for a recipient could change the signature type requirement of the sending user
4296631 Improved the Signing reasons feature to display the reasons in the order defined by the admin control
4297720 Fixed an issue with the Dynamics package that would display error messages when attempting to send a reminder
4297868 Fixed an issue where a pop-up in Japanese could be presented for users that have English as their UI preference
4297990 Improved the functionality of the delegation process with regards to Phone authentication to ensure valid phone numbers are used
4298099 Fixed an error that would prompt an Agreement ID error on the Manage page
4298899 Corrected an issue where emails to the sender of an agreement would report the wrong name in the From: field
4298928 Fixed an issue where Groups: Sorting by 'Administrator' did not work properly
4299116 Fixed an issue where new users could be blocked from attaching documents in the web application
4299124 Improved the French localization for the Approve button
4299286 Corrected the response for the GET /agreements/{agreementId}/events API call when the document is shared
4299765 Fixed an issue where delegating Phone based authentication recipients would default to the US country code instead of the configured value
4300871 Corrected an issue where sending an agreement to authoring and then navigating back to Send could cause  "(Alias) first.last@adobe.com" to be listed as the signer
4301923 Corrected an issue where advanced account sharing could throw an error, despite approving the share
4302356 Fixed an issue that could cause multi-signers in web forms to not function properly
4303017 Fixed an issue that could cause a user to redirect to the login page after logging in.
4303087 Improved search when using apostrophes
4303532 Fixed an issue where PUT /libraryDocuments/{libraryDocumentId}/formFields would place the fields in the wrong location
Note:

Existing customer accounts, settings and customizations will not be impacted by any new features included in this release. Most features, when rolled out to an account, will be available for the account administrator to enable. Account administrators can gradually rollout new features within their account after completing appropriate validation and testing.


Previous Releases

Note:

The prerelease section contains highlights for the new features that are expected to be in the upcoming release.

None of the items/updates listed are guaranteed to make the final deployment, and some features may not be enabled at deployment. 

Prerelease Highlights - May 2021

Improved Functionality

Transfer the ownership of library templates and web forms to a different user

Changing the owner of an asset can now be done by any administrator in the account that has access to the asset.

The administrator can assign the asset ownership to any user under their authority.

  • Account admins have access to all shared assets and all users. Therefore, account-level admins can reassign the ownership of any library template or web form to any other user in their account
    • If the asset is configured to only be available to one user (the owner), it is not shared and therefore unavailable to reassign to a new owner
  • Group administrators can only access library templates and web forms within the groups where they have administrator authority
  • Group administratorss can only reassign an asset to a user whose primary group falls under their administrative authority
Navigate to New Owner action


Updated API endpoints supporting asset transfer

The endpoints described below are only available in the v6 REST API.

PUT /libraryDocuments/{libraryDocumentId}

Extended to support update of library document owner.

LibraryDocumentInfo:

New Field

Type Required

Description

Action
ownerId String No Id of the library document owner. Will be ignored in POST requests. Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

PUT /widgets/{widgetId}

Extended to support update of widget owner.

WidgetInfo:

New Field

Type

Required

Description

Action

ownerId

String

No

Id of web form owner. Will be ignored in POST requests.

Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

GET /libraryDocuments

New fields in LibraryDocument object:

Name Type Description Note
ownerEmail

String Email address of the library document owner.
This field will be populated from Form.user_id.

 

GET /libraryDocuments/{libraryDocumentId}

New fields in LibraryDocumentInfo object:

Name Type Description Note
ownerId String Id of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email address of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of the library document owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.

 

Fields with updated behavior:

Name Type Description Current behavior New behavior
creatorEmail String Email address of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.
creatorName String Name of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.

 

GET /widgets/{widgetId}

New fields in WidgetInfo object:

Name

Type

Description

Note

ownerId

String

Id of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerEmail

String

Email of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerName

String

Name of web form owner. Will be ignored in POST/PUT requests.

This field will be populated from Form.user_id.

creatorName

String

Name of the web form creator. Will be ignored in POST/PUT requests.

This field will be populated from the Participation table.

 

Fields with updated behavior:

Name

Type

Description

Current behavior

New behavior

creatorEmail

String

Email of the web form creator. Will be ignored in POST/PUT requests.

Value from Form.user_id

This field will be populated from the Participation table.


Experience changes for users

The default v6 REST GET /workflows{workflowId} return value has changed

The v6 REST GET /workflows{workflowId} API call has been updated to return the current version of the WorkflowID (vs. the original version ID, which was the returned value prior to the May release)

This update aligns the default API experience with the Webhook experience, providing the same WorkflowID, which should improve the development and management of applications.

If, for any reason, your account requires the API to return the original ID (as it did prior to the May release), contact support to request that your account return the base version IDs for workflows.


Resolved Issues

Issue ID

Description

4283495 Updated the v6 REST GET /workflows{workflowId} API call to return the current version ID for the workflow instead of the original version ID
4296254 Corrected an issue where parallel recipients using the same email would not generate correct signing URLs when queried via API
4296987 Fixed an issue that could cause a recalled agreement to still show as in progress for the sender
4297040 Fixed a caching that could cause template reports to not update from the Manage page as expected
4300974 Fixed an issue where bulk uploading user changes would not change all values.
4301040 Fixed an issue where placing ※at the beginning of an agreement name would corrupt the rest of the name-value
4301913 Corrected an issue where the displayed number of admins in a group was incorrect
4302518 Fixed an issue where placing roman numerals at the beginning of an agreement name would corrupt the rest of the name-value
4302921 Corrected an issue that would strip commas out of the agreement name
4303402/4304263 Improved the read content for the "Read Agreement" control for screen readers
4303432 Updated the Signer role to import the recipient's name value when replacing a Stamp signature (instead of the initials)
4304096 Improved the Stamp image field size when using a docURL
4304679 Improved the read content for the "Download PDF" control for screen readers
4305532 Fixed an issue where agreements that enabled digital signatures with only one allowed provider would not pop up the signature login screen
4306073 Fixed an issue where group admins would not have access to contact Support
4307016 Fixed an issue where the dropdown menus were not visible on iPad devices

Improved Functionality

Transfer the ownership of library templates and web forms to a different user

Navigate to New Owner action


Updated API endpoints supporting asset transfer

The endpoints described below are only available in the v6 REST API.

PUT /libraryDocuments/{libraryDocumentId}

Extended to support update of library document owner.

LibraryDocumentInfo:

New Field

Type Required

Description

Action
ownerId String No Id of the library document owner. Will be ignored in POST requests. Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

PUT /widgets/{widgetId}

Extended to support update of widget owner.

WidgetInfo:

New Field

Type

Required

Description

Action

ownerId

String

No

Id of web form owner. Will be ignored in POST requests.

Updates form and origin participation.

 

Additional Error Status Codes:

HTTP Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

GET /libraryDocuments

New fields in LibraryDocument object:

Name Type Description Note
ownerEmail

String Email address of the library document owner.
This field will be populated from Form.user_id.

 

GET /libraryDocuments/{libraryDocumentId}

New fields in LibraryDocumentInfo object:

Name Type Description Note
ownerId String Id of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email address of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of the library document owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.

 

Fields with updated behavior:

Name Type Description Current behavior New behavior
creatorEmail String Email address of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.
creatorName String Name of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.

 

GET /widgets/{widgetId}

New fields in WidgetInfo object:

Name

Type

Description

Note

ownerId

String

Id of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerEmail

String

Email of web form owner. Will be ignored in POST requests.

This field will be populated from Form.user_id.

ownerName

String

Name of web form owner. Will be ignored in POST/PUT requests.

This field will be populated from Form.user_id.

creatorName

String

Name of the web form creator. Will be ignored in POST/PUT requests.

This field will be populated from the Participation table.

 

Fields with updated behavior:

Name

Type

Description

Current behavior

New behavior

creatorEmail

String

Email of the web form creator. Will be ignored in POST/PUT requests.

Value from Form.user_id

This field will be populated from the Participation table.


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:

12.0 Multi-signer web form


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:

Templates used fopr web forms


"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 >

Liquid Mode


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
More details on this feature can be found here >
Lock name values

Note:

This feature was reported in the February release, and is being re-announced for awareness.


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.

Lock KBA name


Options for enhanced email security

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

Email security options

Email template with options enabled


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:

Header Name Description
x-on-behalf-of-user The userId or email in the format userid:{userId} OR email:{email} of the user that has shared his/her account.

x-api-user

The userId or email of API caller using the account or group token in the format  userid:{userId} OR email:{email}.  If it is not specified, then the caller is inferred from the token.

If-None-Match Pass the value of the e-tag header obtained from the previous response to the same request to get a RESOURCE_NOT_MODIFIED(304) if the resource hasn't changed.

Authorization

An OAuth access token with correct scopes

Note:

Only the v6 REST API is impacted.

Any v6 REST API call that does not include these headers will explicitly document that absence.


/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

New Field

Type

Required Description

Action

ownerId String No Id of the library document owner. Will be ignored in POST requests. Updates form and origin participation.

Code

ErrorCode

Message

400  

INVALID_NEW_OWNER

User-specified as a new owner is invalid.

403

INVALID_ASSET_OWNERSHIP_CHANGE

Ownership change cannot be made because the new owner is not a member of a group that the asset belongs to.

 

Name Type Description Note
ownerEmail String Email address of the library document owner. This field will be populated from Form.user_id.

 

New fields in LibraryDocumentInfo object:

Name Type Description Note
ownerId String Id of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email address of the library document owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of the library document owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.

Fields with updated behaviour:

Name Type Description Current behaviour New behaviour
creatorEmail String Email address of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.
creatorName String Name of the library document creator. Will be ignored in POST/PUT requests. Value from Form.user_id Value from Participation table.


Web Forms (/widgets)

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

Added status code:

Status Code ErrorCode Message
404 INVALID_LIBRARYDOCUMENT_ID-404 The Library Document ID specified is invalid

 

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

Added status code:

Status Code ErrorCode Message
404 INVALID_LIBRARYDOCUMENT_ID-404 The Library Document ID specified is invalid

 

New Field Type Required Description Action
ownerId String No Id of web form owner. Will be ignored in POST requests. Updates form and origin participation.

Added status code:

Status Code ErrorCode Message
400 INVALID_NEW_OWNER User specified as a new owner is invalid.
403 INVALID_ASSET_OWNERSHIP_CHANGE Ownership change cannot be made because new owner is not a member of group that asset belongs to.

 

New fields in WidgetInfo object:

Name Type Description Note
ownerId String Id of web form owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerEmail String Email of web form owner. Will be ignored in POST requests. This field will be populated from Form.user_id.
ownerName String Name of web form owner. Will be ignored in POST/PUT requests. This field will be populated from Form.user_id.
creatorName String Name of web form creator. Will be ignored in POST/PUT requests. This field will be populated from Participation table.

Fields with updated behaviour:

Name Type Description Current behaviour New behaviour
creatorEmail String Email of web form creator. Will be ignored in POST/PUT requests. Value from Form.user_id This field will be populated from Participation table.


/Mega Sign

NEW:

Entity

Value

Endpoint Operation /megaSigns/{megaSignid}/formFields
OAuth Scopes agreement_read
Request Header standard headers
Request Object empty
Parameters parameters (see below)
Response Object MegaSignFormFields
HTTP Status Code 200
Error Code error codes (no new error codes are being introduced)

Parameters:

Parameter

Description

Specify As

Required

megaSignId The Mega Sign identifier, as retrieved from the API to fetch Mega Sign documents. path Yes

Response object:

REST Object

Description

Comment

MegaSignFormFields List of the form fields in a MegaSign parent. Object that contains same fields as AgreementFormFields, response object in  PUT /agreements/{agreementId}/formFields 

 

Entity

Value

Endpoint Operation /megaSigns/{megaSignid}/formFields
OAuth Scopes agreement_write
Request Header standard headers
Request Object FormFieldPutInfo
Parameters parameters (see below)
Response Object MegaSignFormFields
HTTP Status Code 204
Error Code error codes (no new error codes are being introduced)

Parameters:

Parameter

Description

Specify As

Required

megaSignId The Mega Sign identifier, as retrieved from the API to fetch Mega Sign documents. path Yes
FormFieldPutInfo Existing model, used in  PUT agreements/{agreementId}/formFields body Yes

Response object:

REST Object

Description

Comment

MegaSignFormFields List of the form fields in a MegaSign parent. Object that contains same fields as AgreementFormFields, response object in  PUT /agreements/{agreementId}/formFields 

 

UPDATED:

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

Parameter

REST Object

Default

Description

Required

state

String

  • IN_PROCESS
  • AUTHORING  
None State of the Mega Sign Yes

 

  • 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

Parameter

REST Object

Default

Description

Required

state

String:

  • AUTHORING
  • IN_PROCESS
  • CANCELLED
None State of the Mega Sign Yes
megaSignCancellationInfo

megaSignCancellationInfo

None Cancellation information for the agreement. Mandatory while canceling a Mega Sign No


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:

v4 Home and Manage controls


Adobe Sign service level and account ID exposed in Admin menu

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

Account ID

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

Group ID


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
HIPAA page


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.

Payment page


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:

US SSN label update


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.

Retire Social Identity


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.

Retire personal Twitter


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

Issue ID

Description

4271439 Corrected an issue where screen readers would not read the full error message
4271477 Fixed an issue where the Actions panel on the Manage page would not be visible in Portrait mode
4272437 Fixed an issue where the Authoring alignment control were not showing in portrait mode
4272439 Fixed an issue where the Authoring field property panel was not showing in portrait mode
4276305 Fixed a search issue on the new Manage page that would not return stemmed search patterns
4282423 Fixed an issue that would prevent page progression when using  pageSize in the GET /agreements and GET /libraryDocuments API call
4282983 Improved the US Social Security Number validation text to identify the format is for US  numbers only
4284071 Fixed an issue where the signature style would not fully disable when Bio-pharma settings are disabled
4284266 Corrected an issue where searching content in the Archive folder would not return all expected results
4284569 Corrected a localization error where English was being used  instead of the localized string when appending status to the end of a file name in the Signed and Filed email
4287513 Corrected an issue where a Checkbox inserted via Text Tag would still show the tick box after being hidden
4291368 Corrected an issue that could prevent the Upload Document option on the Manage page when a recipient delegates their signature in a workflow signature process
4291409 Improved error messaging when using Self-Sign and non-email authentication
4291503 Fixed an issue with the "Review and sign" link for Signature Requested emails in Outlook
4293239 Corrected the behavior of Mega Sign transactions when they are in a prefill or Sender signs first status to auto-expire after 24 hours
4293488 Corrected an issue where a completed document could show a "DOCUMENTS_NOT_YET_PROCESSED" status in the webhook payload
4293590 Fixed a state where users would see a bogus "Operation not allowed due account migration" error message
4294209 Corrected an issue where the Country dropdown for phone numbers was not exposed to screen readers
4294681 Fixed an issue on the JP1 shard that could cause Timestamp failures
4295459 Fixed a problem where the Signature button in an open agreement could not be tabbed to
4296379 Fixed an issue where an uploaded signature for a recipient could change the signature type requirement of the sending user
4296631 Improved the Signing reasons feature to display the reasons in the order defined by the admin control
4297720 Fixed an issue with the Dynamics package that would display error messages when attempting to send a reminder
4297868 Fixed an issue where a pop-up in Japanese could be presented for users that have English as their UI preference
4297990 Improved the functionality of the delegation process with regards to Phone authentication to ensure valid phone numbers are used
4298099 Fixed an error that would prompt an Agreement ID error on the Manage page
4298899 Corrected an issue where emails to the sender of an agreement would report the wrong name in the From: field
4298928 Fixed an issue where Groups: Sorting by 'Administrator' did not work properly
4299116 Fixed an issue where new users could be blocked from attaching documents in the web application
4299124 Improved the French localization for the Approve button
4299286 Corrected the response for the GET /agreements/{agreementId}/events API call when the document is shared
4299765 Fixed an issue where delegating Phone based authentication recipients would default to the US country code instead of the configured value
4300871 Corrected an issue where sending an agreement to authoring and then navigating back to Send could cause  "(Alias) first.last@adobe.com" to be listed as the signer
4301923 Corrected an issue where advanced account sharing could throw an error, despite approving the share
4302356 Fixed an issue that could cause multi-signers in web forms to not function properly
4303017 Fixed an issue that could cause a user to redirect to the login page after logging in.
4303087 Improved search when using apostrophes
4303532 Fixed an issue where PUT /libraryDocuments/{libraryDocumentId}/formFields would place the fields in the wrong location

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
More details on this feature can be found here >
Lock name values


Experience changes for users

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

Alerts on the post-send page

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

Alerts config page


Resolved Issues

Issue ID

Description

4265931 Corrected a linking error in the Get Started button on the product assignment notification email for localized templates
4291936 Improved the post-send page alert information to better illustrate when alerts would trigger
4292219 Fixed an issue with fields not rendering at the correct size in authoring when the field dimensions are specified via text tag
4292274 Corrected an issue where agreements created via workflows with required files could still allow the file to be removed
4292853 Corrected an issue where recipients authenticating with Adobe Sign authentication on accounts with SAML mode set to Allowed could be served a blank screen
4293157 Fixed debranding of the logo when a signing URL expires
4293445 Fixed an issue that would throw a 502 error when getting the form field data of an agreement with an attachment added
4293531 Fixed an issue where a user accessing agreements via advanced sharing could not add themselves as a CC'd party
4294897 Fixed an issue where some characters were not supported on the Audit Report page and replaced with hash marks
4295354 Corrected some broken links in the quick start guide
4295465 Corrected an issue that prevented Phone authentication from changing the phone number if the agreement was sent via custom workflow
4295565 Corrected a problem that would block sending an agreement that is created via API and send from the authoring state
4296049 Corrected an issue that could block sharing of a Group to a User or another Group under Advance sharing rules
4296293 Fixed an issue with auto-delegation of agreement authority when clicking the signing link
4296351 Fixed an issue where Group admin authority could not be granted to a user in a Created state
4296423 Corrected an issue where the Back button was not displaying for some templates
4296449 Corrected an issue where users were not being activated from a Created state
4297057 Updating the W-4 in the Adobe Sign library
4297612 Fixed an issue that could cause a checkbox to now show as checked is some circumstances


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.

Multi-action - Hide


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:

12.0 Download the  Signer Identity Report

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

12.0 Signer Identity Report


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.

12.0 Digital signature delegation

Note:

Delegation of digital signatures only works with the Cloud Signatures option.

To allow delegation with Cloud Signatures the Download and Sign with Acrobat option must be disabled.

The option can be disabled by navigating to Account > Account Settings > Digital Signatures and uncheck Download and Sign with Acrobat


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.

12.0 Send form Woirkflow controls


The Replace Recipient feature now applies to the Form Filler role

12.0 Replace Form Filler

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).

12.0 Decline reasons


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:

12.0 Mobile Screen Capture error


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:

12.0 In-app help

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

12.0 In-app controls


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

12.0 Email template change


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:

12.0 Cancelation message


The Payments page has updated the user interface

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

12.0 Payments


Resolved Issues

Issue ID

Description

4264717 Fixed an issue where CC'd parties on an isolated shard would not properly be notified of agreement events
4274328 Improved the API swagger documentation with regard to web form authentication
4279853 Fixed an issue where imported fields on web form templates could lose their values if authored after uploading
4280045 Corrected an issue where the final notification email would not send to the first recipient if the agreement is delegated, and the signature type is Written
4283038 Improved the email template layout when rendered in Outlook
4283554 Improved custom email template distribution of the final email to align cosmetically with the standard email template
4283575 Improved handling of agreement notifications for users that are migrated while agreements are in progress for their userID
4283580 Improved handling of SMS authenticated agreements when the phone number entered appears to be something other than a phone
4285215 Corrected a race condition that could cause the deletion date for an agreement to not populate in reporting
4286380 Corrected an issue that could omit the account logo when sending an agreement via API with password authentication
4286935 Fixed an issue with Adobe Sign Authentication in Workflows that could cause multiple authentication requests
4286945 Corrected an issue where a migrated userID would not updated their podID after migration
4287011 Improved file upload handling to prevent locked uploads
4287509 Corrected an issue where special characters in the agreement name were replaced by ASCII code  when downloaded with the document export utility
4287513 Fixed an issue where the check mark for a check box would not be hidden with the checkbox under conditional rules
4287563 / 4291524 Fixed an issue where all phone codes were not being presented when delegating an agreement with SMS authentication
4287839 Corrected an issue with reminder emails where a view link would be sent instead of a signing link
4288915 Corrected an issue with local time stamps not offsetting one hour due to daylight savings adjustment
4288983 Improved handling of the NoChrome value in a session
4289039 Improved the digital signature text formatting to ensure more consistent signature output
4289171 Fixed an issue where running DELETE /agreements/{agreementId}/documents would return code 204 for already deleted documents
4289520 Added Form Filler to the Replace Recipient feature
4289531 Corrected an issue that could cause the banner HTML to flood the Manage page when viewing a shared account
4289591 Corrected an issue where a review link (not a signing link) could be sent when an agreement is delegated
4290535 Fixed an issue where users that are migrated to a federated solution would not adopt the Company name value associated with the federated values
4290729 Fixed an issue where an embedded iFrame esign page would not properly debrand when the cookie expires
4290731 Improved cancelation email messaging
4290997 Password Update email template updated to remove the legacy email address
4291436 Fixed an issue where Group level email header settings would not override the account level settings
4291499 Fixed an issue where IE11 would cause the Remind window to automatically close when opened from the Manage page
4291965 Fixed an issue where hyperlinks in the redirect message for web forms would appear as clear code
4292165 Fixed an issue that could cause an application using a form with auto-detected fields to present a blank page if the recipient only contained one name in their user profile
4292211 Improved the size of the input field for decline reasons


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
This release is adding one action (the first): Hide/Unhide
Multi-action - Hide


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.

Post signing page

Note:

This change only applies to the experience of recipients that have not registered their email address. 

The experience for registered users has not changed.


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
Redirect URL


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
Redirect URL warning message


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

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 Hyperlink values in the report CSV


New REST v6 API methods

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


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

Issue ID

Description

4276902 Corrected an issue where an agreement created from a previously completed agreement, could render one of the signatures on the previous agreement invisible 
4279984 Fixed an issue where the Notes text could be hidden on the legacy Manage page
4281681 Corrected an issue where an error would be triggered if a user on a shared account attempted to adjust the authentication method
4283869 Corrected a state where the expiration time was not being picked up when an agreement was sent via REST v6
4284302 Corrected an issue that could trigger an error message when attempting to add a user to share an account with
4284681 Corrected an issue where the external ID would not be captured when the REST v6 GET/agreement/ID method was called
4284682 Corrected an issue that could hide the "send on behalf of" text on the Activity report of an agreement
4287030 Corrected an issue that could cause the Export Data option to not be available for some agreements
4287675 Fixed an issue that caused some users to send email templates in English instead of Japanese
4288021 Fixed an issue that could cause users to not be able to authenticate
4288027 Corrected an issue that could cause the expiration date to appear to be a day earlier
4288041 Fixed an issue that could cause an attached file to throw an error despite being within the configured size (MB) limit
4288148 Improved load time when exporting User lists
4288873 Corrected an issue where web form mapping n SharePoint could fail to execute
4289213 Fixed an issue where some accounts with SAML configured as mandatory could trigger an error when accessing Pending users
4289382 Fixed an issue in the legacy Manage page when using IE browser and clicking the Audit Report link would remain unresponsive

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.

Back button in Authoring

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)
Editable Compose page

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
Note:

Agreements in a Draft state can also be edited using this mechanism.

Enterprise customers that have enabled the Modify agreement in-flight feature will see both the Modify and Edit option on the Manage page.

  • The Modify option is to be removed in a future release, leaving only the Edit option for Draft agreements, and Modify for agreements in process

foo

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
Hyperlink field properties


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: £
More details on Calculated Fields here >


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
Acceptor Decline

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


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.
Multiselect - Hide


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
Caution:

Having a positive value in the default lifetime setting will cause the signing URL to change on multiple API calls. Given all accounts will have a positive value (either 14 days or 10 years), all accounts will experience this change upon launch.

To avoid this effect, the backend default value must be set to -1.  Contact your Success manager or Support to set this value.

Prior to the September 2020 release:

API Version Expiry Signing URL
REST v5
Lifetime expiry Identical URLs returned on multiple calls
REST v6 Lifetime expiry Identical URLs returned on multiple calls

 

After the September 2020 release:

API Version Optional parameter expiry Default expiry value Signing URL
REST v5
NA > 30 sec and < 315360000 sec Unique URLs returned on multiple calls
REST v5 NA -1; Lifetime expiry Identical URLs returned on multiple calls
REST v6 /signingUrls?expiry=3600 superseded by expiry parameter Unique URLs returned on multiple calls
REST v6 /signingUrls > 30 sec and < 315360000 sec Unique URLs returned on multiple calls
REST v6 signingUrls -1; Lifetime expiry Identical URLs returned on multiple calls


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:


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):

Audit Report


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: £
More details on Calculated Fields here >


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:

Expiration controls

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
Note:

To enable Mega Sign expiration two settings must be enabled under Account Settings > Send Settings

  • Limit number of days signers will have to sign documents - This defines the number of days the agreements will be signable after being sent.  This is the value imported to Mega Sign
  • Include internal signers when applying document expiration dates - Currently this setting must be enabled for the expiration value to be imported form the account/gorup settings.


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:

Wordflow Designer error when editing

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:

Wordflow Designer error when sending

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

Issue ID

Description

4243330 4273246 Updated the audit report to better report the final "Completed" event of the transaction.
4259343 Improved Zooming on the mobile app to prevent cropping the signature field
4263785 Improved how the currency symbol is dictated in calculated fields
4263858 Improved scrolling on the signing screen for Android devices
4270477 Corrected an issue with webhooks where the completed event could fire before the documents were completed in their processing
4271693 Corrected an issue that could prevent adman's from adding users in bulk via CSV
4271820 Improved signing URL expiration for REST v5 and v6
4272911 Fixed a problem with apostrophes not rendering correctly in Workflows
4275099 Fixed a localization problem that blocked some Mobile users from signing with the Mobile option
4275744 Fixed an issue that could prevent placing multiple digital signature fields for a user
4276100 Improved User activation such that Pending users are left in their current group
4276130 Improved Get agreements/ID to return recipients in the order entered when a parallel workflow is in place
4276569 Added an Example overlay to the Transaction verification page sample
4276789 Corrected an issue with Fill and Sign that produced an error if the first and last name were not included n the user profile
4277801 Fixed an issue where group membership headings could line wrap and obscure the first group
4277802 Fixed an issue where a users group membership could be truncated if the group name is too long
4277894 Fixed an issue that could cause multiple verification emails to be sent to a new user
4278261 Fixed an issue where admins could not edit a shared library template
4278967 Fixed an issue where a large number of double-byte characters entered into a signing reason  could obscure the date
4279119 Clarified the company logo "alt" text to be better represented with screen readers
4279288 Fixed an issue that could block replacing the second signer of a workflow from the new Manage page
4279614 Corrected a problem that would prevent filtering reports by user in accounts with very large user counts
4279645 Corrected an issue that could cause report data to hang when exporting
4279646 Corrected a problem that could block verification emails from being sent when creating new users via csv file
4279740 Improved Mega Sign to respect default expiration values
4280779 Fixed an issue where recipients would be requested to log in when attempting to review a signed document link
4280782 Fixed an issue with calculated fields adding date values together incorrectly for some values
4281186 Fixed an issue where a user's Sending rights could be removed if the user changed groups via CSV edit of the user profile
4281434 Improved DELETE call for Privacy Administrators
4281572  Improved error messaging where a last name is required to complete the signature
4281657 Fixed a Permission_Denied error that prevented replacing a participant via API in a parallel workflow
4281698 Fixed an issue that could prevent signer data from populating the form data for the agreement if the signer was replaced
4281728 Fixed an issue where field visibility based on two calculated values showed inconsistent results
4281757 Corrected in issue in REST v5 where existing users could not have their email values changed to unlisted domains
4281951 Improved visibility of signatures for small screens
4281964 Fixed an issue where Workflows were not sorting properly when sorted by last modified date
4282116 Fixed a pagination issue for library templates when trying to attach to a Workflow
4282439 Improved button location and shape for Mobile apps
4282441 Fixed an error generated under Advanced Sharing when a user attempts to send an agreement on behalf of a sharing user, and that field has prefill fields
4282820 Fixed an error [Processed 1 rows of 2] when updating users info by CSV file for a user that is not in the Default Groups
4282840 Corrected a problem where the recipients Date field automatically displayed the time using the GMT offset
4282899 Fixed a problem that would remove the Group admin permissions for the Default group after login
4282935 Fixed an issue where shared user accounts under Advanced sharing could not be seen if the user did not have a First and Last name on tier profile
4282940 Corrected a state where the  Create button could be hidden if the Zoom aspect is too high
4283022 Improved SQL query structure to improve search response
4283539 Fixed an issue where a delegatee would not receive reminder emails
4283698 Fixed an issue where inactive users would not show up in a shared users list of options
4283816 Fixed an issue where the Adobe Sign portal would not auto-redirect SSO users after moving to adobesign.com
4284263 Corrected an issue where creating a new Web Form would adopt the settings for the primary group of the author instead of the assigned group
4284292 Fixed an issue where reminder emails could be sent after the reminder was canceled
4285288 Fixed an issue that could cause the Accept Cookies pop-up to display repeatedly
4286618 Fixed an issue that could cause Workflows configured with SMS verification to fail to send
4286899 Improved messaging when searching for a user that does not exist in the system