Adobe Sign Technical Notifications 2017-2018

Technical Notifications for 2017 - 2018

Default full screen mode for Adobe Sign UI

In order to improve the experience on smaller devices and provide a better reading experience on the desktop, the Adobe Sign March release introduced a more flexible Sign UX based on the width of the browser. 

This was enabled selectively for enterprise accounts and generally for all individual and team accounts. 

In July this became the default configuration.  Users will see the web UI adapted to the width of the page and stack components instead of shrinking them to fit a narrow width.

Action Required

No action is needed to take advantage of this new capability however this can be disabled by an account admin by navigating to the Account > Global Settings > Adobe Sign Page Presentation setting and unchecking the box. 

As part of the September release the ability to disable this feature was removed from the application and the more flexible UX became standard.

New Release: Adobe Sign September 2018

The Adobe Sign September 2018 product release is scheduled for early September.

This product release includes new features and feature enhancements for administrators and end users. No impact to the service is expected with this release. 

Adobe Sign is now supports Aadhaar E-KYC API v2.1

Aadhaar signing workflow in Adobe Sign has now moved to the latest E-KYC (electronic know your customer) API specifications. This was done to comply with new regulatory changes that mandate v2.1. Signers can now sign an agreement using their Virtual ID (VID). This update also improves the signer’s experience and fixes the Internet Explorer 11 problems reported earlier.

Adobe Sign achieves FedRAMP Tailored certification

Adobe Sign is now authorized by the GSA (Government Services Administration of the US) as meeting the requirements of Federal Risk Authorization Management Program (FedRAMP) Tailored, allowing Adobe Sign to be sold and used by non-defense US federal government agencies. 

This certificate means Adobe Sign has been reviewed by the GSA security assessor and has been approved for use at the Li-SaaS In Process level.  Adobe Sign will continue to undergo the constant monitoring required to maintain its status as a certified government cloud service provider. 

You can read more about FedRAMP at https://www.fedramp.gov/

Adobe Sign is focused on promoting data privacy regulations

Adobe Sign will comply with the European Union General Data Protection Regulation (GDPR). 

This privacy law affects all companies that collect personal information from individuals that are citizens of the EU.  Adobe Sign adheres to the rule to collect the minimum amount of information needed to conduct business during the signing process. 

All participants in Adobe Sign can access and modify their personal information through their user profile and by examining the agreements that they’ve signed. 

Adobe Sign customers that engage with consumers will have the ability to provide information to their customers about what was collected and remove that data according to their business processes. You can read about the new GDPR features of Adobe Sign.

You can read about Adobe rules and regulations that protect privacy by design across all products here: https://www.adobe.com/privacy.html.

Adobe has begun to auto-expire agreements that are still unsigned and older than 1 year old

Starting in October 2018, Adobe Sign has begun to expire agreements that are over 1 year old, and are still in the Waiting For Signature state.

Notifications will not be sent to participants of these agreements but they will be able to see them in their Manage page under the Canceled/Declined list.

ACTION REQUIRED

Customers can review their older agreements through the Manage page or by creating a report of agreements older than 1 year and downloading the report.  The filter in both cases is the “Out for Signature” status. 

This new rule applies only to non-terminal agreements.

Agreements that have completed or were canceled or declined will not be impacted.

Integration: Adobe Sign for Salesforce v20 released in July 2018

The Adobe Sign for Salesforce Summer Release 2018 (previously referred to as "Spring Release") was released on July 17^th 2018.

The Summer Release includes new features and feature enhancements for administrators and end users. The update will be available on Adobe Sign’s Salesforce AppExchange listing. 

Read the release notes here.

Insecure traffic blocked

On June 20th 2018, we ended support for several categories of insecure network traffic for Adobe Sign. This was required to meet specific requirements for PCI compliance.

Inbound traffic, or connections made from a client to our servers.

We stopped supporting unencrypted connections to our APIs -- that is, requests that use "http:" rather than "https:".

With this change, customer and partner applications will fail on attempts to establish unencrypted connections.

• The error behavior will be application-specific.

Outbound traffic, or connections made from our servers back to customer-specified servers.

There are two categories:

• Upload callbacks for document uploads (described here for our REST API, but also applies to the legacy SOAP API)
• Status callbacks to notify the customer of a change in agreement status (described here for our REST API, but also applies to the legacy SOAP API)

For both categories of callbacks, we stopped supporting:

• Unencrypted connections (using "http:" rather than "https:" URLs)
• Connections to servers that do not support TLSv1.2 (in other words, TLSv1.0 and TLSv1.1 will no longer be supported)
• Connections to servers that have invalid certificates. This includes certificates that are self-signed or expired, as well as cases in which a URL uses an IP address rather than a hostname.

New Release: Adobe Sign June 2018

The Adobe Sign June 2018 product release was completed on June 11^th.

The June 2018 product release includes new features and feature enhancements for administrators and end users. You can find the release notes here.

New SSL Certificate

Adobe Sign moved to a new SSL Certificate on May 2, 2018. There is no change to the public key, underlying cryptographic protocols or scheme. Please contact Customer Support with questions.

ACTION REQUIRED

If you have custom built integrations with Adobe 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’re pinning the certificate using other methods, you can find the new Adobe Sign certificates in the Adobe Sign System Requirements. The new SSL certificate became active on May 2, 2018.

Important changes to IP address ranges

If your existing network or firewall configuration explicitly lists the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration.

ACTION REQUIRED

If you explicitly allow Adobe Sign IP addresses in either your API Callbacks or firewall, you must allow the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable.

If you use the Adobe Sign for Salesforce integration, admins must allow the additional IP address ranges in their Salesforce.com account (including Sites).

ADD:

• 40.67.155.147/32
• 40.67.154.249/32
• 40.67.155.185/32
• 40.67.155.112/32

If you are allowing the IP ranges for outbound email relays, add:

• 40.67.157.141/32
• 40.67.154.24/32
• 40.67.158.131/32

Integration: Adobe Sign for Dynamics v7 release

The Adobe Sign for Dynamics 365 CRM Summer Release 2018 (v7) is scheduled for mid-June.

This release goes deeper with Microsoft Dynamics 365 CRM with a redesigned UI for quick navigation, and adds customer contact details from LinkedIn so you can always “see” who you’re sending to.  In addition, customers can now completely automate their Adobe Sign processes by embedding Adobe Sign directly into Microsoft Dynamics 365 CRM workflows.

The update is available on Adobe Sign’s Microsoft AppSource listing.  No impact to the service is expected with this release.

Integration: Action required for Adobe Sign for Salesforce v19.x customers

If you are running Adobe Sign for Salesforce version 19.x, you must upgrade to version 19.5.2 either before June 1, 2018 or June 8, 2018, depending on your Salesforce.com organization. The Salesforce Summer ’18 release, being progressively rolled out in June by Salesforce, has changes which affect backwards compatibility with the Adobe Sign for Salesforce integration and will impact the ability to send some agreements.

Starting June 1, 2018, customers running Adobe Sign for Salesforce version 19.x who are upgraded to Salesforce Summer ’18 will be unable to add recipients and send agreements on the Lightning version of the Send page*.

ACTION REQUIRED

If you are running v19.x, upgrade to Adobe Sign for Salesforce v19.5.2 before Salesforce upgrades your org to Salesforce Summer ’18:

• Go to the AppExchange, click Get It Now and follow the instructions. 

If you need help with upgrading, please refer to our Adobe Sign for Salesforce (v19) Upgrade Guide.

New SSL Certificate

Adobe Sign is moving to a new SSL Certificate on May 2, 2018. There is no change to the public key, underlying cryptographic protocols or scheme. Please contact Customer Support with questions.

ACTION REQUIRED

If you have custom built integrations with Adobe Sign using either the SOAP or REST APIs, and if any of these integrations has ‘pinned’ the existing public key, no action is required.

If you’re pinning the certificate using other methods, you can find the new Adobe Sign certificates in the Adobe Sign System Requirements. The new SSL certificate becomes active on May 2, 2018.

Adobe Sign March release complete

The Adobe Sign March 2018 product release was completed 12:00pm PST, March 15, 2018.

For more details, review the full release notes.

SAP SuccessFactors will be released in April.

2017 version of the W-4 US tax form to be removed from service 4/17/18

The 2017 version of the W-4 US Tax form template will be removed from the Adobe Sign library on April 17^th, 2018.

Customers that are using the W-4 from the Adobe Sign library via API should update their document ID to the 2018 version (See below)

If you need more information, please contact your Customer Success Manager.

2018 version of the W-4 US tax form is available

On 3/13/18, a new template for the IRS W-4 form was added to Adobe Sign. It is entitled W-4 2018 (Employee’s Withholding Allowance Certificate)

ACTION REQUIRED

The new W-4 form template has a new libraryDocumentId . If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN  button 

a . Enable the library_read : self   scope

4    Click the Try it out! button

5. In the Response Body, locate the new W-4 form template (not the 2017 version) to see the libraryDocumentId value. 

If you need more information, please contact your Customer Success Manager.

In the Response Body, locate the new W-4 form template (not the 2017 version) to see the libraryDocumentId value. 

If you need more information, please contact your Customer Success Manager.

Security Notice: Support of TLS 1.0 and 1.1 ends April 9 2018

Adobe will be removing support for TLS 1.0 and 1.1 protocols in 2018 to meet industry best practices for SSL/TLS security.

On April 8th, the SSL handshake protocol TLS 1.2 will be required, and the older TLS 1.0 and TLS 1.1 protocols will no longer be accepted. Clients that do not use TLS 1.2 will be unable to make network connections to the Adobe Sign service.

ACTION REQUIRED

For clients running web browsers: Use a supported browser (see System requirements).

For clients running applications using Adobe Sign APIs: Support for TLS 1.2 may depend on the application, the runtime libraries, and/or the operating system. In some cases, TLS support is provided by operating system libraries, while in other cases it is provided by an application runtime library.

For clients running Adobe Sign for Dynamics v5.x and earlier, upgrade to v6.0.

Operating system support for TLS 1.2 requires:

• Windows server: use Windows Server 2008 R2 or later
• Windows desktop: use Windows 8 or later
• OS X: use OS X 10.8 or later

Application framework support for TLS 1.2:

• For Java: use Java 8 or later. Java 7 may be used but requires TLSv1.2 to be explicitly enabled by the application.
• For . NET: use .NET 4.6 or later. .NET 4.5 may be used but requires TLSv1.2 to be explicitly enabled by the application. .NET depends on TLS 1.2 support by Windows (see above).
• For applications using OpenSSL: use OpenSSL 1.01 or later 

Integration: End-of-life for the Adobe Sign for Microsoft Dynamics v4 and v5

Adobe Sign for Microsoft Dynamics v4, v5, and earlier (on-premise and online versions) is now retired. Adobe Sign for Dynamics v6 and later supports Microsoft Dynamics on-premise 2013, 2015, 365 and Dynamics CRM 365 Online. Contact your Customer Success manager with questions about upgrading to the latest version.

ACTION REQUIRED

Upgrade to Adobe Sign for Microsoft Dynamics v6 immediately for on-premise and online versions. You will be able to migrate all data from v4 and earlier to the latest version.

Integration: End-of-life for the Adobe Sign for Microsoft Dynamics v4

Adobe Sign for Microsoft Dynamics v4 and earlier (on-premise and online versions) has been discontinued and no longer functions as of November 30, 2017. Adobe Sign for Dynamics v6 and later supports Microsoft Dynamics on-premise 2013, 2015, 365 and Dynamics CRM 365 Online. Contact your Customer Success manager with questions about upgrading to the latest version.

ACTION REQUIRED

Upgrade to Adobe Sign for Microsoft Dynamics v6 before November 2017 for on- premise and online versions. You will be able to migrate all data from v4 and earlier to the latest version.

Latest template for IRS form W-9 available February 13

On 2/13/18, a new template for the IRS W-9 form will be added to Adobe Sign. It is entitled W-9 (Request for Taxpayer Identification Number) ver. 11/17. Concurrently, the existing W-9 template will be renamed to W-9 (Request for Taxpayer Identification Number) (legacy). This renaming does NOT affect your workflows.

On 3/13/18, the latter template, W-9 (Request for Taxpayer Identification Number) (legacy), will be retired. Prior to 3/13/18, you must take action to avoid interruptions to your workflow.

ACTION REQUIRED

The new W-9 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

To find the libraryDocumentId in an API-enabled account:

1. Log in as an Account Admin
2. Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
3. In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 
   1. Enable the library_read:self scope
4. Click the Try it out! button
5. In the Response Body, locate the new W-9 form template (not the legacy version) to see the libraryDocumentId value. 

If you need more information, please contact your Customer Success Manager.

Integration: End-of-life for Adobe Sign for Microsoft SharePoint v3 and below

Adobe Sign for Microsoft SharePoint v3 and earlier (on-premise and online versions) will no longer function as of March 31, 2017. Adobe Sign for SharePoint v4 and later supports Microsoft SharePoint on-premise 2013, 2016 and SharePoint Online.

Action Required:

Upgrade to Adobe Sign for SharePoint v4 immediately. Contact your Customer Success manager with questions about upgrading to the latest version.

Integration: Critical update to Adobe Sign for Salesforce v18

Salesforce will enforce a new security model for Lightning Components called LockerService in an upcoming release. If you are on Adobe Sign for Salesforce v18, you must upgrade to version 18.27 or higher to ensure all Salesforce Lightning Components work as intended.

ACTION REQUIRED

If you are on Adobe Sign for Salesforce v18, you must upgrade to version 18.27 or higher.

Integration: Support for the Adobe Sign integration with Salesforce v15 has ended

Product updates, security updates and technical support for Adobe Sign for Salesforce v15 has ended as of December 15, 2017

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

IMPORTANT 

Review the required by Salesforce permissions settings before starting your upgrade to v19 in the What’s new in version 19 section.

Adobe Sign templates for 2017 IRS form I-9 is now available.

On 10/24 the new template for the revised IRS I-9 form was added to Adobe Sign. It is entitled: I-9 (Employment Eligibility Verification) ver. 07/17/17 N.  

Concurrently, the existing template I-9 2017 (Employment Eligibility Verification) was renamed to: I-9 (Employment Eligibility Verification) ver. 07/17/17 N (legacy).

This renaming does NOT affect your workflow.

However, on 12/1/17, the latter template, I-9 (Employment Eligibility Verification) ver. 07/17/17 N (legacy), was retired.

If you are using the legacy template’s libraryDocumentId in your applications, you need to update to use the new libraryDocumentId value.

ACTION REQUIRED

The new I-9 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

To find the libraryDocumentId in an API-enabled account:

1. Log in as an Account Admin
2. Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
3. In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 
   1. Enable the library_read:self scope
4. Click the Try it out! button
5. In the Response Body, locate the revised I-9 form template (I-9 (Employment Eligibility Verification) ver. 07/17/17 N ) to see the libraryDocumentId value. 

If you need more information, please contact your Customer Success Manager.

Important changes to IP address ranges

If your existing network or firewall configuration explicitly explicitly lists the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration; however, you should remove two outdate IP address ranges for North America.

ACTION REQUIRED

If you explicitly list Adobe Sign IP addresses in either your API Callbacks or firewall, you must list the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable.

If you use the Adobe Sign for Salesforce integration, admins must list the additional IP address ranges in their Salesforce.com account.

Integration: Critical update to Adobe Sign for NetSuite

Oracle recently upgraded to NetSuite 17.0. The upgrade caused an issue in Adobe Sign for NetSuite in which the Agreement tab may not appear for some roles. Upgrade to Adobe Sign for NetSuite version 4.0.1 to ensure roles provisioned by the administrator on the agreement record will be able to see the Agreement tab.

ACTION REQUIRED

Login to the application and upgrade to Adobe Sign for NetSuite version 4.0.1 to ensure users will be able to see the Adobe Sign Agreement tab.

New Release: Adobe Sign September 2017 release

The Adobe Sign September 2017 product release is now complete. This release includes new features and feature enhancements for administrators and end users, including:

• Support for eIDAS compliant time stamps, certified on the EU Trusted List (EUTL)
• Support for new configurable time stamp services in case your company already uses an LTV time stamp provider
• Broader support for Cloud Signature Consortium with new partners announced
• Support for Aadhaar identity compliance and a new data center in India (IN1)
• Color coded form fields and new form field font support for a better authoring and user experience
• Form Field detection rolled out further to the field
• Replace or add recipients in flight

Broader support for Microsoft products with new or improved integrations to:

• Office 365 – Outlook, Word & PPT
• Dynamics CRM v6
• Teams
• Flow

Security: Support has ended for Windows Vista SP2 and Internet Explorer 9 and 10

Adobe Sign ended support for Windows Vista SP2 and Internet Explorer 9 and 10 on March 17, 2017. Customers continuing to use these browsers will not be able to take advantage of new features and cannot be guaranteed access to Adobe Sign in the future.

ACTION REQUIRED

Update older hardware to newer operating system configurations including, Windows 7, 8 or 10 with one of the supported browsers listed in the Adobe Sign System Requirements to ensure new Adobe Sign features continue to work as intended.

Adobe Sign May release is now complete

The Adobe Sign May release is now complete. This release includes new features and feature enhancements for administrators and end users. With this release, the classic Send and Authoring user interface have been retired, and the new user interface became the standard across Adobe Sign. API integrations that embed the Send page will also experience the change in the user interface. The new Send experience maintains all the functionality of the classic Send experience, except for the Fax signature workflow, which was replaced with a new scan and upload Written signature workflow. The new Send and Authoring experiences also include new capabilities, including private messages, new recipient roles and more.

New agreements now have updated appearance options for assigned text fields. The previous options of Helvetica, Times and Courier have been replaced with Adobe font equivalents of Adobe Source Sans Pro, Source Code Pro, and Source Serif Pro, respectively.

Not all features in this release were enabled at deployment. Some features will be activated in June. Read the Release Notes for more details.

ACTION REQUIRED

No action is required.
 

New SSL Certificate and Certificate Authority

Adobe Sign is moving to a new SSL Certificate and Certificate Authority (CA) on

July 22, 2017. There is no change to the public key, underlying cryptographic protocols or scheme. The root and intermediate CA will change with this update. Please contact Customer Support with questions.

ACTION REQUIRED

If you have custom built integrations with Adobe Sign using either the SOAP or REST APIs, and if any of these integrations has ‘pinned’ the existing public key, no action is required.

If you’re pinning the certificate using other methods, you can find the new Adobe Sign and CA certificates in the Adobe Sign System Requirements. The new SSL certificate and certificate authority will become active on July 22, 2017.

API: New setting to customize the error code generated in case of URL expiry

Currently, the HTTP error code returned when a URL expires is 404 (page not found), which is not compliant with HTTP standards. These URLs can be generated by REST API calls such as GET/agreements/{agrID}/combinedDocument/url. However, the more appropriate HTTP error code is 410 (gone). With the May release, the default HTTP error code was changed to 410. A new setting is available to allow a custom HTTP Status Code (404, 410, etc.) to be sent in this error scenario.

ACTION REQUIRED

If your applications expect an expired URL to throw a 404 error, you will need to request a change to the value of this setting to 404. Contact Customer Support for assistance.

Feature Deprecation: Fax Signature workflow

With the May 2017 release, the new Send experience became the standard, and with it, the Fax signature workflow was replaced with a new Written signature workflow using scan and upload. The modern scan and upload functionality provides improved accuracy and auditability and results in better readability. Customers that use the API were also moved to the new Written signature workflow.

The classic Send experience with Fax signatures will be available for a limited time; however, it will be deprecated on October 31, 2017. Web application users that want to continue using the Fax signature workflow can do so by reverting to the classic Send page through the Send Settings. API users need to contact their Customer Success manager to continue to use the Fax signature workflow.

ACTION REQUIRED

Review the new Written signature workflow documentation and inform your end users of the changes. You may also need to update your end user and customer documentation for written signature workflows.

Mobile: Google ID and Google Apps login in the Adobe Sign mobile app will be removed

In an effort to improve security and usability, Google no longer allows OAuth authentication requests to Google via embedded browsers known as web views in native mobile applications. As a result, the Google and Google Apps login options have been removed from the Adobe Sign mobile app with the May release.

Adobe Sign users will still be able to login with their Google IDs via the standard login (email and password). The only difference is the removal of the Google and Google Apps options on the login page. If you encounter issues with standard login and your Google ID, reset your password and try again.

Planned Maintenance with Downtime for North America (NA1)

Adobe Sign will undergo a period of planned maintenance at our North America (NA1) data center with expected downtime on:

Saturday, April 8, 2017 starting at 5:00 PM PDT and ending April 8 at 11:00 PM PDT

Customers located in our other data centers are not expected to be impacted.

The planned maintenance is required to complete the expansion of our North America data center operations. During the maintenance window, the service will be unavailable on NA1.

To confirm the data center for your account, login to Adobe Sign and note the abbreviation in the URL (NA1, NA2, etc.). Contact your customer success manager with questions.

ACTION REQUIRED

• If you use the Adobe Sign for Salesforce integration: Salesforce Integration admins must explicitly list the additional IP address ranges in their Salesforce.com account for the integration to continue to work after April 7, 2017. 
• If you list Adobe Sign IP addresses in either your API Callbacks or firewall: Adobe Sign admins must list the additional IP addresses in your API Callbacks. Notify third parties that route your Callbacks, if applicable. Without adding the new IP ranges, the callbacks will not be allowed through your firewall. IP Address Ranges and Planned Maintenance FAQ

Integration: Support for the Adobe Sign integration with Salesforce v14 has ended

Product updates, security updates and technical support for Adobe Sign for Salesforce v14 ended December 15, 2016. Version 18 is available now.

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce. Customers using unsupported versions will be required to upgrade to a current version to continue to receive technical support.

API: OAuth application support for SOAP API to be deprecated

With the December maintenance release, new OAuth applications are only able to access REST APIs. Existing OAuth applications and integration keys will continue to have access to SOAP APIs until further notice.

ACTION REQUIRED

Use the REST APIs when developing any new application. For more information, go to the Developer Center.

API & Web App: Password Complexity rules will change in 2017

Adobe Sign is changing the password complexity rules to increase security. In early 2017, customers using the web application will be prompted to update their password, and will have 90 days to comply. Customers that login or provision users through the existing REST or SOAP APIs will have until mid-2018 to update their applications to comply with the Adobe Sign password security requirements. Information on how to transition to the new rules will be available for API users in early 2017.

New password criteria:
• A minimum of 8 characters, maximum of 100 characters
• At least one uppercase character
• At least one lowercase character
• At least one digit
• At least one special character (punctuation), except empty space
• Cannot contain case insensitive username, first name or last name
• The new password will be rejected if it matches previously used passwords

ACTION REQUIRED

In early 2017, web application users should update passwords when requested. Customers that provision users through the API will have until July 2018 to update their applications to use REST API to comply with the new password criteria.

API & Web App: Support has ended for older Text Tag syntax

Support for v1.0 text tags has ended. While v1.0 tags will continue to be honored in the service, no bugs or enhancement requests will be accepted for this syntax.

ACTION REQUIRED
Ensure your users are using 2.0 text tag syntax when creating new document templates. Review applications and existing templates that may contain older text tags and update them with the newer 2.0 text tag syntax. Refer to Creating Forms with Text Tags Reference Guide for details.

Technical Update: January 2017 (Advanced Notice)

Adobe Sign templates for 2017 IRS forms I-9 and W-4 are now available. The templates entitled I-9 (Employment Eligibility Verification 2016) and W-4 2016 (IRS Employees Withholding Allowance) will be unavailable at 12:00 AM PT on January 20, 2017.

ACTION REQUIRED

The 2017 IRS form templates have new Document IDs. If you use the Document ID in your applications, you will need to update the Document IDs.

To find the LibraryDocumentID in an API-enabled account:

1. Log in as an Adobe Sign Account Admin
2. Generate an Integration Key
3. Navigate to the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation. 
4. Scroll down to the Resources and Operations section
5. In the /libraryDocuments row, click the Show/Hide link to expose the methods
6. Click the first GET button next to the /libraryDocuments option
7. Paste your Integration Key into the ‘Access-Token’ field 
8. Click the Try it out! button. 
9. Locate the 2017 I-9 and W-4 forms to see the LibraryDocumentID values

If you need more information, please contact your Customer Success Manager.