Technical notifications

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

 

[Important] The next Adobe Acrobat Sign release is scheduled for September 17, 2024

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

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

Feature Release: Adobe Acrobat Sign – June 18th Release Completed

The release was completed to all shards with no downtime to any services.


[Important]
 Disablement of the SOAP API from Adobe Acrobat Sign accounts is scheduled to start in February 2024

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.

Initially announced in June 2018, the effort to sunset the Acrobat Sign SOAP API will be completed in 2024.

Customer use of the SOAP API is scheduled to be disabled through a rolling process starting in February 2024. All customers and partners using the SOAP API must migrate to REST v6 API or risk a disruption in their service.

Please review the REST v6 and migration documentation:

Access to the SOAP API will be removed per the following schedule:

Account type

SOAP API Disablement Date

  • Free
  • Trial
  • Developer

February 1, 2024 (Completed)

  • Enterprise
  • Business

April 1, 2024 (Completed)

  • Integration Only Partners

The scheduled date has been moved up to July 1, 2024, replacing the previous date of December 1, 2024.

  • Embedded Partners

March 1, 2025


[Important]
 Disablement of the SOAP API for Adobe Acrobat Sign Integration Partners has been moved up to July 1, 2024

First Reported: June 2018 - Updated March 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.

The Acrobat Sign deprecation of the SOAP API has been moved up to July 1, 2024, for all integration partners.

All partners using the SOAP API must migrate to REST v6 API or risk a disruption in their service.

Please review the REST v6 and migration documentation:

Access to the SOAP API will be removed from access for integration partners on July 1, 2024.


[Important]
 Disablement of the SOAP API for Adobe Acrobat Sign Embedded Partners has been scheduled for March 1, 2025

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.

Access to the SOAP API will be removed for all embed partners starting March 1, 2025.
To ensure continued function, all embed partners using the Adobe Acrobat Sign SOAP API must migrate to the latest REST API V6 before March 1, 2025.  

Please review the REST v6 and migration documentation for reference:

For any queries, please contact your designated Adobe Acrobat Sign PSM.
 


[Updated]
 The new Request Signature environment will be promoted to be the default experience in the September 2024 release.
Switch links between Classic and New environments will be removed in the  November 2024 release.

הערה:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: March 2024 - Updated June 2024

Current 

The new and improved Request Signature environment will be the default experience for all accounts to create a new agreement starting with the September 17, 2024, release.

Links will remain available for users to switch between the new and classic environments, and administrators will continue to have the option to reset the default to the classic experience through their admin menu.

The classic environment will be entirely removed from the user experience by March 2025.

הערה:

The new in-application Authoring experience is only available as part of the new Request Signature experience.
Customers who are using new Authoring with classic Request Signature will default to the new Request Signature experience after the September 17 release, and the setting for new authoring will be removed from the admin menu.

As part of the November 2024 release, all accounts will have their default sending environment set to the new Request Signature experience.

The option to enable the switch links for users to switch between the environments will also be disabled.

הערה:

Administrators will continue to have the option to enable the switch links in the admin menu.


[New]
The classic Compose page will be retired and removed from the interface in the March 2025 release.

הערה:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: June 2024

Current 

In the March 2025 release, the classic Compose interface will be removed entirely from the Acrobat Sign interface, completing the promotion of the new Request Signature experience.

All commercial accounts that have not configured the new Request Signature service as their default experience will have the Request Signature environment enabled as the only environment for configuring new agreements.

The option to configure the experience, including the switch links between environments, will be removed from the admin menus.


[New]
External source drives to be removed from support in the new Request Signature experience

First Reported: May 2024

Current 

The option to use an external drive for uploading files will be limited to OneDrive only in the new Request Signature experience.

It's recommended that customers who use other options for file upload use the vendor-specific application to provide a networked drive that can be accessed through the native file picker on the user's local system.


[New]
 An update has been applied to the legacy code that determines whether IP addresses are to be included in audit reports, correcting inconsistent behavior in accounts created before June 17, 2021.

First Reported: May 2024

Current 

On June 21, 2021, an administrative setting, "Request IP addresses from signers," was added to the Signature Preferences tab on the Account and Group pages to specify whether signer IP addresses should be collected and included in audit reports.  For compatibility with previous behavior, the setting defaulted to True (checked) for existing accounts as of that date and False (unchecked) for accounts created after that date.

However, we discovered that for some users subsequently added to existing accounts, the default was not respected, causing audit reports to lack signer IP addresses.

With this update to the legacy code, the product behavior now correctly follows the setting.

 


[New]
Adobe Acrobat Sign database update impacting the Digital Identity Gateway service August 1, 2024.

First Reported: June 2024

Current 

Acrobat Sign recipients will not be able to verify their identity using Identity Providers available via the Digital Identity Gateway during a system database migration on August 1, 2024 (the exact time window to be determined). The total downtime is expected to be roughly 20 minutes.

Impacted users can try again at the end of the maintenance activity.


[New]
Adobe Acrobat Sign maintenance impacting the Sandbox service August 6, 2024.

First Reported: June 2024

Current 

The Acrobat Sign Sandbox will be temporarily unavailable on August 6, 2024 (the exact time window to be determined) while Acrobat Sign performs system maintenance. During that time, OEM Partners with an Acrobat Sign Sandbox account will be unable to perform routine Sandbox tasks like provisioning accounts and users via API, onboarding users, etc. Full Sandbox functionality will be restored on the same day. The total downtime is expected to be roughly 20 minutes.


[New]
Adobe Acrobat Sign database update impacting the integrated Power Automate service August 8, 2024.

First Reported: June 2024

Current 

Acrobat Sign customers will not be able to create or modify Power Automate flows from the Acrobat Sign website during a system database migration occurring on August 8, 2024 (the exact time window to be determined). The total downtime is expected to be roughly 20 minutes.


[New]
Adobe Acrobat Sign database update impacting the Data Governance retention service August 12, 2024.

First Reported: June 2024

Current 

Acrobat Sign customers will not be able to create or modify Data Governance retention policies during a system database migration occurring on August 12, 2024 (the exact time window to be determined). The total downtime is expected to be roughly 20 minutes.

Additionally, the service will fail to schedule or process agreements subject to existing Retention Policies during this time. These jobs will be resumed at the end of the maintenance activity.


[New]
Adobe Acrobat Sign maintenance impacting the Send in Bulk service - August 16, 2024.

First Reported: June 2024

Current 

Acrobat Sign will be making updates to the Bulk Agreement Processor, which manages the processing of the Send in Bulk feature. The upgrade will occur on August 16, 2024 (the exact time window to be determined). The total downtime is expected to be roughly 20 minutes.

During the upgrade, users can still create new Send in Bulk transactions through the user interface or API.

  • Newly created Send in Bulk transactions will be accepted, but the generation of the child agreements will not commence until the update is completed.
  • Send in Bulk transactions that are started, but have not completed the child agreement generation process, will be suspended until the update is completed.
  • Existing transactions will not be affected, and customers will be able to complete their actions on existing agreements without issue.


[New]
Adobe Acrobat Sign database update impacting the Webhook service September 5, 2024.

First Reported: June 2024

Current 

Acrobat Sign customers will not be able to create or modify Webhooks, and Webhook notifications will be delayed during a system database migration occurring on September 5, 2024 (the exact time window to be determined). The total downtime is expected to be roughly 20 minutes.

Delayed notifications will be delivered after the update is completed.


Adobe Acrobat Sign's new
Send in Bulk environment became the default experience for all accounts on April 9, 2024.
The classic Send in Bulk environment will be retired in March 2025.

First Reported: March 2024

Current 

The new and improved Send in Bulk environment became the default environment for all accounts as of the April 9, 2024, release.

Links will remain available for users to switch between the new and classic environments, and administrators will continue to have the option to reset the default to the classic experience through their admin menu.

The classic environment will be entirely removed from the user experience by March 2025.
 


Bio-Pharma accounts - Enable improved authentication challenges for your account before September 17, 2024

First Reported: January 2024

Current 

ACTION REQUIRED

Customers who have configured their Bio-Pharma controls (at the account level or for any group within the account) should manually enable the new experience in the application through their admin menu before September 17, 2024.

All groups will automatically update and properly retain all the expected authentications as configured before the update.

The Bio-Pharma settings to enforce identity authentication were updated in the November 2023 Acrobat Sign system update and placed behind an Enable Now button to permit admins the time to review the update and elevate their account once they were comfortable with the changes. The Enable Now button is only available on the Bio-Pharma subsection of the admin menu.

The change to the enforced identity authentication settings removes the dependency between the controls, allowing admins to select any one (or more) settings as needed. Additionally, in the case of dependent controls that are checked but disabled, the checkbox is cleared to correctly reflect that the setting isn't in effect. 

f

f

Controls that are enabled will remain enabled. All agreements will continue to work as before.

Enabling the new experience through the Enable Now button updates all groups in the account and removes the callout to apply the update. The update cannot be reversed.

Starting in February 2024, accounts that have enabled the first control (Enable authentication challenges and Signing reasons) but have not enabled the improved experience will receive two in-application engagements:

  • A dialog box appears on the Home screen after logging in. This dialog box only shows to a user one time.
  • A "hotspot" graphic on the Bio-Pharma admin menu that opens a dialog box when selected. The hotspot will show up to three times until the user selects it, with a 24-hour delay between displays.

After September 16, 2024, all accounts in the Acrobat Sign service will automatically be updated to use this new interface.

אזהרה:

Customer accounts that have not manually updated their accounts will be automatically updated by the system.

System-updated accounts will not automatically clear the checked but disabled dependent controls, resulting in those controls being enabled after the update.

This will impact new agreements, prompting recipients to authenticate for the enabled control conditions.

To prevent this, manually enable the new experience and take advantage of the automated process that converts disabled settings into unchecked settings.


Adobe Acrobat Sign for SharePoint Online: Ended service as of June 28, 2024

First Reported: January 2024

Current 

Support for the Acrobat Sign for SharePoint Online integration is set to end on June 28, 2024. 

After June 28, agreements sent for signature from this integration will remain available for recipients to sign. However, the final completed documents will not be saved back into SharePoint. The final executed agreement must be downloaded manually (or through some other automation) and uploaded to your SharePoint site if you wish to save a copy in SharePoint Online.

Advanced workflow features, such as data mapping between SharePoint lists and Acrobat Sign workflow templates, will no longer be available, but the underlying data will not be affected. Completed agreements and other data previously stored on your SharePoint site or with Acrobat Sign will not be affected. 

הערה:

This end-of-service notification only applies to the SharePoint Online integration.

Other integrations that can access SharePoint Online (e.g., Microsoft Power Automate and Microsoft Teams) are not impacted.


Improved Request Signature page for embedded applications 

First Reported: November 2023

Current 

Acrobat Sign has developed a version of the new Request Signature page as a  Single Page Application (SPA) for customers that have built their own custom integrations and applications. Instead of using browser cookies for the user session, this new solution uses session access tokens to access the Acrobat Sign workflows and pages.

The SPA solution overcomes a problem where browser cookies stored in an iFrame are viewed as third-party cookies, and the trend for browsers is to disable third-party cookies by default.

Customers with embedded solutions and want to take advantage of the SPA-built Request Signature page should contact support to enable the feature.

 


Classic reporting to be removed from service in the first half of 2025

First Reported: September 2022 - Updated March 2024

Current 

Classic reporting will be completely removed from the Acrobat Sign interface in the first half of 2025. This includes the switch link that allows changing between environments. Once removed, customers will not be able to return to the classic environment to review classic reports, and scheduled reports will stop executing.

The modern reporting environment will remain as the only reporting solution.

All customers are strongly encouraged to recreate all of their existing reports in the new environment as soon as possible.


Additional Resources


Past Notifications

Acrobat Sign Technical Notice and Release-related notifications to end after the March 2024 release

First Reported: February 2024

Removed From Current List: May 2024

Adobe Acrobat Sign will no longer be sending technical updates or release communications.  Instead, please visit the Acrobat Sign User Guide, where you can find Pre-Release Notes, Release Notes, and additional resources.  We also recommend becoming a part of the Adobe Sign community to ask questions and discuss new features and topics.
 


Unsanctioned page modifications may be disabled

First Reported: February 2023

Removed From Current List: July 2024

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 that allow HTTP proxies to modify page content.


Notice to Acrobat Sign API users regarding HTTP header case insensitivity

First Reported: January 2024

Removed From Current List: July 2024

Please note that HTTP headers are case-insensitive, as specified in RFC 2616 and RFC 7230. This means the header names can be written in any combination of upper and lower case letters. However, some applications or libraries may expect a certain case for the header names, such as Pascal-Case (e.g., Content-Type) or lowercase (e.g., content-type).

Due to upcoming infrastructure updates, Adobe Sign will be changing the case of some HTTP headers. This should not affect the service's functionality, but it may require some adjustments in your code or configuration if you rely on a specific case for the header names. We recommend reviewing your code and configuration to ensure they are compatible with case-insensitive headers.

For more information about HTTP headers, refer to the following resources:


Adobe Acrobat Sign end of development for the GigaSign application 

First Reported: March 2024

Removed From Current List: July 2024

Customers using the GigaSign application are advised that there will be no further development of the application.

All customers are advised to move their existing GigaSign processes to utilize the new Send in Bulk feature, which has been improved to cover the functional differences that classic Send in Bulk did not provide. 

Archived Notifications

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

 Adobe

קבל עזרה במהירות ובקלות

משתמש חדש?

‎‎Adobe MAX 2024

Adobe MAX
כנס היצירתיות

14-16 באוקטובר, מיאמי ביץ', ובאינטרנט

Adobe MAX

כנס היצירתיות

14-16 באוקטובר, מיאמי ביץ', ובאינטרנט

‎‎Adobe MAX 2024

Adobe MAX
כנס היצירתיות

14-16 באוקטובר, מיאמי ביץ', ובאינטרנט

Adobe MAX

כנס היצירתיות

14-16 באוקטובר, מיאמי ביץ', ובאינטרנט