5.2 Step Types: Actions, Approvals & Approval Chains

5.2 Step Types: Actions, Approvals & Approval Chains

Quick Answer: Workday's Business Process Framework structures workflow progression through specialized step types. Action steps require an actor to enter or update business object data (e.g., Propose Compensation). Approval steps represent governance checkpoints where an authorized actor evaluates submitted data with three choices: Approve (advance process), Deny (permanently terminate event and discard changes), or Send Back (return event to a prior step for data revision). Approval Chains dynamically walk up an organizational reporting hierarchy until reaching a predefined stop condition (e.g., Vice President level or financial threshold). Consolidated Approvals streamline managerial overhead by bundling multiple subprocess approvals into a single inbox review task.

---

Functional Categorization of Workflow Step Types

Every step in a Workday Business Process Definition performs a distinct operational function. To design compliant and efficient business processes, HCM administrators must categorize steps according to whether they alter data, enforce governance, automate tasks, or group user interactions.

+-----------------------------------------------------------------------------------------+
|                                 WORKDAY BPF STEP TYPES                                  |
+-----------------------------------------------------------------------------------------+
|  DATA INPUT & MUTATION   |       GOVERNANCE        |   AUTOMATION    |   USER EXPERIENCE    |
|  - Action Steps          |  - Approval Steps       |  - Integration  |  - Consolidated      |
|  - Subprocesses          |  - Approval Chains      |  - Service Step |    Approvals         |
|  - Review Tasks          |  - Multiple Approvals   |                 |  - Checklists        |
+-----------------------------------------------------------------------------------------+

---

Action Steps: User Tasks and Subprocesses

An Action step is a transactional step that requires an assigned security group or role to enter, modify, or verify data in Workday before the process can advance.

Characteristics of Action Steps

• Data Mutation: Unlike an approval step, an action step allows the user to change attributes on business objects. For instance, in the Propose Compensation Change action step, the compensation partner selects pay grades, inputs salary amounts, and adds allowance plans.
• Task Presentation: Action steps appear in the assignee's My Tasks (Inbox) as interactive data-entry forms containing fields, drop-down prompts, and configurable grids.
• Subprocess Triggering: Action steps can launch child business processes (subprocesses). For example, during a Change Job business process, an action step can initiate the Propose Compensation Change subprocess, which executes its own independent definition, security policies, and approval hierarchy before returning control to the parent process.

Common Delivered Action Steps

• Propose Compensation Change (Hire, Change Job)
• Edit Position Restrictions (Create Position)
• Change Organization Assignments (Hire, Transfer)
• Edit Government IDs (Onboarding, Hire)
• Assign Pay Group (Staffing Lifecycle)

---

Approval Steps: Governance Mechanics & Decision Actions

An Approval step is a governance checkpoint. It assigns a review task to an authorized security role (e.g., Manager, HR Partner, Finance Director) to validate proposed changes.

The Three Core Decision Actions

When an approver opens an approval task in My Tasks, Workday displays the proposed transaction details alongside three primary action buttons:

[ APPROVE ]  --------------------> Advances workflow to the next step / join point
[ SEND BACK ] -------------------> Reroutes event to a designated prior step for correction
[ DENY ]      -------------------> PERMANENT TERMINATION: Event killed, changes discarded

1. Approve

The approver affirms the proposed transaction. The step transitions to Completed in the Process History, and the BPF engine immediately evaluates the next sequential step or parallel branch.

2. Deny (The Terminal Option)

Deny is a destructive, irreversible governance action. When an approver selects Deny:

• The entire business process event terminates immediately.
• The event status permanently transitions to Denied.
• All active parallel branches and downstream steps are aborted.
• All proposed data entered during preceding action steps is purged; no changes commit to the operational database.
• Critical Exam Rule: A denied event cannot be resumed or un-denied. If the business still wishes to execute the change, the initiator must restart the entire transaction from step a.

3. Send Back (The Corrective Option)

Send Back is used when the proposed transaction is fundamentally valid but contains data entry errors (e.g., an incorrect base salary amount, wrong cost center allocation, or improper job profile).

• When selecting Send Back, the approver is presented with a dialogue box containing a mandatory comment field and a drop-down list of eligible prior action steps (including the initial submission step).
• The approver inputs an explanation (e.g., "Base salary exceeds the approved hiring budget; reduce to $115,000") and submits.
• The event status remains In Progress, but the active task reroutes back to the designated step assignee or original initiator.
• The recipient corrects the flagged data and clicks Submit, resuming the workflow. Depending on configuration, the process can route back through intervening approvers or return directly to the approver who initiated the send-back.

Configurable Approvals: Allow Approver to Edit Data

Standard approval steps are read-only; the approver can only evaluate and decide. However, Workday provides an advanced configuration option: Allow Approver to Edit Data. When enabled on an approval step, the approver can directly modify specific fields (e.g., adjusting an allowance amount or updating an effective date) directly within the approval task, eliminating the operational delays associated with sending the event back to the initiator.

---

Approval Chains: Dynamic Hierarchical Routing

An Approval Chain is an automated workflow construct that routes approval requests sequentially up an organizational reporting structure.

Hierarchy Traversal Mechanics

Rather than requiring administrators to manually configure separate approval steps for each managerial level, an Approval Chain dynamically queries the organizational tree at runtime. It begins at a configured starting point (typically the Subject's Manager or Initiator's Manager) and advances up the direct reporting chain.

Initiator (Worker) 
       |
       v
Step 1: Direct Manager (Level 1) -----------> Approved
       |
       v
Step 2: Senior Manager (Level 2) -----------> Approved
       |
       v
Step 3: Director (Level 3)       -----------> Approved
       |
       v
[STOP RULE SATISFIED: Reached Director Level / Limit $100K] --> Chain Completes

Essential Approval Chain Configuration Parameters

1. Hierarchy Type: Specifies which organizational structure to ascend. Options include Supervisory (direct reporting line), Cost Center Hierarchy, or a custom matrix organization.
2. Start At: Defines where chain traversal commences. Common settings include:
   • Manager of Subject
   • Manager of Initiator
   • Specific Management Level
3. Stopping Criteria (Stop Rules): The chain evaluates stopping rules prior to dispatching each approval. Traversal halts when any of the following occur:
   • Management Level: The chain ascends until it reaches a manager holding a designated management level (e.g., Stop at: Vice President).
   • Number of Levels: The chain executes a fixed number of approvals (e.g., Route 2 Levels Up).
   • Rule Condition: A boolean expression halts the chain based on data attributes (e.g., Stop when Manager Approval Limit >= Proposed Base Pay).
   • Top of Hierarchy: If no stop rule is satisfied, the chain traverses to the top-level supervisory organization (e.g., the Chief Executive Officer).
4. Skip Rules: Prevents workflow redundancy. If a manager in the chain is the person who initiated the event, or if a manager has already approved a preceding step in the same transaction, the Skip Rule automatically skips their step and routes to the next level up.

---

Consolidated Approvals: Manager User Experience Optimization

In high-volume or complex staffing events (such as Hire or Change Job), a transaction frequently spawns multiple concurrent subprocesses, each requiring managerial approval (e.g., approving proposed compensation, approving job profile adjustments, and approving location assignments).

The Administrative Problem: Approval Fatigue

Without consolidation, a hiring manager receives three to four discrete approval notifications in their My Tasks inbox for a single employee hire. Reviewing and clicking Approve across multiple separate tasks creates operational friction and increases the risk of rubber-stamping.

The Architectural Solution: Consolidated Approval

When an administrator configures a Consolidated Approval step on the parent business process definition:

• Workday monitors all child subprocesses generated by the parent event.
• When the child subprocesses reach their respective approval steps, Workday suppresses individual inbox notifications.
• Instead, the BPF engine bundles the pending approvals into a single, comprehensive Consolidated Approval task in the manager's inbox.
• The manager opens one unified interface displaying side-by-side grids of compensation details, organization assignments, and position restrictions.
• A single click of Approve simultaneously satisfies all underlying subprocess approval steps.

---

Review vs. Approval: Architectural Distinctions

On the Workday HCM certification exam, candidates must navigate subtle naming conventions that distinguish data manipulation tasks from governance tasks.

Exam Tip: In delivered Workday definitions, tasks labeled Review Employee Information or Review Proposed Compensation are architecturally configured as Action steps, not Approval steps. They prompt the user with a Submit button, allowing the user to make data adjustments before sending the event downstream.

---

Step Configuration Matrix

---

Certification Pitfalls & Common Exam Traps

1. The Deny vs. Send Back Trap: A classic exam question asks what an approver should do when a submitted job requisition lists an incorrect target start date. If the approver clicks Deny, the requisition is permanently destroyed and cannot be recovered. The correct governance action is Send Back, which returns the requisition to the initiator for date correction.
2. Unbounded Approval Chains: Forgetting to configure an explicit Stop Rule on an Approval Chain results in the chain routing all the way to the CEO. Workday requires either a management level threshold, level count, or condition rule to bound hierarchical traversal.
3. The Proxy Approval Audit Trap: If an administrator or peer acts as an approver via Workday Delegation or administrative proxy, the Process History explicitly records both the assigned role and the exact authenticated worker who clicked Approve (Completed By: Marcus Vance acting on behalf of David Ross).