Technical notifications

This will be a major release, including feature improvements for users and administrators, as well as resolutions to multiple customer-reported issues.  

Customers with a Sandbox entitlement will have access to the new features four weeks prior to launch. Prerelease notes for the release content will also be available at that time.

The release schedule and prerelease notes can be reviewed here >

On November 8th, 2022, Acrobat Sign delivered an improved version of webhooks infrastructure (referred to as “webhooks 2.0”).

• New customer accounts created after November 8th, 2022, are automatically built with webhooks 2.0 enabled.
• The Sandbox environment will be updated on March 9th, 2023.
  
• Accounts existing before November 9th, 2022, are to be migrated to the webhook 2.0 environment after the March 14th, 2023 release.
  
• On July 18th, 2023, Acrobat Sign will sunset the current webhooks infrastructure (referred to as “classic webhooks”).

Webhooks 2.0 supports all the features of classic webhooks with one caveat. Classic webhooks configured for the user, their group, or their account, delivered notifications to all participants of an agreement. In webhooks 2.0, ONLY webhooks configured for the sender, sender’s group or account will receive notifications. In other words, notifications are no longer sent to all participants of an agreement.

Note that all future webhook enhancements will ONLY be delivered on webhooks 2.0.   

Current customers can try webhooks 2.0 on a Trial, Developer, or Sandbox account via Adobe’s Insider Access program starting November 8th. 

The migration is expected to be seamless for all customers. However, customers who have strict network security policies in place will require new IP addresses to be configured in accordance with https://helpx.adobe.com/sign/system-requirements.html. 

If you have any questions, reach out to your success manager or the support team.

The feature that automatically detects and places form fields for the in-application authoring environment is being updated to improve the detection methodology. In practice, users will notice that the field detection notification is placed in the center of the first page.

Customer deployment will follow the below schedule:

In the April 2023 release, the header and footer of the web application will be redesigned to better accommodate displays on smaller platforms, and to improve accessibility.

• The double-stacked header will be merged to contain the branded logo and the navigation tabs in one header bar.
• The header bar will collapse into an options icon on smaller platforms or when the screen magnification requires the space to properly display the content.
  
• The footer will be removed entirely, relocating the Language selector into the profile menu in the top right corner of the page.

Coming soon to Acrobat Sign for Teams: Conveniently send Teams and OneDrive files for signature directly from the application.

1. On the new Documents tab, select from your Recents, Teams and channels, or OneDrive files.
2. Select the recipient from your contacts using Azure Active Directory.
   
3. Select to send directly for signature or choose add options and edit agreement to customize your agreement before sending.

To enable this feature, the Acrobat Sign for Teams application needs permission to access user files stored in M365, including Teams and OneDrive. Granting access to user files is not required to access other application features and is only requested when the user explicitly navigates to the Documents tab.  

Consenting to the Documents Tab Set of Permissions for Administrators

Prerequisite: The basic Adobe Acrobat Sign for Teams app permissions are already consented to for your organization.

Consenting to the permissions for the Documents tab enables those features for all users in the organization. There are two options:

Consenting to the Documents Tab Set of Permissions for Individuals

For organizations that rely on individuals to manage their own permissions, Acrobat Sign for Teams users must consent to the new permissions when they navigate to the Documents tab, where a dialog automatically appears:  

Selecting Next opens a new window allowing the user to authenticate with their Microsoft account and consent to the permissions.

Selecting Cancel returns the user to the Home tab. 

Modifications to HTML pages delivered by Adobe, except for those enabled by published APIs and features, are unsupported. Such modifications may interfere with the functionality of Acrobat Sign. Adobe may, at any time, make technical changes that disable the function of any non-Adobe-sanctioned HTML page modifications.

If your use of Acrobat Sign currently relies on modifying HTML from Acrobat Sign using browser extensions,  HTTP proxies, or any other means not enabled by Adobe published APIs and features, you should migrate away from these as soon as possible to avoid disruption.

This statement applies to any mechanism by which such modifications may be made, such as browser extensions and browser configurations which allow HTTP proxies to modify page content.

The Acrobat Sign for Veeva Vault integration is being upgraded to provide the functionality to notify users when their signature is required on an agreement and allow them to sign within the Veeva Vault environment.

The new IRS W-4 (2023) form, entitled W-4 2023 (Employee's Withholding Certificate), has been added to the Adobe Sign library as part of the January 2023 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 2022 version is to be removed from the system in March 2023.

Any application/API using the legacy (ver 2022) form must be updated before March 1^st 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 2023 (Employee's Withholding Certificate) form template (not ver. 2022) to see the libraryDocumentId value.  

The March 2023 release will update the access points for users who can create and use custom workflows. 

A new Workflows tab will be added at the top of the page and a Create a workflow tile on the Home page. Both new access points open a new page dedicated to creating and managing the workflows available to the user.

The November 2022 release for Acrobat Sign includes two updates to the new reporting environment:

• Scheduling and distribution of reports and data exports
• Addition of previously missing columns in data exports

This release brings the new reporting interface into feature parity with the classic reporting structure and begins the process of adding new capabilities.

All future development for reporting features will be built on the new experience only. Consequently, the classic reporting interface will be removed from service in 2023.

All users and administrators are encouraged to migrate their reporting tasks to the new experience as soon as possible.

Domain name change to AdobeSign.com

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, 3^rd 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

Additional Resources

• Community forums 
• Weekly Training - Weekly Webinar covering training topics for new users and administrators
• Adobe Sign Innovation Series - Monthly Webinar covering the hottest topics in the Adobe Sign space

Acrobat Sign successfully rotated the SSL Certificate on the morning of March 1st, 2023.
There was no change to the public key, underlying cryptographic protocols, or scheme.

ACTION REQUIRED

Use of the public key

• If you have custom-built integrations with Acrobat 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 Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign certificates in the Adobe Acrobat Sign System Requirements.
  • If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the April switch.
  • If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on March 1st, 2023.  

The new SSL certificate has been active since March 1st, 2023.

The CDS certificate applied to the PDFs generated in Acrobat Sign has been updated to reflect the correct branding on the certificate as Adobe Acrobat Sign. The update was completed on February 7th, 2023.

Past Notifications

With the launch of the November 8th, 2022 release, Adobe Acrobat Sign has completed the end-of-support cycle for the Microsoft Internet Explorer 11 and the legacy Microsoft Edge browsers that was started in April of 2021.

After the November release, these legacy browsers are no longer supported on any page of the Acrobat Sign application, including the recipient e-signing page. Users attempting to access the service with these browsers will be served an "Unsupported Browser" page and instructed to use (or download) a modern browser.

Archived Notifications

Listed by the date when the notice was removed from the current notice list, newest to oldest.