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.

New Release: Adobe Sign July 2020

First Reported: April 2020 - Updated: July 2020  Current

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. 


[New] 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


[New] End of Support: The Adobe Sign for Microsoft Power Automate v1 Actions- scheduled for Janurary 2021

First Reported: July 2020 Current

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.


[New] Adobe Sign for Microsoft Power Automate Actions updated to REST v6

First Reported: July 2020 Current

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.


[New] REST v6 API update: Additional attributes for multiple endpoints

First Reported: July 2020 Current

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}


Known Issue: New Home or Manage page is blank

First Reported:  February 2020
Current

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


Domain name change to AdobeSign.com

First Reported: August 2019 - Updated: June 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 expected to customers that have purchased other plans.   

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.  

In the July 2020 release, small business, business and enterprise 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 between the old and the new domain name. 
  • Customers that use explicitly allowed domains, that use 3rd party integrations or custom applications will be able to test the impact of the new domain name on their environment.  If there are conflicts or errors they can switch back to the old domain without an impact to agreements or workflows.  

Please refer to the FAQ to determine the impact of this change on your environment.

June 2020

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

End of July 2020

All NEW small businessbusiness, and enterprise accounts will be provisioned with the adobesign.com domain. 

All existing small businessbusiness, and enterprise 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). 

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.


Planned EOL of SOAP API in February, 2021

First Reported: June 2018 - Updated: June 2020 Current

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 February 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 February 2021.  Direct communications to developers and integrators will occur over the next several quarters to insure a smooth transition to the latest API.


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

First Reported:  June 2020
Current

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
Current

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 >


Fill n Sign has a path for templates and authenticated signing

First Reported: March 2020 Current

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.


Adobe Sign icon and font change

First Reported: January 2020 Current

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.


Planned Application interface changes -
Legacy Custom Workflow UI to be removed after July 2020

First Reported: July 2018 - Updated: January 2020 Current

Custom Workflow Send page – The June 2018 release provided a more consistent Send page experience for custom workflow users.  This new experience is currently optional to provide time for updates to end-user training/documentation as needed.

This option is to be phased out in July 2020.

 

Action required

Below is a description of how to manually set the new experience. 

This setting will no longer be available after July and the new experience will be the default.

No action is necessary to get the new experience after July.  However, if testing is required please follow the instructions below to assure your workflows are compatible with the new Send experience.

Enable the new experience (controlled through the Account > Account Settings > Send Settings > Custom Workflow Send setting in the Admin menu). 

custom_workflow_designercontrols-aug


Planned “End of Life” for the Archive feature

First Reported: October 2019  Current

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 Life” for the Access Code feature

First Reported: December 2019 Current

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.


Additional Resources


Past Notifications


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.

Updates to Mobile Signing Experience

First Reported: September 2019 - Updated: October 2019 Removed From Current List: December, 2019

In our November 2019 launch, improvements will be made to the Adobe Sign recipient experience which include:

  • Responsive design for signer emails
  • Signer experience in a mobile web browser

Key changes on emails include:

  • Removal of agreement thumbnail 
  • Subject line changes on Request emails, for example:
    • From: “Please <participant action> <agreement name>” to “<participant action type> requested on <agreement Name>
      • eg. “Please Sign <agreement Name> to “Signature requested on <agreement Name>"
      • eg. “Please Approve <agreement name> to “Approval requested on <agreement name>"
  • Subject line changes on Signer confirmation emails, for example:
    • From "<Agreement Name>between <Company Name> and <Signer Full Name>) is Signed and Filed!", to "You Signed <agreement Name>"

The signer experience updates include: re-designed mobile responsive signer emails, and changes to streamline the agreement filling and signing experience. Key changes include:

  • Agreement name pop up on viewing of agreement
  • Sender message available in ‘More Options’ (hamburger) menu
  • Navigation bar for guided field navigation and required field countdown
  • Improved smooth zoom for gestures
  • Double-tap gesture to zoom
  • Removal of thumbnail, ‘Reminder’ and “Send another’ links from the post sign confirmation screen

New SSL Certificate Available -
Going into effect October 5th, 2019

First Reported: September 2019 Removed From Current List: December, 2019

Adobe Sign is releasing a new SSL Certificate on October 5th, 2019.
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 5th 2019.

Important changes to IP address ranges

First Reported: September 2019 Removed From Current List: December, 2019

If your existing network or firewall configuration explicitly allows the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration.

See a complete list of IP address ranges in system requirements ›

 

ACTION REQUIRED

If you use the Adobe Sign for Salesforce integration, admins must explicitly allow the additional IP address ranges in their Salesforce.com account (including Sites).

ADD: 51.105.221.160/27

 

If you explicitly list the IP ranges for outbound email relays:

ADD: 51.105.221.64/30

Note:

If you explicitly list Adobe Sign IP addresses in either your API Callbacks or firewall, you must list the additional IP addresses in your API Callbacks.

Notify third parties that route your Callbacks, as applicable.

New Release: Adobe Sign November 2019

First Reported: September 2019 Removed From Current List: December, 2019

The Adobe Sign November 2019 product release is scheduled for early November.

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

No down time is expected with this release. 

End of Support for Sign Mobile OS Versions

First Reported: May 2019 - Updated: September 2019 Removed From Current List: December, 2019

End of Support for Sign Mobile OS Versions

To take advantage of the latest released features in the Sign mobile applications.

  • The Adobe Sign iOS mobile app will require iOS 11 and up
  • The Adobe Sign Android mobile app will require Android 5 and up

Adobe Sign mobile apps support the most recent released versions of iOS and Android. We will continue to support the following moving forward:

  • Latest version and up to one version back for iOS
  • Latest version and up to four versions back for Android

 

ACTION REQUIRED

Upgrade to the latest supported mobile OS version to get access to the latest features.

Adobe Sign mobile apps on older operating systems will continue to work but will not be updated with most recently released features.

Review system requirements here >

Alert messages occurring in automated workflows after June 20th 2019

First Reported: June 2018 Removed From Current List: December, 2019

Starting June 20 2019, automated workflows using document templates with incompatible scopes will display an alert message for both senders (in the classic experience) and admins. These alert messages will not affect the ability to use the automated workflows, however steps should be taken to update the incompatible document templates.

End users will see the alert “This workflow contains documents that are out of scope for users in your account.” Administrators will see the alert “This document template has an inconsistent access scope for this Workflow.”

Full details on this and how to resolve the alert messages are available on this page.  

Custom Workflow Error Messaging

First Reported: August 2019 Removed From Current List: December, 2019

Customers that use the Custom Workflow Designer may be seeing errors that indicate document/authority issues.  

Admins can request their success manager to suppress these error messages while the workflows are being corrected.

Note:

These error messages generally do not prevent using the workflow by the user.  Instead, they indicate a mismatch in the user authority vs. the ownership of the document, which is strongly enforced in the imminent upgrade of the workflow designer.

New Release: Adobe Sign August 2019

First Reported: July 2019 Removed From Current List: September, 2019

The Adobe Sign August 2019 product release was completed August 14th with no down time to the service.

This product release includes added functionality to the new manage page (support for web forms and mega sign transactions) and infrastructure enhancements to further improve platform stability.


New Release: Adobe Sign May 2019

First Reported: April 2019 Removed From Current List: August, 2019

The Adobe Sign May 2019 product released May 21st.

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

No downtime for the service was experienced during this release.


Adobe Sign for "Workplace by Facebook”

First Reported: November 2018 Removed From Current List: August, 2019

Adobe Sign for “Workplace by Facebook” is expected to release in early 2019. This integration allows users to send documents for signature, check the status of all of their agreements, and get Sign notifications inside Workplace Chat.

 

For more information:

 


New release: Adobe Sign for Salesforce v21

First Reported: March 2019 Removed From Current List: May, 2019

Adobe Sign for Salesforce v21 is now available. This release includes new features for administrators and users, including: 

  • Set repeatable signing flows - Revamped Agreement Template makes is easy to create and maintain your signing workflows via Adobe’s Agreement Templates
  • Community Cloud - Get documents signed with Adobe Sign on any Salesforce Portal (customer, partner, employee, citizen).  Users initiate and manage their agreements right from your portal
  • Salesforce CPQ Connector - Updated CPQ connector to enable payments collection when signing the document and adding form fields
  • Government Issued ID - Require signers to verify their ID with a government issued ID

 

The update is available on Adobe Sign’s Salesforce AppExchange listing. 


New (2019) W-4 template available

First Reported: Janurary 2019 Removed From Current List: May, 2019

The new IRS W-4 (2019) form has been added to the Adobe Sign library, entitled W-4 2019 (Employee's Withholding Allowance Certificate)

 

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 2018 version is to be removed from the system in May, 2019.

Any application/API using the legacy (ver 2018) 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 2019 (Employee's Withholding Allowance Certificate) form template (not ver. 2018) to see the libraryDocumentId value. 

 

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.


Immutable Audit Reports have been rolled out to enterprise and business accounts

First Reported: February 2019 Removed From Current List: April, 2019

The December release introduced the new immutable audit report to Adobe Sign at the team, individual, and free levels of service.

As of the February 19th patch release, the enterprise and business tiers of service have adopted this new format.

For more details on the new immutable audit reports, please refer to this article.


New (2019) W-9 template available

First Reported: December 2018 Removed From Current List: April, 2019

The new IRS W-9 form has been added to the Adobe Sign library entitled W-9 (Request for Taxpayer Identification Number) ver. 10/18

 

ACTION REQUIRED

The new W-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 2017 version is to be removed from the system in April, 2019.

Any application/API using the legacy (ver 11/17) form must be updated before April 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-9 (Request for Taxpayer Identification Number) ver. 10/18 form template (not ver. 11/17) to see the libraryDocumentId value. 

 

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

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


Security Notice for the Adobe Sign for Salesforce integration

First Reported: December 2018 Removed From Current List: April, 2019

Versions impacted: All versions prior to 20.9

Adobe Sign for Salesforce customers using a Salesforce Site must take action. The Salesforce security team recently reported a vulnerability. There has been no reported impact to Adobe Sign customers, but action is required.

You can find full details of the required action on this page, as well as information on how to determine if you are using a Salesforce Site.


Salesforce instance update

First Reported: December 2018 Removed From Current List: April, 2019

Salesforce is performing infrastructure upgrades which may result in the name of your Salesforce instance changing. If this occurs, you will need to refresh your auto update setup.   To do this, go the Adobe Sign Admin page and select Enable Automatic Status Updates.

enable_automaticstatusupdates

How can I get more information?

For more information, please contact Support through the Adobe Sign application. Your Support options are presented by first signing in to Adobe Sign (https://secure.echosign.com/public/login) and then selecting the “?” up in the top right-hand corner. Alternatively, contact your customer success manager.


Support for the Adobe Sign for Salesforce integration v18.x and lower ends March 1, 2019.

First Reported: November 2018 Removed From Current List: April, 2019

Product updates, security updates and technical support for Adobe Sign for Salesforce v18 will end on March 1, 2019.

  

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

Get the upgrade guide ›

Download from the AppExchange >

 


Adobe Sign for Salesforce integration v18.x Upgrade

First Reported: December 2018 Removed From Current List: April, 2019

All customers are recommended to upgrade to the latest version of Adobe Sign for Salesforce before March 1 2019.

Re-authenticating your account for automatic status updates from Adobe Sign will no longer work after March 2019 for v18 and lower. 


If you are running version 18 or earlier, you MUST upgrade in order to continue to receive support.

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. 


Fill & Sign is the default to sign anything you’ve been sent

First Reported: December 2018 Removed From Current List: March, 2019

In December 2018, the Fill & Sign interface was enabled as the default way to sign any document you’ve been sent from outside the Adobe Sign service.

Fill & Sign provides the flexibility of a free-form filling and signing experience while providing the trust and security you expect from Adobe Sign electronic signatures.

Our Classic Only I Sign functionality continues to be available via a switch for enterprise customers, but will be eventually discontinued in favor of the simplified Fill & Sign experience.

nav_to_settings


Adobe Sign for Salesforce v20.11 update
(incremental patch)

First Reported: Janurary 2019 Removed From Current List: March, 2019

A new patch for Adobe Sign for Salesforce is available on AppExchange

This patch brings several improvements and fixes for Edge and Internet Explorer browsers.

The full list can be found in the release notes.


New Release: Adobe Sign December 2018 product release

First Reported: November 2018 Removed From Current List: March, 2019

The December 2018 product update released on schedule with several feature improvments.

Reveiw the updated content in the release notes.

 


Integration: Support for the Adobe Sign for Salesforce integration v16 and v17 has ended as of November 15, 2018

First Reported: April 2018 Removed From Current List: January 2019

Product updates, security updates and technical support for Adobe Sign for Salesforce v16 and v17 has ended as of November 15, 2018. 

 

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

Get the upgrade guide ›


Integration: Support ended for Adobe Sign for Dynamics v5

First Reported: July 2018 Removed From Current List: January 2019

Support has ended for Adobe Sign for Dynamics v5.  Adobe Sign for Dynamics 365 CRM  v7 was released in June.

Customers using Dynamics onPrem and Online 365, who have not yet done so, should update to the latest version which is available for download on Adobe Sign’s Microsoft AppSource listing. 

 


Default full screen mode for Adobe Sign UI

First Reported: June 2018 Removed From Current List: October 2018

In order to improve the experience on smaller devices and provide a better reading experience on the desktop, the Adobe Sign March release introduced a more flexible Sign UX based on the width of the browser. 

This was enabled selectively for enterprise accounts and generally for all individual and team accounts. 

In July this became the default configuration.  Users will see the web UI adapted to the width of the page and stack components instead of shrinking them to fit a narrow width.

 

Action Required

No action is needed to take advantage of this new capability however this can be disabled by an account admin by navigating to the Account > Global Settings > Adobe Sign Page Presentation setting and unchecking the box. 

As part of the September release the ability to disable this feature was removed from the application and the more flexible UX became standard.

 


New Release: Adobe Sign September 2018

First Reported: August 2018 Removed From Current List: October 2018

The Adobe Sign September 2018 product release is scheduled for early September.

This product release includes new features and feature enhancements for administrators and end users. No impact to the service is expected with this release. 

 


Adobe Sign is now supports Aadhaar E-KYC API v2.1

First Reported: August 2018 Removed From Current List: October 2018

Aadhaar signing workflow in Adobe Sign has now moved to the latest E-KYC (electronic know your customer) API specifications. This was done to comply with new regulatory changes that mandate v2.1. Signers can now sign an agreement using their Virtual ID (VID). This update also improves the signer’s experience and fixes the Internet Explorer 11 problems reported earlier.


Adobe Sign achieves FedRAMP Tailored certification

First Reported: May 2018 Removed From Current List: October 2018

Adobe Sign is now authorized by the GSA (Government Services Administration of the US) as meeting the requirements of Federal Risk Authorization Management Program (FedRAMP) Tailored, allowing Adobe Sign to be sold and used by non-defense US federal government agencies. 

This certificate means Adobe Sign has been reviewed by the GSA security assessor and has been approved for use at the Li-SaaS In Process level.  Adobe Sign will continue to undergo the constant monitoring required to maintain its status as a certified government cloud service provider. 

You can read more about FedRAMP at https://www.fedramp.gov/


Adobe Sign is focused on promoting data privacy regulations

First Reported: May 2018 Removed From Current List: October 2018

Adobe Sign will comply with the European Union General Data Protection Regulation (GDPR)

This privacy law affects all companies that collect personal information from individuals that are citizens of the EU.  Adobe Sign adheres to the rule to collect the minimum amount of information needed to conduct business during the signing process. 

All participants in Adobe Sign can access and modify their personal information through their user profile and by examining the agreements that they’ve signed. 

Adobe Sign customers that engage with consumers will have the ability to provide information to their customers about what was collected and remove that data according to their business processes. You can read about the new GDPR features of Adobe Sign here.

You can read about Adobe rules and regulations that protect privacy by design across all products here: https://www.adobe.com/privacy.html.


Adobe has begun to auto-expire agreements that are still unsigned and older than 1 year old

First Reported: February 2018 Removed From Current List: October 2018

Starting in October 2018, Adobe Sign has begun to expire agreements that are over 1 year old, and are still in the Waiting For Signature state.

Notifications will not be sent to participants of these agreements but they will be able to see them in their Manage page under the Canceled/Declined list.

 

ACTION REQUIRED

Customers can review their older agreements through the Manage page or by creating a report of agreements older than 1 year and downloading the report.  The filter in both cases is the “Out for Signature” status. 

This new rule applies only to non-terminal agreements.

Agreements that have completed or were canceled or declined will not be impacted.


Integration: Adobe Sign for Salesforce v20 released in July 2018

First Reported: June 2018 Removed From Current List: October 2018

The Adobe Sign for Salesforce Summer Release 2018 (previously referred to as "Spring Release") was released on July 17th 2018.

The Summer Release includes new features and feature enhancements for administrators and end users. The update will be available on Adobe Sign’s Salesforce AppExchange listing. 

 

Read the release notes here.

 


Insecure traffic blocked

First Reported: June 2018 Removed From Current List: August 2018

On June 20th 2018, we ended support for several categories of insecure network traffic for Adobe Sign. This was required to meet specific requirements for PCI compliance.

 

Inbound traffic, or connections made from a client to our servers.

We stopped supporting unencrypted connections to our APIs -- that is, requests that use "http:" rather than "https:".

With this change, customer and partner applications will fail on attempts to establish unencrypted connections.

  • The error behavior will be application-specific.

 

Outbound traffic, or connections made from our servers back to customer-specified servers.

There are two categories:

  • Upload callbacks for document uploads (described here for our REST API, but also applies to the legacy SOAP API)
  • Status callbacks to notify the customer of a change in agreement status (described here for our REST API, but also applies to the legacy SOAP API)

For both categories of callbacks, we stopped supporting:

  • Unencrypted connections (using "http:" rather than "https:" URLs)
  • Connections to servers that do not support TLSv1.2 (in other words, TLSv1.0 and TLSv1.1 will no longer be supported)
  • Connections to servers that have invalid certificates. This includes certificates that are self-signed or expired, as well as cases in which a URL uses an IP address rather than a hostname.

 

Read the FAQ >


New Release: Adobe Sign June 2018

First Reported: May 2018 Removed From Current List: July 2018

The Adobe Sign June 2018 product release was completed on June 11th.

The June 2018 product release includes new features and feature enhancements for administrators and end users. You can find the release notes here.


New SSL Certificate

First Reported: April 2018 Removed From Current List: July 2018

Adobe Sign moved to a new SSL Certificate on May 2, 2018. There is no change to the public key, underlying cryptographic protocols or scheme. Please contact Customer Support with questions.

 

ACTION REQUIRED

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 using other methods, you can find the new Adobe Sign certificates in the Adobe Sign System Requirements. The new SSL certificate became active on May 2, 2018.


Important changes to IP address ranges

First Reported: April 2018 Removed From Current List: July 2018

If your existing network or firewall configuration explicitly lists the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration.

See a complete list of IP address ranges in system requirements ›

 

ACTION REQUIRED

If you explicitly allow Adobe Sign IP addresses in either your API Callbacks or firewall, you must allow the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable.

If you use the Adobe Sign for Salesforce integration, admins must allow the additional IP address ranges in their Salesforce.com account (including Sites).

ADD:

  • 40.67.155.147/32
  • 40.67.154.249/32
  • 40.67.155.185/32
  • 40.67.155.112/32

 

If you are allowing the IP ranges for outbound email relays, add:

  • 40.67.157.141/32
  • 40.67.154.24/32
  • 40.67.158.131/32


Integration: Adobe Sign for Dynamics v7 release

First Reported: June 2018 Removed From Current List: July 2018

The Adobe Sign for Dynamics 365 CRM Summer Release 2018 (v7) is scheduled for mid-June.

 

This release goes deeper with Microsoft Dynamics 365 CRM with a redesigned UI for quick navigation, and adds customer contact details from LinkedIn so you can always “see” who you’re sending to.  In addition, customers can now completely automate their Adobe Sign processes by embedding Adobe Sign directly into Microsoft Dynamics 365 CRM workflows.

 

The update is available on Adobe Sign’s Microsoft AppSource listing.  No impact to the service is expected with this release.


Integration: Action required for Adobe Sign for Salesforce v19.x customers

First Reported: June 2018 Removed From Current List: July 2018

If you are running Adobe Sign for Salesforce version 19.x, you must upgrade to version 19.5.2 either before June 1, 2018 or June 8, 2018, depending on your Salesforce.com organization. The Salesforce Summer ’18 release, being progressively rolled out in June by Salesforce, has changes which affect backwards compatibility with the Adobe Sign for Salesforce integration and will impact the ability to send some agreements.

Starting June 1, 2018, customers running Adobe Sign for Salesforce version 19.x who are upgraded to Salesforce Summer ’18 will be unable to add recipients and send agreements on the Lightning version of the Send page*.

 

ACTION REQUIRED

If you are running v19.x, upgrade to Adobe Sign for Salesforce v19.5.2 before Salesforce upgrades your org to Salesforce Summer ’18:

  • Go to the AppExchange, click Get It Now and follow the instructions. 

If you need help with upgrading, please refer to our Adobe Sign for Salesforce (v19) Upgrade Guide.


New SSL Certificate

First Reported: April 2018 Removed From Current List: July 2018

Adobe Sign is moving to a new SSL Certificate on May 2, 2018. There is no change to the public key, underlying cryptographic protocols or scheme. Please contact Customer Support with questions.

 

ACTION REQUIRED

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

If you’re pinning the certificate using other methods, you can find the new Adobe Sign certificates in the Adobe Sign System Requirements. The new SSL certificate becomes active on May 2, 2018.


Adobe Sign March release complete

First Reported: January 2018 Removed From Current List: May 2018

The Adobe Sign March 2018 product release was completed 12:00pm PST, March 15, 2018.

For more details, review the full release notes.

Release notes

SAP SuccessFactors will be released in April.


2017 version of the W-4 US tax form to be removed from service 4/17/18

First Reported: April 2018 Removed From Current List: May 2018

The 2017 version of the W-4 US Tax form template will be removed from the Adobe Sign library on April 17th, 2018.

Customers that are using the W-4 from the Adobe Sign library via API should update their document ID to the 2018 version (See below)

 

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


2018 version of the W-4 US tax form is available

First Reported: March 2018 Removed From Current List: May 2018

On 3/13/18, a new template for the IRS W-4 form was added to Adobe Sign. It is entitled W-4 2018 (Employee’s Withholding Allowance Certificate)

 

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.

 

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 form template (not the 2017 version) to see the libraryDocumentId value. 

 

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

find_librarydocid-March1

5. In the Response Body, locate the new W-4 form template (not the 2017 version) to see the libraryDocumentId value. 

 

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


Security Notice: Support of TLS 1.0 and 1.1 ends April 9 2018

First Reported: January 2017 Removed From Current List: May 2018

Adobe will be removing support for TLS 1.0 and 1.1 protocols in 2018 to meet industry best practices for SSL/TLS security.

On April 8th, the SSL handshake protocol TLS 1.2 will be required, and the older TLS 1.0 and TLS 1.1 protocols will no longer be accepted. Clients that do not use TLS 1.2 will be unable to make network connections to the Adobe Sign service.

 

ACTION REQUIRED

For clients running web browsers: Use a supported browser (see System requirements).

For clients running applications using Adobe Sign APIs: Support for TLS 1.2 may depend on the application, the runtime libraries, and/or the operating system. In some cases, TLS support is provided by operating system libraries, while in other cases it is provided by an application runtime library.

For clients running Adobe Sign for Dynamics v5.x and earlier, upgrade to v6.0.

Operating system support for TLS 1.2 requires:

  • Windows server: use Windows Server 2008 R2 or later
  • Windows desktop: use Windows 8 or later
  • OS X: use OS X 10.8 or later

 

Application framework support for TLS 1.2:

  • For Java: use Java 8 or later. Java 7 may be used but requires TLSv1.2 to be explicitly enabled by the application.
  • For .NET: use .NET 4.6 or later. .NET 4.5 may be used but requires TLSv1.2 to be explicitly enabled by the application. .NET depends on TLS 1.2 support by Windows (see above).
  • For applications using OpenSSL: use OpenSSL 1.01 or later 

FAQ for this EOL >

Read about system requirements ›


Integration: End-of-life for the Adobe Sign for Microsoft Dynamics v4 and v5

First Reported: February 2018 Removed From Current List: May 2018

Adobe Sign for Microsoft Dynamics v4, v5, and earlier (on-premise and online versions) is now retired. Adobe Sign for Dynamics v6 and later supports Microsoft Dynamics on-premise 2013, 2015, 365 and Dynamics CRM 365 Online. Contact your Customer Success manager with questions about upgrading to the latest version.

Read the Release Notes ›

Get the Update Guide ›

 

ACTION REQUIRED

Upgrade to Adobe Sign for Microsoft Dynamics v6 immediately for on-premise and online versions. You will be able to migrate all data from v4 and earlier to the latest version.


Integration: End-of-life for the Adobe Sign for Microsoft Dynamics v4

First Reported: September 2016 Removed From Current List: May 2018

Adobe Sign for Microsoft Dynamics v4 and earlier (on-premise and online versions) has been discontinued and no longer functions as of November 30, 2017. Adobe Sign for Dynamics v6 and later supports Microsoft Dynamics on-premise 2013, 2015, 365 and Dynamics CRM 365 Online. Contact your Customer Success manager with questions about upgrading to the latest version.

Read the Release Notes ›

Get the Update Guide ›

 

ACTION REQUIRED

Upgrade to Adobe Sign for Microsoft Dynamics v6 before November 2017 for on- premise and online versions. You will be able to migrate all data from v4 and earlier to the latest version.


Latest template for IRS form W-9 available February 13

First Reported: February 2018 Removed From Current List: April 2018

On 2/13/18, a new template for the IRS W-9 form will be added to Adobe Sign. It is entitled W-9 (Request for Taxpayer Identification Number) ver. 11/17. Concurrently, the existing W-9 template will be renamed to W-9 (Request for Taxpayer Identification Number) (legacy). This renaming does NOT affect your workflows.

On 3/13/18, the latter template, W-9 (Request for Taxpayer Identification Number) (legacy), will be retired. Prior to 3/13/18, you must take action to avoid interruptions to your workflow.

 

ACTION REQUIRED

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

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 
    1. Enable the library_read:self scope
  4. Click the Try it out! button
  5. In the Response Body, locate the new W-9 form template (not the legacy version) to see the libraryDocumentId value. 

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


Integration: End-of-life for Adobe Sign for Microsoft SharePoint v3 and below

First Reported: October 2017 Removed From Current List: April 2018

Adobe Sign for Microsoft SharePoint v3 and earlier (on-premise and online versions) will no longer function as of March 31, 2017. Adobe Sign for SharePoint v4 and later supports Microsoft SharePoint on-premise 2013, 2016 and SharePoint Online.

 

Action Required:

Upgrade to Adobe Sign for SharePoint v4 immediately. Contact your Customer Success manager with questions about upgrading to the latest version.

 

Get the Upgrade Guide ›


Integration: Critical update to Adobe Sign for Salesforce v18

First Reported: May 2017 Removed From Current List: March 2018

Salesforce will enforce a new security model for Lightning Components called LockerService in an upcoming release. If you are on Adobe Sign for Salesforce v18, you must upgrade to version 18.27 or higher to ensure all Salesforce Lightning Components work as intended.

 

ACTION REQUIRED

If you are on Adobe Sign for Salesforce v18, you must upgrade to version 18.27 or higher.

Learn about Salesforce LockerService ›

Get the latest package from the AppExchange ›


Integration: Support for the Adobe Sign integration with Salesforce v15 has ended

First Reported: April 2017 Removed From Current List: March 2018

Product updates, security updates and technical support for Adobe Sign for Salesforce v15 has ended as of December 15, 2017

Version 19 is available now in the Salesforce AppExchange.

 

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

Get the upgrade guide ›

 

IMPORTANT 

Review the required by Salesforce permissions settings before starting your upgrade to v19 in the What’s new in version 1section:

https://helpx.adobe.com/sign/help/adobe_sign_for_salesforce_upgrade_guide.html


Adobe Sign templates for 2017 IRS form I-9 is now available.

First Reported: November 2017 Removed From Current List: Feburary 2018

On 10/24 the new template for the revised IRS I-9 form was added to Adobe Sign. It is entitled: I-9 (Employment Eligibility Verification) ver. 07/17/17 N.  

Concurrently, the existing template I-9 2017 (Employment Eligibility Verification) was renamed to: I-9 (Employment Eligibility Verification) ver. 07/17/17 N (legacy).

This renaming does NOT affect your workflow.

However, on 12/1/17, the latter template, I-9 (Employment Eligibility Verification) ver. 07/17/17 N (legacy), was retired.

If you are using the legacy template’s libraryDocumentId in your applications, you need to update to use the new libraryDocumentId value.

 

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.

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 
    1. Enable the library_read:self scope
  4. Click the Try it out! button
  5. In the Response Body, locate the revised I-9 form template (I-9 (Employment Eligibility Verification) ver. 07/17/17 N ) to see the libraryDocumentId value. 

 

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


Important changes to IP address ranges

First Reported: June 2017 Removed From Current List: Feburary 2018

If your existing network or firewall configuration explicitly explicitly lists the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration; however, you should remove two outdate IP address ranges for North America.

See a complete list of IP address ranges in system requirements ›

 

ACTION REQUIRED

If you explicitly list Adobe Sign IP addresses in either your API Callbacks or firewall, you must list the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable.

If you use the Adobe Sign for Salesforce integration, admins must list the additional IP address ranges in their Salesforce.com account.

ADD:

India:

 

13.126.23.0/27

REMOVE:

North America:

 

166.78.79.112/28

207.97.227.112/28


Integration: Critical update to Adobe Sign for NetSuite

First Reported: May 2017 Removed From Current List: Feburary 2018

Oracle recently upgraded to NetSuite 17.0. The upgrade caused an issue in Adobe Sign for NetSuite in which the Agreement tab may not appear for some roles. Upgrade to Adobe Sign for NetSuite version 4.0.1 to ensure roles provisioned by the administrator on the agreement record will be able to see the Agreement tab.

 

ACTION REQUIRED

Login to the application and upgrade to Adobe Sign for NetSuite version 4.0.1 to ensure users will be able to see the Adobe Sign Agreement tab.

New Release: Adobe Sign September 2017 release

First Reported: September 2017 Removed From Current List: November 2017

The Adobe Sign September 2017 product release is now complete. This release includes new features and feature enhancements for administrators and end users, including:

  • Support for eIDAS compliant time stamps, certified on the EU Trusted List (EUTL)
  • Support for new configurable time stamp services in case your company already uses an LTV time stamp provider
  • Broader support for Cloud Signature Consortium with new partners announced
  • Support for Aadhaar identity compliance and a new data center in India (IN1)
  • Color coded form fields and new form field font support for a better authoring and user experience
  • Form Field detection rolled out further to the field
  • Replace or add recipients in flight

 

Broader support for Microsoft products with new or improved integrations to:

  • Office 365 – Outlook, Word & PPT
  • Dynamics CRM v6
  • Teams
  • Flow

Read the Release Notes ›


Security: Support has ended for Windows Vista SP2 and Internet Explorer 9 and 10

First Reported: March 2017 Removed From Current List: November 2017

Adobe Sign ended support for Windows Vista SP2 and Internet Explorer 9 and 10 on March 17, 2017. Customers continuing to use these browsers will not be able to take advantage of new features and cannot be guaranteed access to Adobe Sign in the future.

 

ACTION REQUIRED

Update older hardware to newer operating system configurations including, Windows 7, 8 or 10 with one of the supported browsers listed in the Adobe Sign System Requirements to ensure new Adobe Sign features continue to work as intended.

Read about system requirements ›

Adobe Sign May release is now complete

First Reported: April 2017 Removed From Current List: July 2017

The Adobe Sign May release is now complete. This release includes new features and feature enhancements for administrators and end users. With this release, the classic Send and Authoring user interface have been retired, and the new user interface became the standard across Adobe Sign. API integrations that embed the Send page will also experience the change in the user interface. The new Send experience maintains all the functionality of the classic Send experience, except for the Fax signature workflow, which was replaced with a new scan and upload Written signature workflow. The new Send and Authoring experiences also include new capabilities, including private messages, new recipient roles and more.

New agreements now have updated appearance options for assigned text fields. The previous options of Helvetica, Times and Courier have been replaced with Adobe font equivalents of Adobe Source Sans Pro, Source Code Pro, and Source Serif Pro, respectively.

Not all features in this release were enabled at deployment. Some features will be activated in June. Read the Release Notes for more details.

Release Notes ›

Read about the Embedded Send page changes ›

Read about the Written Signature changes ›

 

ACTION REQUIRED

No action is required.
 


New SSL Certificate and Certificate Authority

First Reported: June 2017 Removed From Current List: July 2017

Adobe Sign is moving to a new SSL Certificate and Certificate Authority (CA) on

July 22, 2017. There is no change to the public key, underlying cryptographic protocols or scheme. The root and intermediate CA will change with this update. Please contact Customer Support with questions.

 

ACTION REQUIRED

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

 

If you’re pinning the certificate using other methods, you can find the new Adobe Sign and CA certificates in the Adobe Sign System Requirements. The new SSL certificate and certificate authority will become active on July 22, 2017.

Read about the system requirements ›


API: New setting to customize the error code generated in case of URL expiry

First Reported: May 2017 Removed From Current List: July 2017

Currently, the HTTP error code returned when a URL expires is 404 (page not found), which is not compliant with HTTP standards. These URLs can be generated by REST API calls such as GET/agreements/{agrID}/combinedDocument/url. However, the more appropriate HTTP error code is 410 (gone). With the May release, the default HTTP error code was changed to 410. A new setting is available to allow a custom HTTP Status Code (404, 410, etc.) to be sent in this error scenario.

 

ACTION REQUIRED

If your applications expect an expired URL to throw a 404 error, you will need to request a change to the value of this setting to 404. Contact Customer Support for assistance.


Feature Deprecation: Fax Signature workflow

First Reported: May 2017 Removed From Current List: July 2017

With the May 2017 release, the new Send experience became the standard, and with it, the Fax signature workflow was replaced with a new Written signature workflow using scan and upload. The modern scan and upload functionality provides improved accuracy and auditability and results in better readability. Customers that use the API were also moved to the new Written signature workflow.

The classic Send experience with Fax signatures will be available for a limited time; however, it will be deprecated on October 31, 2017. Web application users that want to continue using the Fax signature workflow can do so by reverting to the classic Send page through the Send Settings. API users need to contact their Customer Success manager to continue to use the Fax signature workflow.

 

ACTION REQUIRED

Review the new Written signature workflow documentation and inform your end users of the changes. You may also need to update your end user and customer documentation for written signature workflows.

Read about the new written signature workflow ›


Mobile: Google ID and Google Apps login in the Adobe Sign mobile app will be removed

First Reported: March 2017 Removed From Current List: June 2017

In an effort to improve security and usability, Google no longer allows OAuth authentication requests to Google via embedded browsers known as web views in native mobile applications. As a result, the Google and Google Apps login options have been removed from the Adobe Sign mobile app with the May release.

Adobe Sign users will still be able to login with their Google IDs via the standard login (email and password). The only difference is the removal of the Google and Google Apps options on the login page. If you encounter issues with standard login and your Google ID, reset your password and try again.

Read the Google blog ›

 


Planned Maintenance with Downtime for North America (NA1)

First Reported: January 2017 Removed From Current List: April 2017

Adobe Sign will undergo a period of planned maintenance at our North America (NA1) data center with expected downtime on:

Saturday, April 8, 2017 starting at 5:00 PM PDT and ending April 8 at 11:00 PM PDT

Customers located in our other data centers are not expected to be impacted.

The planned maintenance is required to complete the expansion of our North America data center operations. During the maintenance window, the service will be unavailable on NA1.

To confirm the data center for your account, login to Adobe Sign and note the abbreviation in the URL (NA1, NA2, etc.). Contact your customer success manager with questions.

 

ACTION REQUIRED

  • If you use the Adobe Sign for Salesforce integration: Salesforce Integration admins must explicitly list the additional IP address ranges in their Salesforce.com account for the integration to continue to work after April 7, 2017. 
  • If you list Adobe Sign IP addresses in either your API Callbacks or firewall: Adobe Sign admins must list the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable. Without adding the new IP ranges, the callbacks will not be allowed through your firewall. IP Address Ranges and Planned Maintenance FAQ ›


Integration: Support for the Adobe Sign integration with Salesforce v14 has ended

First Reported: September 2016 Removed From Current List: February 2017

Product updates, security updates and technical support for Adobe Sign for Salesforce v14 ended December 15, 2016. Version 18 is available now.

 

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce. Customers using unsupported versions will be required to upgrade to a current version to continue to receive technical support.

Get the upgrade guide

 


API: OAuth application support for SOAP API to be deprecated

First Reported: November 2016 Removed From Current List: February 2017

With the December maintenance release, new OAuth applications are only able to access REST APIs. Existing OAuth applications and integration keys will continue to have access to SOAP APIs until further notice.

 

ACTION REQUIRED

Use the REST APIs when developing any new application. For more information, go to the Developer Center.

 


API & Web App: Password Complexity rules will change in 2017

First Reported: November 2016 Removed From Current List: February 2017

Adobe Sign is changing the password complexity rules to increase security. In early 2017, customers using the web application will be prompted to update their password, and will have 90 days to comply. Customers that login or provision users through the existing REST or SOAP APIs will have until mid-2018 to update their applications to comply with the Adobe Sign password security requirements. Information on how to transition to the new rules will be available for API users in early 2017.

New password criteria:
• A minimum of 8 characters, maximum of 100 characters
• At least one uppercase character
• At least one lowercase character
• At least one digit
• At least one special character (punctuation), except empty space
• Cannot contain case insensitive username, first name or last name
• The new password will be rejected if it matches previously used passwords

 

ACTION REQUIRED

In early 2017, web application users should update passwords when requested. Customers that provision users through the API will have until July 2018 to update their applications to use REST API to comply with the new password criteria.

 


API & Web App: Support has ended for older Text Tag syntax

First Reported: June 2016 Removed From Current List: February 2017

Support for v1.0 text tags has ended. While v1.0 tags will continue to be honored in the service, no bugs or enhancement requests will be accepted for this syntax.

 

ACTION REQUIRED
Ensure your users are using 2.0 text tag syntax when creating new document templates. Review applications and existing templates that may contain older text tags and update them with the newer 2.0 text tag syntax. Refer to Creating Forms with Text Tags Reference Guide for details.

Read the Text Tag Reference Guide ›


Technical Update: January 2017 (Advanced Notice)

First Reported: June 2016 Removed From Current List: February 2017

Adobe Sign templates for 2017 IRS forms I-9 and W-4 are now available. The templates entitled I-9 (Employment Eligibility Verification 2016) and W-4 2016 (IRS Employees Withholding Allowance) will be unavailable at 12:00 AM PT on January 20, 2017.

 

ACTION REQUIRED

The 2017 IRS form templates have new Document IDs. If you use the Document ID in your applications, you will need to update the Document IDs.

To find the LibraryDocumentID in an API-enabled account:

  1. Log in as an Adobe Sign Account Admin
  2. Generate an Integration Key
  3. Navigate to the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
  4. Scroll down to the Resources and Operations section
  5. In the /libraryDocuments row, click the Show/Hide link to expose the methods
  6. Click the first GET button next to the /libraryDocuments option
  7. Paste your Integration Key into the ‘Access-Token’ field 
  8. Click the Try it out! button. 
  9. Locate the 2017 I-9 and W-4 forms to see the LibraryDocumentID values

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