What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
Support and Troubleshooting
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 November 12, 2024
The Sandbox deployment for the November 2024 release has been delayed until October 22, 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 – September 17th Release Completed
The release was completed to all shards with no downtime to any services.
First Reported: September 2024 |
Current |
---|
To improve Adobe Acrobat Sign service security and robustness, we will roll out network changes beginning the week of January 13, 2025. These changes will route traffic into Acrobat Sign application servers through the Akamai content network. This routing will be invisible to most customers. Usage will not interfere with access to Acrobat Sign from any Adobe clients or integrations.
Action Required
In most cases, this change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. However, the underlying IP addresses for the Acrobat Sign API endpoints will shift.
Integrations written to explicitly allow-list the previously documented Acrobat Sign API ingress addresses will need to remove those legacy allow-listings by January 13, 2025.
-
Ingress vs. Egress Access to Acrobat Sign
Acrobat Sign provides ingress endpoints for API requests to Acrobat Sign and egress endpoints for webhook callbacks to customer applications and email delivery.
Only the ingress traffic is affected by this change. There are no changes to egress traffic. -
Why is Acrobat Sign making these Changes?
The use of the Akamai content network improves Acrobat Sign's protection against harmful traffic and helps us better address security, robustness, and compliance requirements.
-
I have a custom integration into Acrobat Sign. Will my application be affected?
In most cases, no, but it depends on how your application is written.
Typically, applications depend only on the Acrobat Sign service domain names (e.g., "api.na1.adobesign.com"), and these names will continue to work. Less commonly, an application will take the additional step of allow-listing the specific IP address that this name resolves to.
Such allow-listing is more commonly seen when developing a webhook endpoint to verify that the webhook request is coming from a valid Acrobat Sign server. Webhook IP addresses are not affected by this change.
Less commonly, an application initiating a request to an Acrobat Sign endpoint will validate the IP address against an allow-list. Such validation logic must be removed, or the application will fail.
As a standard best practice, the application should perform server certificate validation of the Acrobat Sign endpoint when initiating the TLS connection. This provides strong assurance that the request is going to a valid Acrobat Sign endpoint. Most HTTP/S frameworks and libraries perform server certificate validation by default.
-
Are there new IP address lists that can be substituted?
Acrobat Sign will no longer publish or support a list of server ingress IP addresses as such usage isn't compatible with the Akamai network. The server egress IP addresses, used by webhooks and email relays, will continue as documented on the System Requirements for Acrobat Sign page.
-
My organization has implemented network filtering using Acrobat Sign's published domain list for traffic from our corporate network. Are we affected?
No.
The network changes described here do not impact Acrobat Sign's domain list, as documented on the System Requirements for Acrobat Sign page. Domain-level filtering is unaffected. -
My organization employs IP address validation for email delivery from Acrobat Sign servers. Are we affected?
No.
The IP ranges for outbound mail relays, as listed on the System Requirements for Acrobat Sign page, are not changing. -
My organization has configured our Acrobat Sign account to restrict access to our own IP addresses. Are we affected?
No.
Acrobat Sign can be configured to validate incoming traffic against customer-chosen IP addresses, as described on the Restrict access to your account using IP address ranges page. Such usage will not be affected by this change. -
My organization has implemented network filtering using Acrobat Sign's published list of ingress IP addresses. Are we affected?
Yes.
Acrobat Sign will no longer publish or support a list of server ingress IP addresses as such usage isn't compatible with the Akamai network. The respective network filters, for example on firewalls, must be removed by January 13, 2025.If these legacy IP network restrictions are not removed before this change goes into effect, connectivity to Acrobat Sign will stop working.
Note:Note that this refers to IP-level filtering for the environment hosting your application. Domain-level filtering is not affected.
First Reported: August 2024 |
Current |
---|
Action Required
Customers who maintain network security practices that explicitly list inbound IP addresses must update the IP ranges for the Acrobat Sign service by the end of September 2024.
The complete list of IP ranges is published on the system requirements page.
To ensure the continued seamless function of your callbacks and webhook notifications, the IP ranges below must be added to the allow list for all customer accounts in the EU2 data center.
The added IP ranges are:
- 4.207.3.96/28
- 4.207.4.160/28
- 4.208.75.176/28
- 4.208.75.80/28
- 4.208.79.192/28
- 4.208.79.208/28
- 4.245.45.176/28
- 4.245.45.192/28
- 4.245.45.208/28
- 4.245.45.224/28
- 4.245.45.240/28
- 4.245.46.128/28
- 4.245.85.80/28
- 20.23.101.224/28
- 20.31.209.192/28
- 20.31.209.240/28
- 20.31.210.16/28
- 20.31.210.48/28
- 20.105.66.176/28
- 20.166.106.144/28
- 20.166.107.112/28
- 20.166.107.240/28
- 20.166.107.32/28
- 40.127.244.64/28
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 |
|
February 1, 2024 (Completed) |
|
April 1, 2024 (Completed) |
|
The scheduled date has been moved up to July 1, 2024, replacing the previous date of December 1, 2024. |
|
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.
First Reported: September 2024 |
Current |
---|
Action Required
All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability.
Versions 1 through 4 of the Acrobat Sign REST API have been deprecated and will be removed from service on December 1, 2025.
Updating APIs can involve considerable effort, so all customers are strongly encouraged to scope and budget their update as soon as possible so that support can be fully engaged to resolve any questions or problems that arise before the December 2025 cutoff date.
While REST API v1-4 are deprecated, they will continue to function, and your applications will continue to work until December 1, 2025, when the REST API v1-4 will be removed.
After December 1, 2025, applications built on the REST API v1-4 will cease functioning.
First Reported: September 2024 |
Current |
---|
First Reported: September 2024 |
Current |
---|
The autocompletion feature that generates a list of email addresses when entering a recipient into any email field has traditionally only matched strings from the beginning of the address.
The API that drives that autocomplete functionality has been updated to support "tokenizing" the email, allowing for each token to match individually to the searched for string.
Tokenizing is the process where the email address is broken into smaller strings (tokens) based on common delimiters. Characters treated as delimiters (other than whitespace) are: ~ ` ! @ # $ % ^ & * ( ) - + = { } [ ] | \ . , : ; " ' < > ? /
First Reported: August 2024 |
Current |
---|
The legacy Accept-Charset header will be removed from all Webhook and Callback notifications with the November 2024 release.
All customers that rely on this header for any reason should refactor their code to account for it's absence.
First Reported: July 2024 |
Current |
---|
This notification applies only to Acrobat Sign commercial enterprise administrators who have yet to migrate their users to an Adobe VIP, VIP Custom, or ETLA console.
- If your Acrobat Sign contract expires before September 17, 2024, you may disregard this notification.
- Customer accounts in the Government Cloud environment are not impacted.
Starting September 17, 2024, you'll see a new workflow to contact Adobe Acrobat Sign Support. Here is a high-level overview of the workflow:
- Log in to your Acrobat Sign account as an administrator.
- Select the "Contact Support" option under the question mark in the upper right of the window.
- You will be redirected to a new page with three channels to contact Support. Please select one of the three channels to get help with your issue:
- Web form: For priority 2 and lower issues, you may submit a support request through the web form and expect a response in one business day.
- Phone: For priority one critical issues, please call us so we can serve you immediately.
- Chat: Get in touch with our experts in real-time.
If you have an unresolved ticket with Support beyond September 17, 2024, your ticket history and conversation will be moved to a new system by the assigned support agent, who will confirm the move before and after. Future communications between you and Support regarding the unresolved issue will happen on the new system.
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.
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.
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.
- Dropbox: https://www.dropbox.com/desktop
- Google Drive: https://support.google.com/drive/answer/10838124
- Box: https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync
- Acrobat/Document Cloud: https://www.adobe.com/acrobat/hub/share-sync-pdfs.html
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.
First Reported: November 2023 |
Current |
---|
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.
First Reported: August 2024 |
Current |
---|
The new IRS I-9 and W-9 forms, entitled I-9 (Employment Eligibility Verification) Exp 5/31/27 and W-9 (Request for Taxpayer Identification Number) Rev 3/24, respectively, are scheduled to be added to the Acrobat Sign library with the September 17, 2024 release.
ACTION REQUIRED
The new library templates have new libraryDocumentIds. If you use either existing template’s libraryDocumentId in your applications, you'll need to update it.
The 2023 versions are scheduled to be removed from the system with the November 12, 2024 release.
Any application/API using the legacy (ver 2023) templates must be updated before November 8, 2024 to ensure no disruption to successful service.
To find the libraryDocumentId in an API-enabled account:
- Log in as an Account Admin
- Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
- In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button
- Enable the library_read:self scope
- Click the Try it out! button
- In the Response Body, locate the new I-9 ( Employment Eligibility Verification) Exp 5/31/27 or W-9 (Request for Taxpayer Identification Number) Rev 3/24 form template (not ver. 2023) to see the libraryDocumentId value.
First Reported: July 2024 |
Current |
---|
Emails sent through the Acrobat Sign Custom Email Template service will be temporarily delayed on September 13, 2024, starting at 7 am Pacific Time to undergo system maintenance.
All emails will be sent once the maintenance is completed.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
First Reported: June 2024 - Updated September 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 6, 2024, starting at 5 pm Pacific Time.
Delayed notifications will be delivered after the update is completed.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
This maintenance will not impact regular sending and signing activities.
First Reported: June 2024 - Updated July 2024 |
Current |
---|
The Acrobat Sign Sandbox will be temporarily unavailable on August 8, 2024, starting at 8 pm Pacific Time 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.
First Reported: June 2024 - Updated July 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 9, 2024, starting at 7 am Pacific Time.
Impacted users can try again at the end of the maintenance activity.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
First Reported: June 2024 - Updated July 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 12, 2024, starting at 7 am Pacific Time.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
This maintenance will not impact regular sending and signing activities.
First Reported: June 2024 - Updated July 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 14, 2024, starting at 7 am Pacific Time.
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.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
This maintenance will not impact regular sending and signing activities.
First Reported: June 2024 - Updated July 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, starting at 7 am Pacific Time.
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.
The impacted environments are NA3, EU2, SG1, and the Sandbox.
The total downtime is expected to be roughly 20 minutes.
This maintenance will not impact the regular sending of individual agreements and signing activities.
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.
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.
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
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.
First Reported: January 2024 |
Removed From Current List: July 2024 |
---|
ACTION REQUIRED
Administrators of organizations that use the integration are advised to remove the Acrobat Sign plug-in from the SharePoint site and transition workflows to other applications such as Microsoft Power Automate and Microsoft Teams:
- Request signature for a SharePoint file via Acrobat Sign for Power Automate
- Request signature for a SharePoint list item via Acrobat Sign for Power Automate
- Save a completed Acrobat Sign agreement to SharePoint
- Create Power Automate flows using form field data and update a SharePoint list
- Request signature for a SharePoint file via Acrobat Sign for Microsoft Teams
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.
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.
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:
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.