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 >

Prior to the March 2024 release, the Acrobat Sign API does not have the parameters to retrieve the groupID of an agreement for accounts that do not have Users in Multiple Groups enabled. In this case, the user's current groupID is used when applying a Group filter to a report.

This impacts reporting for accounts that have moved users between groups, causing discrepancies by including and excluding agreements based on the user's current group and not the group the agreement was originally related to. Additionally, any data export containing an agreement from a user that has been moved reflects the current user's group, and may misrepresent some of the agreement's actual group.

The March 2024 release adds parameters to the API structure that include the creating groupID, thereby ensuring that group filtering will apply to the original group the agreement was created in and not the group the user is currently a member of. Customers that don't have UMG enabled should be aware that agreement numbers on reports created before the March 2024 release may change based on the number of users that have been moved between groups and their total volume of agreements.

Classic reporting will be completely removed from the Acrobat Sign interface in the March 2024 release. This includes the switch link that allows changing between environments. After the March 2024 release, 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.

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.

An update to the Acrobat Sign for Veeva Vault integration will be released on November 13, 2023. Updates include:

• Veeva Vault Library Upgrade - The application has been updated to a more modern and efficient Vault API library (VAPIL) for enhanced integration.
• Veeva Vault API version Upgrade - The Veeva Vault API version has been upgraded to v23.1
• The Integration deployment package has been enhanced to ensure no requirements are imposed on customers to use the latest document version.

Adobe Acrobat Sign has re-enabled the option to define an ad hoc recipient group using the email field in the workflow designer page.

The existing method of using the Add Recipient Group button to select from a list of reusable recipient groups continues to work as an option.

Adobe Acrobat Sign will rotate the Root and Intermediate SSL Certificates on the morning of March 1st, 2024.
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 March 1st, 2024.  

The new SSL certificates will be active on March 1st, 2024.

Acrobat Sign support for Microsoft SharePoint on-premises is set to end by October 22, 2023. On that date, the integration will no longer be able to send or process agreements.

Agreements previously sent for signature from the integration will continue to be available for recipients to sign,  but the completed documents will not be saved back to SharePoint. Users will need to manually download a copy of the final executed agreement and upload it to their SharePoint site if they wish to save a copy in SharePoint.

Advanced workflow features (e.g., data mapping between SharePoint lists and Acrobat Sign workflow templates) will no longer be available. However, the underlying data will not be affected. Completed agreements and other data stored on your SharePoint instance or with Acrobat Sign will not be affected. 

It's recommended that impacted customers remove the Acrobat Sign plug-in from their SharePoint on-premise instance and replace it with other Acrobat Sign integrations, such as Adobe Acrobat Sign for Microsoft Sharepoint Online or the integration with Microsoft Power Automate.

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 NemID service has been retired and replaced by the MitID service, effective November 1, 2023.

As of November 1, NemID is no longer available as a cloud signature provider in Acrobat Sign, and customers should move to using the MitID provider.

For detailed information on the retirement of the NemID service, read the following notice (from NemID website): https://www.nemid.nu/dk-en/about_nemid/nemid_will_soon_close.html

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

With the September 2023 release, the customer interface for viewing an agreement has moved the PDF controls from under the document to the right side of the document.

Additionally, an option to view two pages has been added.

The Search option isn't included in the PDF controls at this time, but users can employ Ctrl/Cmd + F to search the document content.

The known issue regarding not being able to move signature and text fields in the drag-and-drop authoring environment when using new Chrome and Edge versions was resolved in the September 26, 2023 release. 

The impacted browser versions are:

• Chrome 
  • 116.0.5845.96
  • 116.0.5845.97
    
  • 116.0.5845.111
    
• Microsoft Edge 116.x

Current workaround options are:

• Use a different browser.
• If no other browser is available:
  • In classic authoring, select the grab handle to the left of the field to drag/drop.
  • In new authoring, select the field, then use the keyboard (Cmd + Shift + arrow keys) to move the fields.

Adobe Acrobat Sign updated to the search service on the NA2 server environment starting in the afternoon of Saturday, September 2nd, and completing the morning of Sunday, September 3rd.PST. During the upgrade, users on the NA2 shard may experience a delay in observing their latest agreement updates/additions on the Manage page.

This activity will NOT impact 

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

To maintain a strong level of security within the Adobe Acrobat Sign service, several legacy TLS ciphers that use static keys or the SHA-1 hash function will no longer be supported after July 17, 2023.

Customers using legacy ciphers should update the O/S, framework, or application code to use one of the supported TLS ciphers before July 18, 2023, to ensure uninterrupted service use.

After July 17, 2023, any application attempting to connect to an Acrobat Sign endpoint with a legacy cipher suite will fail.

Legacy cipher suites being removed from service:

Supported cipher suites:

Adobe Acrobat Sign is planning an update to the search service on the NA1 server environment during the early morning hours of Sunday, August 20^th EST. During the upgrade, users on the NA1 shard may experience a delay in observing their latest agreement updates/additions on the Manage page.

This activity will NOT impact 

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

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 May 2nd, 2023.
  
• Accounts existing before November 9th, 2022, are to be migrated to the webhook 2.0 environment per the below schedule.
  
• Accounts in the Adobe Acrobat Sign for Government environment will be updated to Webhooks 2.0 on a future (undecided) date.
  

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

In the July 2023 release, all accounts that have enabled Custom Send Workflows for their administrators will automatically be enabled with workflow designer access for all users.

Users can access the workflow designer through the Workflows tab in the top navigation bar and the Create reusable workflows tile on the Home page.

Administrators that would like to remove workflow designer access from their users can disable the feature (at the account or group level) by navigating to Account Settings > Global Settings > Custom Send Workflows.

Throttling is being applied to REST /search API calls - All /search API calls are subject to volume throttling at the rate of:

• No more than 1000 calls per minute.
• No more than 2500 calls per hour.
• No more than 7200 calls per day.

Throttling will begin after the July 18th release is completed.

Administrators should file a support request to elevate the volumes if needed.

The Acrobat Sign release scheduled for May 2023 included availability of the Microsoft Power Automate integration for all accounts with an enterprise license.

Access to discover this feature via the Workflows tab and Home page access points is enabled by default for all users. 

Using these access points, users are able to discover the value of Power Automate, and request access to the integration from their administrators.   

Controls to disable user discoverability can be found in Account Settings > Global Settings.

The Acrobat Sign release scheduled for May 2023 included availability of the Microsoft Power Automate integration for all accounts with an enterprise license.

Access to discover this feature via the Workflows tab and Home page access points is enabled by default for all users. 

Using these access points, users are able to discover the value of Power Automate, and request access to the integration from their administrators.   

Archived Notifications

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

Archive of Technical Notifications 2023

Archive of Technical Notifications 2021 - 2022

Archive of Technical Notifications 2019 - 2020

Archive of Technical Notifications 2017 - 2018

Archive of Technical Notifications 2015 - 2016