İçindekiler
Yenilikler
Başlayın
- Yöneticiler için hızlı başlangıç kılavuzu
- Kullanıcılar için hızlı başlangıç kılavuzu
- Geliştiriciler için
- Video eğitim kitaplığı
- SSS
Yönetim
- Admin Console'a Genel Bakış
- Kullanıcı Yönetimi
- Kullanıcı ekleme
- Fonksiyon odaklı kullanıcılar oluşturma
- Sağlama hataları olan kullanıcıları kontrol etme
- Ad/E-posta Adresi Değiştirme
- Kullanıcının grup üyeliğini düzenleme
- Bir kullanıcının grup üyeliğini grup arayüzü üzerinden düzenleme
- Bir kullanıcıyı yönetici rolüne yükseltme
- Kullanıcı Kimlik Türleri ve SSO
- Kullanıcı Kimliğini Değiştirme
- Kullanıcıların Kimliğini MS Azure ile Doğrulama
- Kullanıcıların Kimliğini Google Federation ile Doğrulama
- Ürün Profilleri
- Oturum Açma Deneyimi
- Hesap/Grup Ayarları
- Ayarlara Genel Bakış
- Global Ayarlar
- Hesap düzeyi ve kimliği
- Yeni Alıcı Deneyimi
- Kendi Kendine İmzalı İş Akışları
- Toplu Halde Gönder
- Web Formları
- Özel Gönderme İş Akışları
- Power Automate İş Akışları
- Kitaplık Belgeleri
- Sözleşmelerle form verileri toplama
- Sınırlı Belge Görünürlüğü
- İmzalanan sözleşmenin PDF kopyasını ekleme
- E-postaya bağlantı ekleme
- E-postaya görüntü ekleme
- E-postalara eklenen dosyalar şu şekilde adlandırılır:
- Belgelere denetim raporu ekleme
- Birden çok belgeyi tek bir belgede birleştirme
- Belgeleri ayrı ayrı indirme
- İmzalanan belgeyi yükleme
- Hesabımdaki kullanıcılar için delegasyon
- Harici alıcıların delege etmesine izin verme
- İmzalama yetkisi
- Gönderme yetkisi
- Elektronik Mühür ekleme yetkisi
- Varsayılan saat dilimini ayarlama
- Varsayılan tarih formatını ayarlama
- Birden Çok Gruptaki Kullanıcılar (UMG)
- Grup Yöneticisi İzinleri
- Alıcıyı değiştirme
- Denetim Raporu
- İşlem Altbilgisi
- Ürün İçi Mesajlar ve Rehberlik
- Erişilebilir PDF'ler
- Yeni içerik oluşturma deneyimi
- Sağlık müşterisi
- Hesap Ayarları
- İmza Tercihleri
- İyi biçimlendirilmiş imzalar
- Alıcıların imza eklemesine izin verme
- İmzalayanlar adlarını değiştirebilir
- Alıcıların kayıtlı imzalarını kullanmasına izin verme
- Özel Kullanım Koşulları ve Tüketici Açıklaması
- Alıcıları form alanlarında gezindirme
- Sözleşme iş akışını yeniden başlatma
- İmzalamayı reddetme
- Zaman Dalgaları iş akışlarına izin verme
- İmzalayanlardan Unvanlarını veya Şirketlerini sağlamalarını isteme
- İmzalayanların ıslak imza yazdırmasına ve yerleştirmesine izin verme
- E-imzalama sırasında mesajları gösterme
- İmzalayanlardan imzalarını oluştururken mobil cihaz kullanmalarını isteme
- İmzalayanlardan IP adresi isteme
- Katılım damgasında şirket adını ve unvanı hariç tutma
- Dijital İmzalar
- Elektronik Mühürler
- Dijital Kimlik
- Rapor Ayarları
- Yeni rapor deneyimi
- Klasik rapor ayarları
- Güvenlik Ayarları
- Tekli Oturum Açma ayarları
- Beni Hatırla ayarları
- Oturum açma parola politikası
- Oturum açma parolası kuvveti
- Web oturumu süresi
- PDF şifreleme türü
- API
- Kullanıcı ve grup bilgileri erişimi
- İzin Verilen IP Aralıkları
- Hesap Paylaşımı
- Hesap paylaşım izinleri
- Sözleşme paylaşma denetimleri
- İmzalayan kimliği doğrulama
- Sözleşme imzalama parolası
- Belge parolası güvenlik düzeyi
- Coğrafi konuma göre imzalayanları engelleme
- Telefonla Kimlik Doğrulama
- Bilgi Tabanlı Kimlik Doğrulama (KBA)
- Sayfa çıkarmaya izin verme
- Belge bağlantısı kullanım süresi
- Web kancaları/geri çağırmalar için istemci sertifikası yükleme
- Zaman damgası
- Gönderim ayarları
- Oturum açtıktan sonra Gönder sayfasını gösterme
- Gönderimde alıcı adını zorunlu kılma
- Bilinen kullanıcılar için ad değerlerini kilitleme
- İzin verilen alıcı rolleri
- E-şahitlere izin verme
- Alıcı grupları
- CC alıcılar
- Alıcı Sözleşme Erişimi
- Gerekli alanlar
- Belge ekleme
- Alan düzleştirme
- Sözleşmelerde Değişiklik Yapma
- Sözleşme adı
- Diller
- Özel mesajlar
- İzin verilen imza türleri
- Hatırlatıcılar
- İmzalanan belge parola koruması
- Sözleşme Bildirimi'ni gönderme yolları
- İmzalayan tanımlama seçenekleri
- İçerik Koruması
- Noter işlemlerini etkinleştirme
- Belge Sona Erme Tarihi
- İmzaları önizleme, yerleştirme ve alan ekleme
- İmzalama sırası
- Liquid mode
- Özel iş akışı kontrolleri
- E-imza sayfası için yükleme seçenekleri
- İmza sonrası onay URL'sini yeniden yönlendirme
- Mesaj Şablonları
- Bio-Pharma Ayarları
- İş Akışı Entegrasyonu
- Noter Onayı Ayarları
- Ödeme Entegrasyonu
- İmzalayan Mesajları
- SAML Ayarları
- SAML Yapılandırması
- Microsoft Active Directory Federation Service'i yükleme
- Okta'yı yükleme
- OneLogin'i yükleme
- Oracle Identity Federation'ı yükleme
- SAML Yapılandırması
- Veri Yönetimi
- Zaman Damgası Ayarları
- Harici Arşiv
- Hesap Dilleri
- E-posta Ayarları
- echosign.com'dan adobesign.com'a geçiş
- Alıcılar için Seçenekleri Yapılandırma
- Yasal gereklilikler kılavuzu
- Erişilebilirlik
- HIPAA
- GDPR
- 21 CFR bölüm 11 ve EudraLex Ek 11
- Sağlık müşterileri
- IVES desteği
- Sözleşmeleri "Kasaya Alma"
- AB/İngiltere ile ilgili hususlar
- Sözleşmeleri Toplu Halde İndirme
- Etki alanı talep etme
- Kötüye Kullanım Bildirme bağlantıları
Sözleşmeleri Gönderme, İmzalama ve Yönetme
- Alıcı Seçenekleri
- E-posta hatırlatıcısını iptal etme
- E-imza sayfasındaki seçenekler
- E-imza sayfasına genel bakış
- Sözleşmeyi alan olmadan okumak için açma
- Sözleşme imzalamayı reddetme
- İmzalama yetkisi delege etme
- Sözleşmeyi yeniden başlatma
- Sözleşmenin PDF'sini indirme
- Sözleşme geçmişini görüntüleme
- Sözleşme mesajlarını görüntüleme
- Elektronik imzayı yazılı imzaya dönüştürme
- Yazılı imzadan elektronik imzaya dönüştürme
- Form alanları arasında gezinme
- Form alanlarından verileri temizleme
- E-imza sayfasını büyütme ve sayfada gezinme
- Sözleşme araçlarında ve bilgilerinde kullanılan dili değiştirme
- Yasal Uyarıları inceleme
- Acrobat Sign Çerez Tercihlerini Ayarlama
- Sözleşme Gönderme
- Belgelerde alan oluşturma
- Uygulama içi içerik oluşturma ortamı
- Otomatik alanı algılama
- İçerik oluşturma ortamını kullanarak alanları sürükleyip bırakma
- Form alanlarını alıcılara atama
- Önceden Doldurma rolü
- Alanları yeniden kullanılabilir alan şablonuyla uygulama
- Alanları yeni bir kitaplık şablonuna taşıma
- Sözleşme gönderme işlemleri için güncellenmiş içerik oluşturma ortamı
- Metin etiketli formlar oluşturma
- Acrobat ile formlar oluşturma (AcroForms)
- Alanlar
- İçerik Oluşturma Hakkında SSS
- Uygulama içi içerik oluşturma ortamı
- Sözleşmeleri İmzalama
- Sözleşmeleri Yönetme
- Yönet sayfasına genel bakış
- Sözleşmeleri delege etme
- Alıcıları Değiştirme
- Belge Görünürlüğünü Sınırlama
- Sözleşmeyi İptal Etme
- Yeni hatırlatıcılar oluşturma
- Hatırlatıcıları inceleme
- Hatırlatıcıyı iptal etme
- Power Automate akışlarına erişme
- Daha Fazla Eylem...
- Arama nasıl çalışır?
- Sözleşmeyi görüntüleme
- Sözleşmeden şablon oluşturma
- Sözleşmeleri görünümden gizleme/gösterme
- İmzalanan sözleşmeyi yükleme
- Gönderilmiş bir sözleşmenin dosyalarını veya alanlarını değiştirme
- Alıcının kimlik doğrulama yöntemini düzenleme
- Sona erme tarihi ekleme veya değiştirme
- Sözleşmeye not ekleme
- Tekil sözleşme paylaşma
- Sözleşmenin paylaşımını kaldırma
- Bireysel sözleşme indirme
- Sözleşmenin dosyalarını ayrı ayrı indirme
- Sözleşmenin Denetim Raporunu indirme
- Sözleşmenin alan içeriğini indirme
- Denetim Raporu
- Rapor ve Veri dışa aktarımları
- Genel bakış
- Raporlara kullanıcı erişimi verme
- Rapor çizelgeleri
- Veri Dışa Aktarımları
- Raporları/dışa aktarımları yeniden adlandırma
- Raporları/dışa aktarımları yineleme
- Rapor/dışa aktarım planlama
- Raporları/dışa aktarımları silme
- İşlem Kullanımını kontrol etme
Gelişmiş Sözleşme Özellikleri ve İş Akışları
- Web formları
- Yeniden Kullanılabilir Şablonlar (Şablon kitaplıkları)
- Acrobat Sign kitaplığındaki ABD resmi formları
- Kitaplık şablonu oluşturma
- Kitaplık şablonunun adını değiştirme
- Kitaplık şablonunun türünü değiştirme
- Kitaplık şablonunun izin düzeyini değiştirme
- Paylaşılan şablonları kopyalama, düzenleme ve kaydetme
- Kitaplık şablonları için toplu alan verilerini indirme
- Web formlarının ve kitaplık şablonlarının sahipliğini aktarma
- Power Automate İş Akışları
- Power Automate entegrasyonuna ve içerdiği yetkilere genel bakış
- Power Automate entegrasyonunu etkinleştirme
- Yönet sayfasındaki Bağlam İçi Eylemler
- Power Automate kullanımını takip etme
- Yeni akış oluşturma (Örnekler)
- Akışlarda kullanılan tetikleyiciler
- Acrobat Sign dışındaki akışları içe aktarma
- Akışları yönetme
- Akışları düzenleme
- Akışları paylaşma
- Akışları devre dışı bırakma veya etkinleştirme
- Akışları silme
- Faydalı Şablonlar
- Yalnızca yönetici
- Sözleşmeleri arşivleme
- Web formu sözleşmelerini arşivleme
- Tamamlanan web formu belgelerini SharePoint Kitaplığına kaydetme
- Tamamlanan web formu belgelerini OneDrive for Business'a kaydetme
- Tamamlanan belgeleri Google Drive'a kaydetme
- Tamamlanan web formu belgelerini Box'a kaydetme
- Sözleşme verilerini ayıklama
- Sözleşme bildirimleri
- Sözleşme içeriği ve imzalanan sözleşmeyle birlikte özel e-posta bildirimleri gönderme
- Adobe Acrobat Sign bildirimlerinizi Teams kanalında alma
- Adobe Acrobat Sign bildirimlerini Slack'e alma
- Adobe Acrobat Sign bildirimlerini Webex'e alma
- Sözleşme oluşturma
- Power App formundan ve Word şablonundan belge oluşturma ve imzaya gönderme
- OneDrive'da Word şablonundan sözleşme oluşturma ve imza alma
- Seçilen Excel satırı için sözleşme oluşturma, incelemeye ve imzaya gönderme
- Özel Gönderme iş akışları
- Kullanıcıları ve sözleşmeleri paylaşma
Diğer ürünlerle entegrasyon
- Acrobat Sign entegrasyonlarına genel bakış
- Salesforce için Acrobat Sign
- Microsoft için Acrobat Sign
- Diğer Entegrasyonlar
- İş ortağı tarafından yönetilen entegrasyonlar
- Entegrasyon anahtarı alma
Acrobat Sign Developer
- REST API'leri
- Web Kancaları
Destek ve Sorun Giderme
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 February 11, 2025
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.
Feature Release: Adobe Acrobat Sign – November 12th Release Completed
The release was completed to all shards with no downtime to any services.
First Reported: December 2024 |
Current |
---|
Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.
In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025. This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.
Action Required
- Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
- 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 other 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 SSL 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 January switch.
- If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.
The new SSL certificates will be active on January 22, 2025.
First Reported: September 2024 - Updated January 2025 |
Current |
---|
To improve Adobe Acrobat Sign service security and robustness, we will roll out network changes to include a web application firewall (WAF) in the first half of 2025 (final dates to be determined; Bookmark this notice!). These changes will route traffic into Acrobat Sign application servers through the WAF 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 outbound connections with the previously documented Acrobat Sign API ingress addresses will need to remove those legacy allow-listings before the WAF implementation.
-
Ingress vs. Egress Access to Acrobat Sign
Acrobat Sign will no longer publish or support a list of server ingress IP addresses as such usage isn't compatible with the WAF network. The server egress IP addresses, used by webhooks and email relays, will continue as documented on the System Requirements for Acrobat Sign page.
-
Why is Acrobat Sign making these Changes?
The use of a WAF 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 WAF 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 WAF network. The respective network filters, for example on firewalls, must be removed before the WAF installation.If these legacy IP network restrictions are not removed before this change goes into effect, connectivity to Acrobat Sign will stop working.
Not:Note that this refers to IP-level filtering for the environment hosting your application. Domain-level filtering is not affected.
-
I'm using the Salesforce integration with explicitly configured IP allow-listing. Do I need to do anything?
No.
The WAF installation requires no changes for existing Salesforce installations at this time.
The existing configuration/process, as described in the help documentation, remains the same, and administrators should follow all IP allow-listing steps.
ISV and Embed Partners should contact their Success Manager for any further questions.
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: November 2024 - Updated: December 2024 |
Current |
---|
Senders can provide an additional view of agreements for mobile recipients that lists only the field within the agreement available to the recipient.
Senders can arrange the field list as they like, and group fields into logical sections to help the signers move through the field input with a minimum of scrolling.
Recipients have the option to view the mobile-friendly fields list or the original PDF view with the fields placed within the document content.
This feature is scheduled to be released:
- To be deployed on the Sandbox environment on December 11, 2024
- To be deployed on the Production environment on January 7, 2025
First Reported: December 2024 |
Current |
---|
Adobe Acrobat Sign rotated the Public key (for *.adobesign.com and *.echosign.com), Root, and Intermediate SSL Certificates on the morning of February 1, 2024.
There is no change to the underlying cryptographic protocols or schemes.
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 Root and Intermediate certificates in the Adobe Acrobat Sign System Requirements. The Public Key will be available on February 1, 2024.
- 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 February 1, 2024.
The new SSL certificates will be active on February 1, 2024.
First Reported: November 2024 |
Current |
---|
The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.
First Reported: November 2024 |
Current |
---|
With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.
Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.
New workflows will warn about the label limit before they are saved.
Action Required
It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.
First Reported: September 2024 |
Current |
---|
The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads when the March 2025 release is deployed.
The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.
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: 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.
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
First Reported: March 2024 - Updated November 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 commercial user experience by April 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.
As part of the April 2025 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: 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: 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: 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
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: August 2024 |
Removed From Current List: November 2024 |
---|
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: August 2024 |
Removed From Current List: November 2024 |
---|
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.
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: November 2023 |
Removed From Current List: November 2024 |
---|
First Reported: September 2024 |
Removed From Current List: November 2024 |
---|
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: July 2024 |
Removed From Current List: November 2024 |
---|
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.
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.