11.3 Completing Tasks During Business Processes

Workday Pro HCM Core Certification Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Format 1.2 Eligibility, Learning Path & Access 1.3 Study Strategy & Blueprint Map

2 Navigation & Business Objects

2.1 Navigation Techniques in Workday 2.2 Business Objects & Finding Data

3 Organizations & Hierarchy

3.1 Organization Types & Subtypes 3.2 Supervisory Organizations & Reporting Structure 3.3 Cost Centers, Company Hierarchies & Locations 3.4 Leadership Roles & Worker Organization Assignments

4 Staffing Models

4.1 Position Management Staffing Model 4.2 Job Management Staffing Model 4.3 Hiring Restrictions on Organizations

5 Job Profiles & Job Structure

5.1 Creating & Editing Job Profiles 5.2 Job Profiles, Jobs, Positions & Workers 5.3 Job Families, Family Groups & Job Requisitions

6 Compensation Fundamentals

6.1 Compensation Framework Components 6.2 Eligibility Rules & Compensation Defaulting 6.3 Packages, Grades & Grade Profiles 6.4 Salary Plans, Allowance Plans & Worker Comp Events

7 Jobs, Positions & Staffing Events

7.1 Creating Positions & Position Hiring Restrictions 7.2 Managing Filled, Unfilled, Close & Freeze 7.3 Hire Process End-to-End 7.4 Job Changes & Additional Staffing

8 Termination & Contingent Workers

8.1 Terminate Employees 8.2 Contracting Contingent Workers 8.3 Ending Contingent Worker Contracts

9 Configurable Security

9.1 Functional Areas, Domains & Business Processes 9.2 User-Based, Role-Based & Workday-Assigned Groups 9.3 Domain Security Policies 9.4 BP Security Policies, Org Access & Activation

10 Business Process Framework

10.1 Organizations, Security & BP Relationships 10.2 Default, Org-Specific & Rule-Based Definitions 10.3 Definition, Type, Event & Step

11 Business Process Steps & Approvals

11.1 Actions & Subprocesses 11.2 Approvals & Approval Chains 11.3 Completing Tasks During Business Processes

12 Business Process Configuration

12.1 Condition Rules 12.2 Advanced Routing, Labels & Help Text 12.3 Custom Notifications 12.4 Step Ordering Letters & Validation Conditions

13 BP Management & Security

13.1 Mass and Individual BP Management 13.2 BPs and Configurable Security Interaction

14 Report Writer Fundamentals

14.1 Standard Reports & Copy/Modify 14.2 Building Custom Reports: Index vs Standard 14.3 Sorting, Filtering & Prompts 14.4 Report Security, Sharing & Ownership

15 Advanced Reporting & Calculated Fields

15.1 Scheduling Reports 15.2 Matrix Reports 15.3 Discovery Boards 15.4 Calculated Fields & Report Performance

11.3 Completing Tasks During Business Processes

Key Takeaways Explain This Topic AI

My Tasks (Inbox) is the personal queue of awaiting BP work—approvals, Actions, To Dos, checklists—assigned to you; completed items move toward archive/history views as designed.

Initiator is the user who starts the BP (Initiate permission); Subject is the Worker the event is about—keep these roles distinct when tracing an event.

Parallel steps can appear together and require all required siblings to finish; serial steps appear in order—stuck events often mean waiting on another parallel actor, not a broken tenant.

Cancel applies only while a BP is still in progress; after successful completion use Correct (edit without full unwind) or Rescind (reverse and unwind downstream effects).

Cancel, Correct, and Rescind availability and authority are governed by BP Security Policy and event state—not merely by "I was the initiator."

Last updated: September 2026

11.3 Completing Tasks During Business Processes

Study index: T-numbers here refer to this guide’s index of an older Workday topic list. They are not current Workday task IDs or published exam weights.

Quick Summary: Configuration means nothing if you cannot complete work at runtime. My Tasks is where Actions, Approvals, To Dos, and Checklists land. Know Initiator vs Subject , watch parallel vs serial waiting behavior, and master the exam trap triangle Cancel / Correct / Rescind based on whether the event is still in progress or already complete.

Tasks T47 and T48 are not only definition vocabulary. Pro HCM Core expects you to demonstrate how work flows through the inbox while a Hire or Change Job is alive—and what to do when something must stop or reverse. This section is the runtime companion to Actions, Subprocesses, and Approvals.

My Tasks (Inbox): The Action Queue

My Tasks (formerly commonly called Inbox in older materials) is each user's personal queue of Business Process items that need action:

Item kinds you will see What you do
Approvals Approve, deny, send back as configured
Actions Complete task forms / required work
To Dos Acknowledge / complete instructional items
Checklist items Complete grouped onboarding/offboarding tasks
Other questionnaires / tasks As the definition routes them
What My Tasks is not
Not the tenant-wide process catalog,
Not a substitute for Search to find Workers or orgs,
Not a shared company Favorites list,

Not email itself (email may notify , but the work queue is My Tasks).

Configuration scenario: Jordan, a store Manager, opens My Tasks Monday morning and sees three Hire approvals, one Change Job approval, and two onboarding checklist items. Completing those items is how Jordan participates in BPs—not by editing BP definitions.

Finding process context

When researching a stuck or historical event:

Open the item from My Tasks while it is awaiting you,

Use Worker History / view business process for worker to see initiator, approvers, dates, and outcomes for that Worker,

Distinguish parent event vs subprocess child when compensation is nested under Hire.

Initiator vs Subject

These two nouns are exam magnets.

Role Who How determined
Initiator User who starts the BP Must have Initiate on the BP Security Policy (and succeed at initiation)

Subject Worker the BP is about The person being hired, changed, terminated, compensated, etc.

Common confusions

Stem language Correct read
"Who launched Change Job for Alex?" Initiator
"Who is Alex on that Change Job?" Subject
"Can only the initiator approve?" Not necessarily —Approve is separate permission/routing

"Is the subject always the initiator?" No —self-service cases exist, but Hire is often HR/Manager initiating for a new/existing subject

Exam trap: Options that say the Initiator is "the Worker the BP is about" are describing the Subject . Options that say the Subject always runs payroll or is always the system administrator are noise. HR Partner (Initiator) starts Hire

│
▼
Hire event Subject = new Employee being hired
│
├── Manager Approval → Manager (not initiator, not subject)
└── Propose Compensation subprocess → Compensation Partner
Parallel vs Serial Step Awareness at Runtime
Serial experience

You only see your step after prior required steps complete. If Manager approval is step 3 and you are HR on step 4, your My Tasks item may not exist until Manager finishes.

Parallel experience

Multiple people receive tasks together . The event stays in progress until all required parallel steps complete. A frequent support question is: "I approved already; why is Hire not complete?" Answer: another parallel approver or action is still open .

Symptom Likely runtime cause
Item never appears for user A Security/routing; or serial wait on earlier step; or wrong definition
User A completed; event still In Progress Parallel sibling still open; or subprocess still open
Wrong person received approval Role assignment / routing / constrained org context
Subprocess tasks appear "inside" hire story Nested BP working as designed
Completing Tasks: Practical Sequence

Identify the event type (Hire, Change Job, Terminate, Propose Compensation…).

Open My Tasks item; read instructions / help text if present.

Enter required data for Actions; choose approve/deny for Approvals.

Submit to complete your step.

Confirm whether the overall event completed or advanced to someone else.

If still open, check process history for the next waiting step (parallel partner, subprocess, chain level).

Delegation at completion time

If the normal approver is out, delegation may route their BP responsibilities temporarily. Completing a delegated item still records proper participation under the delegation design—it is not the same as permanently reassigning the Manager role.

Cancel vs Rescind vs Correct (Exam Traps)

This triad appears across staffing and BP questions. Tie it tightly to event state .

Operation When available (conceptual) What it does

Cancel BP still in progress (not successfully completed) Stops the incomplete event so it does not complete as a successful transaction

Correct In progress or completed, where supported by BP type and security Edits supported event data without fully unwinding the event

Rescind BP completed Reverses the completed event and unwinds downstream effects—powerful, destructive, use sparingly

Decision tree Is the BP successfully completed?

│
├── NO (in progress)
│ └── Cancel may apply (if security allows)

│ Correct may be available in progress; Rescind follows the completion step.

│
└── YES (completed)
├── Need limited data fix without full unwind? → Correct
└── Event should never have completed / must reverse effects? → Rescind
Cancel is NO LONGER available
Important traps

Trap statement Reality
"Cancel after completion" Invalid —completion ends Cancel
"Rescind and Cancel are synonyms" False —different states and effects

"Correct fully unwinds benefits, access, and everything like Rescind" False —Correct is edit-without-full-unwind

"Only the original initiator can Cancel" Not reliable —permission is BP Security Policy , not initiator magic
"Suspend is the standard completed-event fix" No —not the Cancel/Correct/Rescind triad taught for Core

Scenario 1 — In progress: HR started Hire with the wrong position; Manager has not approved. A user with Cancel rights Cancels the in-progress Hire and starts correctly. Rescind is the wrong mental model because nothing successfully completed.

Scenario 2 — Completed wrong date: Termination completed with the wrong termination date; benefits tasks already fired. Cancel is gone. Choose Correct for an allowed data correction path, or Rescind if the termination must reverse and unwind. Coordinate carefully—Rescind is not casual.

Scenario 3 — Completed false hire: Hire completed for the wrong person. You do not "Cancel" yesterday's completed Hire. Security-permitted Rescind reverses the completed event; then process the correct hire if needed.

In-Progress vs Completed: Why the Exam Cares

Downstream effects (onboarding checklists, compensation history, benefits, position vacancy, security role impacts) attach when events complete . That is why:

Cancel is safe-stop language for incomplete work,
Rescind is reverse-the-world language for completed work,

Correct edits supported event data, in progress or completed where allowed, without claiming a full unwind.

Staffing chapters already introduced this triad on Terminate and Hire; BP Fundamentals expects you to apply it generically to any Business Process event state.

Security Reminder While Completing Work

Need Where it lives
See My Tasks item Routing + membership + BP permissions
Complete Action BP policy rights for that action + domain access to fields
Approve Approve on BP policy + routing
Cancel / Rescind / Correct Specific BP policy permissions + event state
Nested compensation task Child BP policy, not only parent

If a user "is Manager" but cannot approve, diagnose policy listing , activation of pending security policy changes, role assignment , constraint , and routing —not only My Tasks UI preference.

End-to-End Runtime Story

Initiator HR Partner starts Hire for Subject Taylor (Position Management vacant seat).

Subprocess Propose Compensation opens for Compensation Partner (Action/approval work on child BP).

Parallel Manager Approval and HR secondary review both appear.

Manager completes approval; Hire still waits on HR parallel step.

HR completes; onboarding Checklist items land in Manager and IT My Tasks.

Event completes ; Worker History shows full path.

Next day, HR notices wrong location on the completed hire: Cancel unavailable → Correct if appropriate, else carefully evaluate Rescind .

Study Checklist for Runtime Mastery

Use My Tasks as the completion surface for BP steps.

Name Initiator vs Subject without hesitation.

Predict parallel wait vs serial wait symptoms.

Apply Cancel / Correct / Rescind from event state first, operation second.

Always ask whether security + routing explain a missing task before blaming the step type.

Runtime fluency turns T47–T48 from vocabulary into the same judgment you need when a live Hire is stuck at 4:55 p.m.—exactly the consultant mindset Workday Pro HCM Core rewards.