Adobe Acrobat Sign for Workday: Quick Start Guide

Contact Adobe Sign Support

Overview

This document is designed to help Workday administrators understand how to customize the Workday Business Processes to include Adobe Sign for obtaining e-signatures. To use Adobe Sign within Workday, you must know how to create and modify Workday items such as:

• Business Process Framework
• Tenant Set-up and configuration
• Reporting and Workday Studio Integration

Accessing Adobe Sign within Workday

Adobe Sign electronic signature capability is surfaced as Review Document Step action within the Business Process Framework (BPF) and as a Distribute Documents task.

Review Document Step

Adobe Sign for Workday is exposed via the Review Document Step that you can add to any of over 400 Business Processes within Workday, including Offer, Distribute Documents and Tasks, Propose Compensation, and more.

You may refer to the Workday community articles on Review Document Step.

There is a 1:1 relationship between Review Document Steps and billable transactions with Adobe Sign. You can combine multiple documents within a single Review Document Step and they are presented as a single package for signature.

Note: Only a single Dynamic document can be referenced within a specific Review Document Step.

To define a functional Review Document Step:

1. Insert a Review Document Step.
2. Specify the Groups (roles) that can act upon the Review Document Step.

To configure the Review Document Step:

1. Specify the eSignature Integration type as eSign by Adobe.
2. Add rows to the Signature Grid.
   
   • The signature grid specifies the serial order in which the document is routed for signature. Each row can contain one or more roles and each row represents a step in the signing process.
   • Every member of the role within a particular step is notified that a signing event is pending.
   • Once a single person from the role signs, the row step is completed and the document is moved to the next row step.
   • When all rows have been signed, the Review Document Step is complete.

3. Specify the document to be signed. If the document is an Offer BP, you can use it from a Generate Document step. Otherwise, choose an existing document or report.

4. Repeat step 3 for as many documents as you require.
5. Optionally, add a ‘redirect user’ for capturing ‘decline to sign’ actions. When users decline, Workday reroutes the documents to a configured security group for review.
6. From the related actions menu of a Review Document Step, select Business Process > Maintain Redirect. Next, select one of the following:
   • Send Back: To enable security group members to send a step back to a prior step in the business process. The business process restarts from that step.
   • Move to Next Step: To enable security group members to forward a step to the next step in the business process.
   • Security Groups: To redirect steps in the business process flow. Security groups that display at this prompt are selected in the business process security policy in the Redirect section.

Business process step notes

The Business Process Framework is powerful; however, you must ensure that:

• Every Business Process must have a completion step, which is ideally at the end of the business process.

• A completion step is set off the related actions menu of the search icon. This is possible only while “viewing” the BP and not while “editing” it.

• Every step of the business process is executed sequentially.

  You can change the order of a step by changing the order value. For instance, to insert a step between items “c” and “d”, specify a new item as “ca”.

Offer Example 

The Offer BP is a sub-process of the Job Application Dynamic BP that must be configured to execute the Offer BP. It is triggered when the Job Application state is moved to “Offer” or “Make Offer”.

In the below example, a Review Document Step is using a Dynamic Document step for both North America and Japan.

This BP does the following:

• Asks the initiator of the BP to propose compensation for the candidate (step b).

• Uses a step condition to test whether the current country is NOT Japan.

  If true, it executes step “ba” which uses an English language document.

  If false, it executes step “bb” which uses a Japanese language document.

• Defines the signature process in the Review Document Step “bc”.

• Defines the decision point to make an offer in the required completion step “d”.

The Dynamic document being generated in step “ba” is called Offer Letter and contains a single text block named Rapid Offer. You can add multiple text blocks such as header, salutation, compensation, stock, closing, terms, and more as required.

The Dynamic offer letter below is created in the Workday rich text editor. The items highlighted in gray are Workday-provided objects that reference contextual data.

Items in {{brackets}} are Adobe Text tags.

Within the Review Document Step, the dynamic document is referenced from the previous step and defines the sequential signature process via two signing groups.

The behavior illustrated below routes the dynamically generated document first to the Hiring Manager, and then to the Candidate.

Distribute documents Example

Introduced in Workday 30, the Mass Distribute Documents or Tasks task can be used to send a single document to a large group (<20K) of individual signers. It is limited to a single signature per document. The creation of distribution is performed by accessing the ‘Create Distribute Documents or Tasks’ action from the search bar.

Example: Send an employee equity choice form to all managers with Global Modern Services. You can further filter it to individual managers if desired.

You can also access the View Distribute Documents or Tasks report to track the progress of the distribution.

Reporting Example

Workday has a rich reporting infrastructure. To look at the details of the Adobe Sign process, inspect the elements of the Review Document Event.

Below is a simple custom report that can be run across all BPs looking for Adobe Sign transactions and their status.

The following report was generated by looking at Offer, Onboarding, and Propose Compensation BPs within an implementation tenant.

You can see:

• The documents out for signature
• The associated BP step
• The next person awaiting signature

Signed documents

The Workday signature cycle suppresses all email notifications by Adobe Sign. Users are informed of pending actions within their Workday inbox.

Once a document is signed by all Signature Groups, a copy of the signed document is distributed to all the members of the Signature Group via email.

To suppress this behavior, you may contact your Adobe Sign Success Manager or the Adobe Sign Support team.

Within Workday, you can access the signed documents on the full process record. You may find:

• Worker documents on the Worker Profile, and
• Candidate documents (offer letters) on the Candidate profile.

The below image shows a signed offer letter for the candidate Chris Foxx.

Support

Workday support

Workday is the integration owner and should be your first point of contact for questions about the scope of the integration, feature requests, or problems in day to day function of the integration.

The Workday community has several good articles on how to troubleshoot the integration and generate documents:

• Troubleshoot eSignature Integrations
• Review Documents Step
• Dynamic Document Generation
• Offer Document Generation Configuration tips

Adobe Sign support

Adobe Sign is the integration partner and should be contacted if the integration is failing to obtain signatures, or if notification of pending signatures fails.

Adobe Sign Customers should contact their Customer Success Manager for support. Alternatively, Adobe Technical Support can be reached by phone at 1-866-318-4100, wait for the product list then enter 4 and then 2 (as prompted).

• Adding Adobe Text Tags to Documents