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”.
Example: offer
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.
Example: Distribute documents
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. Creation of a 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.
Example: Reporting
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.