Technical notifications

This will be a minor patch release to resolve a number of customer-found defects and apply any optimization/security patches as needed.

The Sandbox environment will adopt these patches four weeks prior to the scheduled release. A listing of the resolved customer issues will be published at that time and updated 14 days prior to release.

The release schedule and prerelease notes can be reviewed here >

With the launch of the November 8th, 2022 release, Adobe Acrobat Sign will complete 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 will no longer be 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.

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

The Workflows tab will be removed from the Admin menu and replaced with a Workflows tab 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 new Your workflows page is designed in the same style as the Manage page, complete with quick actions that are available when hovering over a workflow record.  Quick actions for workflows are:

• Open - Opens the workflow in a view-only mode.
• Edit - Opens the workflow to edit the properties. Available only to the workflow owner and administrators that have authority over the group the workflow is assigned to.
  
• Run - Triggers the start of the workflow, opening the modified Send page with the pre-defined settings of the workflow.

The CDS certificate applied to the PDFs generated in Acrobat Sign will be updated in a future release of the application, sometime after the November 8th release.

On November 8th, 2022, Acrobat Sign is rolling out 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.
• Accounts existing before November 9th, 2022, will be migrated to the webhook 2.0 environment on March 14th, 2023.
  
• 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 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.

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:

The search functionality used to find agreements has been improved to support more complex string queries using special syntax. The documentation for the improved search functionality is available in the online help documentation.

The upgraded search feature has been deployed to all tiers of service on all shards as of the November 2022 release

A link to the documentation for searching is provided in the application by clicking the information icon next to the search field:

In the November 2022 feature release, the Box.com upload option was removed from the Send in Bulk interface.

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

Past Notifications

Two new webhooks have been added in the June 14th release:

• Agreement expiration updated (AGREEMENT_EXPIRATION_UPDATED) (Only available via REST v6 API POST /webhooks) - Triggers when an agreement's expiration date is updated.
  
• Agreement signer name changed by signer (AGREEMENT_SIGNER_NAME_CHANGED_BY_SIGNER) - Triggered when a recipient changes their name when signing to be a different value than the name provided when the agreement was created.

Both webhooks are available.

The payload for the new webhooks can be viewed here >

The Access Code feature has been completely removed from the Acrobat Sign system with the June 2022 release when the classic Manage page was removed from service.  

End of support for the Microsoft Internet Explorer 11 and legacy Edge browsers as of December 31st, 2021

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 e-Sign 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.

Acrobat Sign has released the new SSL Certificates on the morning of April 1st, 2022.
There is 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 April 1st, 2022.  

The new SSL certificates are now active as of April 1st, 2022.

Archived Notifications

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