Technical notifications

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

Feature Release: Adobe Sign December 2021

First reported: September 2021 Current

Adobe Sign will be delivering a feature release scheduled for December 2021. No downtime is anticipated during this release

The December release includes feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  


The new Home and Manage page become the standard in December; Classic pages removed from service

First reported: September 2021 Current

Adobe Sign is retiring the classic experiences for Home and Manage pages in the December release. At that time, all accounts will be transitioned to the modern Home and Manage experience, with no option to revert to the classic interface.
Please note that we are committed to making this transition as smooth as possible, and have released features to match behaviors of the classic manage page, including:

  • Targeted search by first and last name.
  • Senders can now add a message when replacing the signer.
  • Added functionality to remind CCs and signers who have completed.

In the December release, we are further enhancing search capabilities and adding a ‘quick glance at metadata’ feature.  


Feature Release: Adobe Sign October 2021

First reported: September 2021 Current

Adobe Sign has completed the October 2021 release with no downtime experienced in the application.

The October release includes feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  

Planned end of support for the Microsoft Internet Explorer 11 and legacy Edge browsers by December 31st, 2021

First Reported: April 2021

 Current

By December 31, 2021, Adobe Sign will no longer formally support the Microsoft Internet Explorer 11 or Microsoft Edge Legacy browsers. We recommend that customers no longer access the Adobe Sign application with these browsers.  After December 31, 2021, customers using these browsers may have a degraded experience, and some features may cease to work.

The recipient's eSign page should continue to function properly on these browsers to avoid disrupting the recipient's workflows. We are committed to helping make this transition as smooth as possible.

Adobe Sign for Salesforce: End of service notice for versions 19.x and 20.x

First reported: June 2021 Current

Service access to the Adobe Sign for Salesforce integration v19.x and v20.x expires in October 2021. Post expiration, these versions will not be accessible to the Adobe Sign service. Ensure that you upgrade to the latest supported version of Adobe Sign for Salesforce to continue using Adobe Sign through Salesforce.

If you are on version 20.x or older, please upgrade to the new package to ensure the continuation of support.

Note:

Upgrading from a version prior to 21.5.11 requires installing the 21.5.11 package before installing the current package. Attempting to install the current package before 21.5.11 is in place results in a failed update.

Note the following while upgrading your Adobe Sign for Salesforce integration package:

  • Do not uninstall your existing Adobe Sign for Salesforce package. 
    • Uninstalling the package results in the loss of all your Adobe Sign data in Salesforce.
  • If you have users in your Salesforce org who belong to multiple Adobe Sign accounts, reach out to your Adobe client success manager or Adobe support before upgrading.
  • Upgrade and test in your Sandbox environment before upgrading your production account.
    • Ensure that your email address in the Sandbox environment is one that you have access to in case you need to change the email for your Adobe Sign account.
  • Ensure that the Lock sessions to the IP address from which they originated setting is disabled. Configure here: Setup > Settings > Security > Session Settings.
  • Review the Adobe Sign for Salesforce - Upgrade Guide to determine if there are options you need to manually configure.
    • A number of new features/settings are added in every release.  Often these new features require a manual update to the service configuration to expose their use.

Gated access to the eSign page in the September release

First reported: August 2021 Current

To comply with Adobe Legal requirements, Adobe Sign is updating the terms of use (TOU) acceptance behavior on the eSign page. Under the new experience, all "unknown" recipients must accept the Adobe Sign TOU (by clicking the Continue button) before interacting with the agreement. This acceptance is distinct from any custom TOU that the customer account may have configured, which will continue to resolve per the account TOU/CD acceptance configuration.

  • An "unknown" recipient is any email address that is not a registered, active user email in a trusted account.
  • "Known" users have accepted the Adobe Sign TOU as part of the registration process when they verified their user account, so they are not prompted to accept again.

Below is an example of the Implicit consent flow for an agreement with a custom ToU configured by the customer:

  1. Accept the Adobe Sign ToU by selecting the Continue button (after opening the agreement).
  2. Fill in the agreement fields as required.
  3. Accept the Customer Disclosure and custom ToU by selecting the Click to Sign button.
Gated access to sign


Locking name values extended to typed signatures

First reported: August 2021 Current

The March release introduced a setting to enable/disable a recipient's ability to edit their name value when signing, provided the name was supplied or known (via API or user profile). Typed signatures were excluded from this feature resulting in the ability for some signers to change their name value during the signature process. The September release updates this feature to honor the name locking setting for all signature types – including typed signatures.

  • Customers who have enabled Typing their name and initials and disabled Signers can change their name or initials will see a behavior change – the name value is no longer be editable during the signature process for typed signatures.
  • Customers that want to allow editing the name-value during the signature process should enable the Signers can change their name or initials setting (in the Signature Preferences menu).
Allow recipients to edit their name


Adobe Sign for Dynamics end of service notice for all versions older than 9.4.x

First reported: July 2021 Current

Adobe Sign will be discontinuing service for all versions of the Adobe Sign for Dynamics package versions that are older than version 9.4.x in November of 2021.

All accounts are encouraged to update their installed packages to the most current version as soon as possible.

Note:

This is an exception to the normal integration lifecycle due to the nature of the security patches applied in v9.5


Release: Adobe Sign September 2021

First reported: July 2021 Current

Adobe Sign completed a feature release on September 16th, 2021. No downtime was experienced during this release

The September release includes feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  

Domain name change to AdobeSign.com

First Reported: August 2019 - Updated:
September 2020

 Current

Adobe is changing the domain name for the Adobe Sign service to adobesign.com

The transition began with the March 2020 release for free and individual user accounts with no impact to customers that have purchased other plans.

Please refer to the table below for an up to date schedule for the rollout of the feature to your account tier.

When enabled, account administrators will have a new control available in the Account Menu: Account Settings tab to move to the new domain.

  • The control enables the ability to switch to new domain name
  • Customers that use explicitly allowed domains, 3rd party integrations, or custom applications will be able to test the impact of the new domain name on their environment
  • Please refer to the FAQ to determine if this change will have an impact on your environment
  • If there are conflicts or errors, reverting to echosign.com is supported without any impact to agreements or workflows

For Accounts that have migrated to adobesign.com

  • The new domain is being rolled out as a redirect from the main login page
  • Redirects are not necessary to access existing agreements
  • Existing agreements remain available to all parties from the existing domain name

June 2020

The migration of all free and individual accounts to the adobesign.com domain will be completed

July

All NEW small business, and individual accounts will be provisioned with the adobesign.com domain. 

September


All NEW Team accounts will be provisioned with the AdobeSign Domain

All existing Team  accounts will have an option to opt-in to the new domain. Administrators can access the control through the Account Menu UI (via the Account Setup tab). 

October


All NEW Enterprise accounts will be provisioned with the AdobeSign Domain

Gradually roll out the option to opt-in to the new domain to existing enterprise Accounts. Administrators can access the control through the Account Menu UI (via the Account Setup tab). 

H1 of 2021

The expectation is that customers will be migrated to adobesign.com in H1 2021

H2 of 2021

The option to switch to the echosign.com domain will be removed.

Adobe Sign authentication redirects to Adobe Identity Management

First Reported: August 2020

Current

Starting with the September Adobe Sign release, some users that authenticate directly to the Adobe Sign application will find their authentication method rerouted to the Adobe Identity Manager.

Adobe is standardizing authentication to this format throughout the end of 2020.

More details can be found here >

Known Issue: Admins that manage users in the Adobe Admin Console cannot change the Company value for users via the Users tab

First Reported: July 2020

Current

Admins that are managing their users via the Adobe Admin Console may find that they cannot update their user's Company value when editing the user's profile

  • Admins can still update the users using the CSV (Edit users in bulk) method
  • The user can edit their own profile successfully
  • New users added will adopt the default Company value from the Admin Console


Additional Resources


Past Notifications

API and Send page updates for the Notarize Integration feature (expected in October)

First reported: September 2021 Removed From Current List:
November 2021

The October release will introduce a new Adobe Sign feature to support integration with Notarize, Inc.'s Remote Online Notarization (RON) platform. The Adobe Sign integration with Notarize, Inc. is available for use in the U.S. only.

Below is the summary of changes:  

Notarize Integration - Adobe Sign integration with Notarize, Inc.'s Remote Online Notarization (RON) platform allows customers to add remote online notarization service as part of their Adobe Sign transactions. Available for enablement for customers in enterprise and business tiers sold directly by Adobe via the ETLA program. Notarize Transactions can be purchased as an add-on at an additional cost for these customers only. 

There are two elements that should be reviewed by customers building their own apps or using integrations: 

The Send page has a new element to identify a signer as requiring a notarized signature, and additional configuration steps to guide the signature process.  

The REST API has been updated to accommodate the requirements to leverage this functionality, and customers leveraging the REST API should review the below to determine if there is any impact for their existing use. 

  • Send Page updates

Customers with Notarize Transactions enabled can select the Requires notarization option on the recipient record, just to the right of the authentication method:

Notarize Interface on the Send page

After the agreement is configured and the sender clicks Next, the sender is presented with additional configuration options for the notarization process:

Configure Notarize options

  • API updates - There are significant updates to the APIs to support the Notarize Integration:

POST /agreements

The POST /agreements API has been updated to support sending an agreement for notarization.

  • A new role, NOTARY_SIGNER, should be used to indicate a notary session participant.
  • A new NotaryInfo attribute has been added to the AgreementInfo definition to contain all of the options associated with creating a new agreement that requires notarization.

Parameter Name

REST Object

Description

memberInfos

ParticipantInfo[]

Array of ParticipantInfo objects, containing participant-specific data (email, e.g.). All participants in the array belong to the same set.

role

Value

Description

SIGNER

Signs the Agreement

APPROVER

Approves the Agreement

DELEGATE_TO_SIGNER

One who herself can not sign but delegates the agreement to another signer

DELEGATE_TO_APPROVER

One who herself can not approve but delegates the agreement to another approver

SHARE

Participant with whom this agreement has been shared

DELEGATE

Participant to whom the Agreement was delegated. This role can not be used at the time of creating or updating agreement through POST/PUT call on agreement resource. Delegation happens separately by participants.

NOTARY_SIGNER

Notary Session Participant

Role assumed by all participants in the set (signer, approver, etc.)

 

FileInfo extension

The FileInfo definition will need to be expanded to indicate which documents should be notarized.

FileInfo

Parameter Name

Type

Default

Required

Description

document

Document

optional

A document that is associated with the agreement.
This field cannot be provided in POST call.
In case of GET call, this is the only field returned in the response

label  

String

optional

The unique label value of a file info element. In case of custom workflow this will map a file to corresponding file element in workflow definition.

libraryDocumentId

String

optional

ID for an existing Library document that will be added to the agreement

transientDocumentId

String

optional

ID for a transient document that will be added to the agreement

notarize

true

false

optional

Indicates that this document needs to be notarized.

 

ParticipantInfo extension

The ParticipantInfo definition has been expanded to allow the notary authentication method to be specified.

ParticipantInfo

Parameter Name

Type

Default

Required

Description

email

String

N/A

required

Email of the participant.

notaryAuthentication

Enum

MULTI_FACTOR_AUTHENTICATION

optional

MULTI_FACTOR_AUTHENTICATION - Notary authentication is performed using a two-factor authentication method
NONE - No authentication is required.

 

NotaryInfo

A new optionanotaryInfo field has been added to the AgreementInfo definition to contain the NotaryInfo object that specifies additional options associated with notarization.

NotaryInfo

Parameter Name

Type

Default

Required

Description

notaryType

Enum

If only Notarize Notary on Demand Service is enable on the account,
then the notaryType will default to NOTARIZE_NOTARY, otherwise it will default to BYON_NOTARY

required

NOTARIZE_NOTARY - Notarize Service provides the notary
BYON_NOTARY - Account provides the notary

payment

Enum

BY_SENDER

optional

Only applies if type == NOTARIZE_NOTARY
BY_SENDER - Sender pays for the notarization
BY_SIGNER - Signer pays for the notarization

appointmentStart

String

""

optional  

ISO_DATE_TIME formatted string See ISO_ZONED_DATE_TIME

note

String

none

optional  

Notes for notary session.

notaryEmail

String

""

optional  

email of the bring your own notary

 

Example /agreement

{
    "fileInfos": [
        {
            "transientDocumentId": "",
            "notarize": true
        }
    ],
    "name": "notary_agreement_name",
    "participantSetsInfo": [
        {
            "memberInfos": [
                {
                    "email": "someone@somewhere.com",
                    "securityOption": {
                        "notaryAuthentication": "MULTI_FACTOR_AUTHENTICATION"
                    }
                }
            ],
            "order": 1,
            "role": "NOTARY_SIGNER",
            "name": "participant_set_name"
        }
    ],
    "signatureType": "ESIGN",
    "state": "IN_PROCESS",
    "notaryInfo": {
        "appointment": "2021-10-29'T'13:00",
        "notaryEmail": "notaries@email.com",
        "notaryType": "PROVIDER_NOTARY",
        "note": "This is a note for the notary.",
        "payment": "BY_SIGNER"
    }
}

 

PUT|GET /agreements/{aid}

PUT /agreements/{aid} API will support updating an agreement with notarization options. GET /agreements/{aid} API will return any options set for agreement notarization. See POST /agreements section to view updated attributes.

 

Error Codes

Existing error codes for POST /agreements remain unchanged. We have defined a new error code as given below:

REST Error Code

HTTP Status Code

Message

Scenario

PERMISSION_DENIED

403

User setting or OAuth scope token do not permit sending agreement for notarization.

This error will be thrown when role is set to NOTARY_SIGNER and the API caller (i.e prospective sender) does not have notary feature enabled and/or if notary service provider is not set.

 

Documentation impact

In the request's AgreementInfo object, "status" element will include the new agreement status "WAITING_FOR_NOTARIZATION".

 

POST /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingTokens

The API can be used by customers (notary signers) to obtain a signing token that allows them to complete the esign phase of the flow. 

  • New signing capability has been added to capture the new role - ACCEPT_BEFORE_NOTARIZATION. 
  • Signing tokens should not be obtained to complete the notarization phase.
{
  "securityInfo": {
  "authenticationMethod": "NONE"
},
  "signingCapabilities": [
    "ACCEPT_BEFORE_NOTARIZATION"
  ]
}

 

PUT /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/status

The API can be used by customers (notary signers) to complete the esign phase of the flow. To accommodate the new role, new enum status value has been introduced - ACCEPTED_BEFORE_NOTARIZATION.

Attribute

Type

Description

Status

Enum<String>

Value

SIGNED

APPROVED

ACCEPTED

DELIVERED

FORM_FILLED

ACCEPTED_BEFORE_NOTARIZATION

                                         

This status indicates that recipient with role SIGNER completed agreement.

This status indicates that recipient with role APPROVER completed agreement.

This status indicates that recipient with role ACCEPTOR completed agreement.

This status indicates that recipient with role CERTIFIED_RECIPIENT completed agreement.

This status indicates that recipient with role FORM_FILLER completed agreement.

This status indicates that recipient with role NOTARY_SIGNER completed agreement without notarizing it

The notary signer can follow the below sequence of API calls to complete the esign phase:

  1. GET /agreements/{agreementId}/members - to fetch the notary signer's participant ID & participant set ID
  2. POST /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingTokens - to request signing token for notary signer with ACCEPT_BEFORE_NOTARIZATION capability
  3. POST /transientDocuments - to upload document that was reviewed
  4. PUT /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/status - to submit reviewed document and complete esign phase.

New webhook event

Customers can subscribe to new webhook event, AGREEMENT_READY_FOR_NOTARIZATION, to be notified when agreement is ready for notarization. The event is not visible on the webhooks UI & can be subcribed to via POST /webhooks API call.

Documentation impact

The following APIs are not modified but their documentation has been updated to include new agreement status "WAITING_FOR_NOTARIZATION" or new role "NOTARY_SIGNER".

GET /agreements

In response UserAgreements/UserAgreement object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

GET /agreements/{agreementId}

In response AgreementInfo object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

GET /agreements/{agreementId}/events

API is updated to support new READY_TO_NOTARIZE and NOTARIZED events.

In response Event object

  • "participantRole" element now includes new role NOTARY_SIGNER.
  • "type" element includes new events READY_TO_NOTARIZE and NOTARIZED. "description" element will be  "Document sent for notarization" and  "Notarized document received" respectively

GET /agreements/{agreementId}/members/participantSets/{participantSetId}

In response DetailedParticipantSetInfo object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

PUT /agreements/{agreementId}

Request AgreementInfo object now includes "WAITING_FOR_NOTARIZATION" status.

PUT /agreements/{agreementId}/members/participantSets/{participantSetId}

WAITING_FOR_NOTARIZATION status is one of the "status" element values in the DetailedParticipantSetInfo object.

POST /agreements/{agreementId}/view

WAITING_FOR_NOTARIZATION status has been added as one of the allowed views.

GET /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingInfo

If the participant specified in request path has notary signer role, the API will return ACCEPT_BEFORE_NOTARIZATION signing configuration, inline with all of the other signing configurations for this agreement/participant.

Company Name option to be removed from Phone Authentication

First reported: June 2021 Removed From Current List:
October 2021

SMS security (with regards to the sendingID matching the purported company name in the message) has improved to the point where Adobe Sign sending SMS messages with another company name can cause the message to fail in delivery.

As a result, the option to customize the phone authentication message with the company name is to be removed from service in the September 2021 release.


Known Issue: New Home or Manage page is blank

First Reported:  February 2020

Removed From Current List:
October 2021

Problem: When switching to the new Home or Manage page, the page is entirely blank.

Test: attempt to load this page: https://documentcloud.adobe.com/

  • If you can not load https://documentcloud.adobe.com/ then you should contact your internal network administration and work with them to unblock the documentcloud.adobe.com domain.
  • If you can access the above link, contact support

Adobe Sign v6 REST POST /workflows/ID/agreements has been removed from service

First reported: June 2021 Removed From Current List:
October 2021

The v6 REST POST /workflows/ID/agreements API call has been removed from service in the June 2021 release, one year after removing the call from documentation and notifying the users that the endpoint was to be removed.

Customers that continue to use this API call will now receive a 404 error.

The suggested alternative for replacing this functionality is to use a POST/agreement call with a workflowID in the JSON request.

Sample request body:

{
  "fileInfos": [
    {
      "transientDocumentId": "dsakjdfksajfkhaskdfuisdfklfsdkjfgvsdksjdkasj"
    }
  ],
  "name": "Sending a workflow",
  "participantSetsInfo": [
    {
      "memberInfos": [
        {
          "email": "someemail@somedomain.com"
        }
      ],
      "order": 1,
      "role": "SIGNER"
    }
  ],
  "workflowId": "woDJFWOFJhjlkadsfjkfdskfnksdfn"
  "signatureType": "ESIGN",
  "state": "IN_PROCESS"
}

v6REST Update for GET /agreements/{agreementId}/signingUrls

First reported: June 2021 Removed From Current List:
October 2021

Prior to the June release, when calling GET /agreements/{agreementId}/signingUrls, the API would return a 404 immediately after the agreement was created.

For a short time after the 404 error cleared, the response would return a non-404 response, but would only include the sender's signingURLs. (While the signer's participation was still being defined.)

After the June 2021 launch, a 404: AGREEMENT_NOT_EXPOSED code will be returned until the full list of signing URLs is completed, at which time a 200 code is delivered.

Customers that do not want to continue to try the API call until the 200 response is returned are encouraged to use Webhooks, and respond to the AGREEMENT_CREATED event.


Scheduled downtime for the Adobe Sign for Word/PowerPoint, Outlook, and Teams integrations

First Reported: March 2021 - Updated June 2021

Removed From Current List:
October 2021

On Saturday, July 17th 2021, Adobe Sign completed maintenance on the following integrations:

  • Adobe Sign for Microsoft Teams
  • Adobe Sign for Microsoft Word/Powerpoint
  • Adobe Sign for Microsoft Outlook

The integrations are now up and running normally.

Patch Release: Adobe Sign August 2021

First reported: June 2021 - Updated August 2021 Removed From Current List: September 2021

Adobe Sign has completed the patch update as of August 11, 2021. The patch was completed with no downtime.

The August patch release includes minor experience changes and resolutions to multiple customer-reported issues.  

Planned End of Service for the SOAP API in May, 2021

First Reported: June 2018 - Updated: February 2021

Removed From Current List: September 2021

With the release of REST API Version 6 providing the best programming experience for Adobe Sign developers, the SOAP API has been deprecated and will not be supported past May 2021.  The REST API is now the preferred interface to integrators and application developers and future development should move to this API.

Here are some references to help with the transition:

 

ACTION REQUIRED

If you have developed an integration or application to the Adobe Sign service based on the SOAP API you will have to rewrite your application using at least REST API Version 6 prior to May 2021.  Direct communications to developers and integrators will occur over the next several quarters to insure a smooth transition to the latest API.

Planned "End of Service" for IE 11 browsers in Microsoft integrations

First Reported: January  2021

Removed From Current List: September 2021

Microsoft is ending support for Internet Explorer 11 on August 17, 2021.

As a result, the Adobe Sign for Microsoft integrations are also ending support for IE11 on the same timeline.

Services impacted are:

  • Dynamics 365 (Online and On-Prem)
  • Microsoft 365
  • Outlook 365
  • Power Automate/Power Apps
  • SharePoint (Online and On-Prem)
  • Teams

For more information regarding the sunset of these browser options, see the Microsoft announcement >

Planned End of Service for Adobe Sign’s integration with Dropbox

First Reported: March 2021

Removed From Current List: August 2021

Adobe Sign’s integration with Dropbox is scheduled to end on July 31st, 2021.

At that time, Adobe Sign will no longer be available through your Dropbox account, however all of your Adobe Sign agreements will remain available to you and can be accessed by logging in to your Adobe Sign account.

New Release: Adobe Sign June 2021

Adobe Sign has completed the June 2021 release with no downtime.

The June release includes feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  

New SSL Certificate Available -
In effect as of June 1st, 2021

First Reported: April 2021

Removed From Current List: August 2021

Adobe Sign is releasing new SSL Certificates on June 1st, 2021
There is no change to the public key, underlying cryptographic protocols, or scheme.

The new certificates are available by download from the Adobe Sign System Requirements page.

 

ACTION REQUIRED

Use of the public key
If you have custom-built integrations with Adobe Sign using either the SOAP or REST APIs, and if any of these integrations have ‘pinned’ the existing public key, no action is required.

If you are using Adobe Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Adobe Sign certificates in the Adobe Sign System Requirements.

The new SSL certificates will become active on June 1st, 2021

New Release: Adobe Sign May 2021

First Reported: January 2021

Removed From Current List: July 2021 

The new IRS W-4 (2021) form, entitled W-4 2021 (Employee's Withholding Certificate), is expected to be added to the Adobe Sign library as part of the February 2021 release.

 

ACTION REQUIRED

The new W-4 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2020 version is to be removed from the system in May 2021.

Any application/API using the legacy (ver 2020) form must be updated before May 1st to ensure no disruption to successful service.

 

To find the libraryDocumentId in an API-enabled account:

  1. Log in as an Account Admin
  2. Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
  3. In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 
    • Enable the library_read:self scope
  4. Click the Try it out! button
  5. In the Response Body, locate the new W-4 2021 (Employee's Withholding Certificate) form template (not ver. 2020) to see the libraryDocumentId value.  
Obtain the docID

Note:

Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

If you need more information, please contact your Customer Success Manager.

New W-4 for 2021 added to the Adobe Sign Library

First Reported: March 2021

Removed From Current List: July 2021

Adobe Sign has completed the May 2021 release with no downtime.

The May release includes feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  

Adobe Sign Cookie management update

First Reported: August 2020

Removed From Current List: July 2021

Adobe Sign is adopting a new cookie consent banner from OneTrust that is persistent until the user explicitly makes a choice.

Users that redirect to a new domain during authentication need to consent a second time for the second domain (The common case for this is redirecting from echosign.com to adobesign.com due to the domain switch). 

Users are advised to update their bookmarks to eliminate the redirect.

Fill & Sign has a path for templates and authenticated signing

First Reported: March 2020

Removed From Current List: July 2021

The Only I Sign compose page will be replaced by a new compose page (based on the latest Send page designs) that allow the use of templates and the placement of fields through authoring.

Admin settings determine the default user experience. An optional "switch" link can be enabled to allow the user to switch between the free form Fill & Sign interface and the new authoring-enabled Self-sign experience. 

New to this experience is the ability to employ authentication for the signer. 

The controls are based on the Enforce identity authentication settings. When enabled,  the user will be prompted to enter their Adobe Sign credentials when opening the agreement, and (optionally) again when they place a signature or finalize the agreement. 

The controls for the new self-signing experience, as well as enforced identity authentication, can be set at the account and/or the group level (group-level settings over-ride the account-level settings)

 

Rollout plan

The new self-signing experience will replace the legacy Only I Sign page over the next two major releases. 

Customers that are using the legacy Only I Sign capability should plan to migrate to the new experience by Fall 2020 when it becomes the default and the legacy page is removed from service. 

  • No changes to the existing settings will be made with the July release
  • In the following release, the new experience will be set as the default with the option to revert to the old page
  • In the Fall 2020 release, the ability to revert to the legacy interface will be removed.

The Adobe Sign for Word/PowerPoint, Outlook, and Teams update goes live April 19th

First Reported: December 2020 - Updated: March 2021

Removed From Current List: May 2021

The update will go into effect at 8:00AM PDT / 11:00 EST / 15:00 UTC

This update is being put in place to enhance overall security across all three integrations.

After the update is completed, administrators/users will be prompted to re-accept a permissions request for the application before access is permitted.

Details can be found here >

New Release: Adobe Sign March 2021

First Reported: February 2021

Removed From Current List: May 2021

Adobe Sign has completed the release for March 2021 with no downtime.

This product release includes new features/enhancements for administrators and end-users as well as multiple resolved issues.

Planned "End of Service" for Edge Legacy browsers in Microsoft integrations

First Reported: January  2021

Removed From Current List: May 2021

Microsoft is ending support for the Edge Legacy browser on March 9th, 2021

As a result, the Adobe Sign for Microsoft integrations are also ending support for Edge Legacy on the same timeline.

Services impacted are:

  • Dynamics 365 (Online and On-Prem)
  • Microsoft 365
  • Outlook 365
  • Power Automate/Power Apps
  • SharePoint (Online and On-Prem)
  • Teams

For more information regarding the sunset of these browser options, see the Microsoft announcement >

End of Support: The Adobe Sign for Microsoft Power Automate v1 Actions- scheduled for January 2021

First Reported: July 2020

Removed From Current List: May 2021

Adobe Sign for Power Automate 3.0 update introduces new REST v6 Actions that are intended as more robust replacements for existing actions of the same name.

Workflows using legacy actions will continue to run if no action is taken. The legacy actions have been marked with (Old) in their name.  These legacy Actions are scheduled to be deprecated by January 2021.

The list of Actions to be deprecated is:

  • Create a library template from a document URL (Old)
  • Create a library template from an uploaded document (Old)
  • Create an agreement from a document URL and send for signature (Old)
  • Create an agreement from a library template and send for signature (Old)
  • Create an agreement from an uploaded document and send for signature (Old)
  • Get a list of all agreements (Old)
  • Get a list of all library templates (Old)
  • Get form field data of agreement (Old)
  • Upload a document and get a document ID (Old)

 

The new actions show in the Actions list with the same name as the legacy Actions.

Customers that use these Actions should update their flows to use the new connector Actions. This can be done by replacing the Legacy action with the new Actions in your existing automation flow.

End of Service for Social Authentication

First Reported: November 2020

Removed From Current List: May 2021

The ability to require signers to provide their social identity before they gain access to view and sign the document will be removed in March 2021.  This feature enabled Senders to require a sign-in from Facebook, LinkedIn, Google, Yahoo!, Microsoft Live or Twitter. 


Planned "End of Service" for the personal Twitter integration

First Reported: December 2020 - Updated: January 2021

Removed From Current List: May 2021

The option to integrate with Twitter at the User level (via Personal Preferences) is to be removed from the user interface in March 2021. At that time:

  • No new user accounts can enable Twitter at the User level
  • Users that have Twitter enabled will stop seeing Twitter messages for new agreements created
  • Free user accounts that have Twitter enabled will have the monthly transaction limit reduced from ten to:
    • 5 transactions per month for Adobe Sign Web clients
    • 2 transactions per month for Acrobat clients
  • Enabled accounts will have their Twitter credentials removed from the Adobe Sign systems
  • Adobe Sign's Twitter app will be deleted to expire all Twitter tokens
12.2Twitter

New Release: Adobe Sign February 2021

First Reported: January  2021 - Updated: February 2021

Removed From Current List: March 2021

The  February release has been completed with no downtime to the service.

This product release includes new features/enhancements for administrators and end-users as well as multiple resolved issues.

Workflow Designer producing error messages

First Reported: September 2020

Removed From Current List: March 2021

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:

Workflow designer error

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

Workflow 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

End of Service for Adobe Sign for Workplace by Facebook

First Reported: November 2020

Removed From Current List: January 2021

The Adobe Sign for Workplace by Facebook integration has being fully decommissioned as of  November 29th, 2020.


End of Service of RC4 Encryption for Adobe Sign generated PDFs

First Reported: September 2020

Removed From Current List: December 2020

In January 2021 Adobe Sign will end the use of RC4 encryption in the Adobe Sign application and transition all accounts using RC4 to AES-128 Encryption.

Existing PDFs will remain unaffected by this change.

Adobe Sign deprecated the use of the 128-bit RC4 encryption method early in 2020 as support for the RC4 cipher option is no longer considered to be secure.

  • The use of this cipher is to be eliminated in January 2021
  • Adobe Sign will continue to offer the AES-128 and AES-256 cipher, which are both very strong, industry-standard options

 

ACTION REQUIRED:

None.

  • Accounts configured for RC4 PDF encryption will have that setting upgraded automatically to AES-128
  • Accounts configured for AES-128 or AES-256 encryption will remain the same


Access to Adobe Sign Support is changing: September 2020

First Reported: August 2020

Removed From Current List: December 2020

The process for contacting Adobe Sign Support is changing two elements in September 2020:
Note: If you submit cases via the Adobe Admin Console this process will remain the same.

  • Email is no longer supported for creating new cases - The decision to remove email support has been made to serve our customers more efficiently. Creating cases through an authenticated process ensures that Support can act on the request knowing it has been submitted by an authorized party for the customer organization.
  • All cases must be submitted via an Admin. End-users must contact their group, privacy, or account admin to submit new support requests.


More information on how to contact support is available here


New SSL Certificate Available -
Going into effect October 8th, 2020

First Reported: August 2020

Removed From Current List: December 2020

Adobe Sign is releasing a new SSL Certificate on October 8th, 2020.
There is no change to the public key, underlying cryptographic protocols, or scheme.

The new certificate is available by downloading it from Adobe Sign System Requirements.

 

ACTION REQUIRED

Use of the public key
If you have custom-built integrations with Adobe Sign using either the SOAP or REST APIs, and if any of these integrations have ‘pinned’ the existing public key, no action is required.

If you’re pinning the certificate itself or using other methods, you can find the new Adobe Sign certificate in the Adobe Sign System Requirements.

The new SSL certificate will become active on October 8th, 2020.


Adobe Sign for Dynamics 365: Upgrade to version 9.2

First Reported: September 2020 - Updated October 2020

Removed From Current List: December 2020

A new version of Adobe Sign for Dynamics 365 has been released.

Dynamics admins can upgrade the existing app via the admin Settings > Solutions  


Adobe Sign for Microsoft Power Automate Actions updated to REST v6

First Reported: July 2020

Removed From Current List: October 2020

The Adobe Sign for Power Automate 3.0 update introduces new REST v6 Actions that are intended as replacements for existing actions of the same name. Legacy Actions will be hidden and are deprecated by January 2021.


REST v6 API update: Additional attributes for multiple endpoints

First Reported: July 2020

Removed From Current List: October 2020

As part of the July 2020 release, several of the REST v6 API endpoints are getting additional attributes:

Resource

Attribute

REST Object

Impacted Endpoints

AgreementInfo lastEventDate Date GET /agreements/{agreementId}
DetailedGroupInfo isDefaultGroup Boolean GET /groups/{groupId}
DetailedParticipantInfo createdDate Date GET /agreements/{agreementId}/members
DetailedParticipantInfo userId String GET /agreements/{agreementId}/members
DetailedUserInfo createdDate Date GET /users/{userId}
Document createdDate Date GET /agreements/{agreementId}//documents
Event id String GET /agreements/{agreementId}/events
GroupInfo createdDate Date GET /groups
GroupInfo isDefaultGroup Boolean GET /groups
LibraryDocumentInfo lastEventDate Date GET /libraryDocuments/{libraryDocumentId}
MegaSignInfo lastEventDate Date GET /megaSigns/{megaSignId}
SenderInfo createdDate Date GET /agreements/{agreementId}/members
SenderInfo userId String GET /agreements/{agreementId}/members
UserGroupInfo createdDate Date GET /users/{userId}/groups
WidgetInfo lastEventDate Date GET /widgets/{widgetId}


New Release: Adobe Sign September 2020

First Reported: August 2020 - Updated September 2020

Removed From Current List: October 2020

The Adobe Sign September 2020 product release has completed with no downtime.

This product release includes new features and feature enhancements for administrators and end-users.


Planned “End of Service” for the Archive feature

First Reported: October 2019

Removed From Current List: October 2020

The Archive feature is scheduled to be removed from the Adobe Sign system when the new Home and Manage pages are fully deployed and in service. This includes both direct upload and email to archive.

Users that have content in their Archive will still be able to view and access that content on the new Manage page, but new content may not be added. 

 

ACTION REQUIRED

No action is required. 

The ability to upload new content to the Archive section will be disconnected when the account migrates to the new Home/Manage page structure.


Planned “End of Service” for the Access Code feature

First Reported: December 2019

Removed From Current List: October 2020

The legacy Access Code feature is scheduled to be removed from the Adobe Sign system when the new Home and Manage pages are fully deployed and in service. 

Users that have processes leveraging the Access Code should contact their Success Manager to discuss alternate methods to fulfill their business requirements.

 

ACTION REQUIRED

Customers that rely on the Access Code should contact their Success manager directly to discuss their signature flow requirements.

Limited Manage page availability on the evening of October 3rd PDT

First Reported: September 2020

Removed From Current List: October 2020

Adobe Sign is planning an update to the search service during the evening of October 3rd Pacific time.  There will be limited access to the manage page during this time and users may experience a maintenance message. 

This activity will NOT impact 

  • Logging in to the application
  • Sending new agreements or signing agreements that are in flight
  • Creating new forms or signing active forms
  • Using workflows or creating new workflows

The maintenance windows are planned regionally in order to have the smallest impact to active use as possible. Note: perceived impacts will be much shorter than these windows.

The planned maintenance windows for each region:

  • APAC : 7:30 am – 8:30 am on Oct 4th (3 pm – 4 pm PDT on Oct 3rd)
  • India: 4:30 am – 5 am on Oct 4th (4 pm – 4:30 pm PDT on Oct 3rd)
  • Europe: 2 am – 3 am on Oct 4th (5 pm – 6 pm PDT on Oct 3rd)
  • US (East): 11 pm – 12 am on Oct 3rd (8 pm – 9 pm PDT on Oct 3rd)
  • US (West): 9 pm – 9:30 pm on Oct 3rd

New Release: Adobe Sign July 2020

First Reported: April 2020 - Updated: July 2020

Removed From Current List: September 2020

The Adobe Sign July 2020 product release has been completed.

This product release includes new features and feature enhancements for administrators and end-users.

No downtime was experienced during the release. 


Adobe Sign for SharePoint Online: Upload limit increased to 10MB

First Reported:  June 2020

Removed From Current List: September 2020

The upload limit for Adobe Sign for SharepPoint Online customers has been improved from 5MB to 10MB.

All customers gain the increase. No action is required, the update is in-place.


Adobe Sign for SharePoint Online: Seamless user provisioning

First Reported:  June 2020

Removed From Current List: September 2020

Seamless user provisioning is available to all Adobe Sign for SharePoint Online customers. Version does not matter.

SharePoint Administrators have a new option that grants access to the Adobe Sign integration automatically for any user assigned the default Edit permission for your SharePoint site.

Review the Release Notes >


Adobe Sign icon and font change

First Reported: January 2020

Removed From Current List: September 2020

The August 2020 release includes a change to the Adobe Sign icon as well as the fonts used throughout the application.

Customers that use any type of robotic process automation (RPA) should be aware of this change in case it impacts how their automation functions.  

Adobe Sign does not support RPA, but it's understood that some customers may use it to automate common processes. 

If RPA is part of a customer's automation strategy they should be prepared to test and repair their existing RPA suites during this release time frame.

Contact your success manager if you have any questions.


Security Notice: Adobe Sign is ending support for older API authentication models in June 2020

First Reported: August 2018 - Updated: September 2019

Removed From Current List: June 2020

Adobe is committed to providing safe and secure product experience for our customers by adhering to the latest industry standard security protocols. As a part of that process, Adobe Sign is ending support by June 2020 for older API authentication models that allowed sending username and password in the API call.

 

IMPACT

Clients currently using the older authentication model will need to move to the newer OAuth-based authentication. 

 

ACTION REQUIRED

  • Customers using an integration should upgrade to the latest version. Refer to reference guides for all the latest Adobe-built partner integrations.
  • Customers who have built their own custom integration with Adobe Sign will need to update to the latest OAuth-based authentication. For more details, please refer to this Migration Guide
  • Mobile users will need to upgrade to the latest version of the Adobe Sign app for iOS & Android.

 


New Release: Adobe Sign March 2020

First Reported: January 2020 - Updated:  February 2020

Removed From Current List: May 2020

The Adobe Sign March 2020 product released March 18th.

This product release includes new features and feature enhancements for administrators and end-users.

No downtime was experienced during the release. 

Note:

All accounts will have their default Home and Manage pages set to the new experiences.

Accounts on free, individual, and small business service plans will have the UI controls removed.

  • These service levels are fully migrated to the new experience and may not revert to the classic pages.

Accounts on business or enterprise service plans will have the new experience set as the default. However:

  • The optional "Switch" link will still be available
    • The "Switch" link controls are scheduled to be removed from the interface in May 2020
  • The default experience controls will still be available, allowing the default experience to be set back to the classic pages
    • The default experience controls are expected to be removed from the interface in the second half of 2020

 

New UI Controls

 


Footer link to the Adobe Privacy site is to be removed from the Web interface

First Reported:  February 2020

Removed From Current List: May 2020

In the March 2020 release, the link to the Adobe privacy site in the web page footer was removed.


New Release: Adobe Sign for SharePoint Online v2

First Reported:  February 2020

Removed From Current List: May 2020

The latest version of Adobe Sign for SharePoint supports web form functionalities to help businesses collect data and e-signatures at scale.

SharePoint admins can upgrade the existing app from previous versions to version 2.0 via AppSource.

Review the Release Notes >


End of life for Adobe Sign for SharePoint Online Workflow - March 1st, 2020

First Reported:  February 2020

Removed From Current List: May 2020

The Adobe Sign for SharePoint Online Workflow package is being fully decommissioned and will stop functioning on March 1st, 2020.

Customers that leverage Workflows should migrate their processes to the Power Automate solution.


Throttling limits go into effect for Agreement processing

First Reported: February 2020

Removed From Current List: May 2020

Throttling for agreement generating processes has been enabled for all accounts.

Please refer to the FAQ for specifics on the throttling process.


Chrome browser alert

First Reported: February 2020

Removed From Current List: May 2020

The Chrome browser is updating to v80, and that update brings improved security around cookies.

These security updates demanded changes to our code that may impact older (unsupported) versions of the Chrome browser (v66 and older).

Customers that notice new UI errors/bugs should first check their browsers to ensure they are running a modern (supported) version of the browser, and update if they are not.

 

For more information please refer to the following articles:


New I-9 for 2020 added to the Adobe Sign Library

First Reported: February 2020

Removed From Current List: May 2020

The new IRS I-9 (2020) form, entitled I-9 2020 (Employment Eligibility Verification), has been added to the Adobe Sign library.

 

ACTION REQUIRED

The new I-9 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2019 version is to be removed from the system in May 2020.

Any application/API using the legacy (ver 2019) form must be updated before May 1st to ensure no disruption to successful service.

 

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new I-9 2020 (Employment Eligibility Verification) form template (not ver. 2019) to see the libraryDocumentId value. 

Obtain the docID


New W-4 for 2020 added to the Adobe Sign Library

First Reported: January 2020

Removed From Current List: March 2020

The new IRS W-4 (2020) form, entitled W-4 2020 (Employee's Withholding Certificate), had been added to the Adobe Sign library.

 

ACTION REQUIRED

The new W-4 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2019 version is to be removed from the system in May 2020.

Any application/API using the legacy (ver 2019) form must be updated before May 1st to ensure no disruption to successful service.

 

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new W-4 2020 (Employee's Withholding Certificate) form template (not ver. 2019) to see the libraryDocumentId value. 

 

Note: Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

If you need more information, please contact your Customer Success Manager.


Adobe Sign for Salesforce v21.5.11

First Reported: August 2019 - Updated: November 2019

Removed From Current List: March 2020

Adobe Sign for Salesforce customers must upgrade to the latest version as soon as possible.

Adobe Sign for Salesforce v21.5.11 is required as a pre-requisite for all new Adobe Sign for Salesforce versions going forward.

 

Action required

Please upgrade before the end of November 2019. To upgrade:

If you are running version 18 or earlier, you must upgrade immediately. Adobe support has ended for these versions.

  • We will begin turning off versions 14 and below starting December 9, 2019. 
  • Versions 17 and below will be turned off on Feburary 3, 2020.

 

Important

Please review the release notes and test in a Sandbox org before upgrading your Production instance. This is an important step if you have developed a custom solution. Object definitions may have changed and you may be required to update your customization.

Please keep the API version of Lightning Locker at 46 when Salesforce Winter ’20 is released. Please see the release notes from Salesforce on Lightning Locker version.

Refer to the release notes for additional information on the newest features in Adobe Sign for Salesforce.

 

Stay updated

Adobe recommends, as best practice, that customers always upgrade to the latest version of Adobe Sign for Salesforce, as this version provides the latest security patches and “older” versions have an “End of Support” date. You may also be missing out on the latest solution to automate and accelerate your business.

We’ve added support for Salesforce process builder, Community Cloud, email integration, Salesforce CPQ support, and full Lightning support including drag and drop ease on any device. See complete list of all the latest features and solutions here.

 

Planned “End of Life” for old versions of Adobe Acrobat Reader for digital signatures in January 2020

First Reported: October 2019

Removed From Current List: February 2020

Adobe Sign customers applying digital signatures with the Download and Sign With Acrobat option using Adobe Acrobat Reader on a desktop computer must upgrade to a recent version of the software.

Download with Acrobat

ACTION REQUIRED

Please upgrade old versions of Acrobat Reader to one of the following:

Please upgrade before the end of December 2019.

 

Impact

Customers currently using the Download and Sign With Acrobat option with older versions of Acrobat Reader will need to upgrade to successfully apply a digital signature after December 2019. After that date, when using older versions, the following message will be shown but users will not be able to apply their digital signature:

Acrobat error

More details

This change derives from the removal of the “Reader Extension” enablement from PDF files generated by Adobe Sign starting from January 2020. Reader Extension was required by old releases of Adobe Acrobat Reader prior to version 11.0.7 to enable digital signatures. This feature is not technically feasible from some new cloud platforms hosting Adobe Sign.

In addition, the new requirement has been introduced to minimize security threats associated with using insecure and unsupported versions of Adobe Acrobat Reader to apply digital signatures.

Email templates and the post-signing confirmation page are changing with the November release

First Reported: October 2019

Removed From Current List: January 2020

The November release includes new email templates for the Please Sign and Signed and Filed base templates.

All customers that are using the base templates (not a Custom Email Template) will inherit the new templates by default.

Please Sign -> Review and Sign

Signed and Filed -> Done Signing 

EmailTemplatesoct2019

The new post-signing page

post sign page

ACTION REQUIRED

No action is required and you will inherit the new templates seamlessly.

Adobe logo

Sign in to your account