PracticeVideosBlogFlashcards

11.3 Completing Tasks During Business Processes

Key Takeaways

  • 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 seeWhat you do
ApprovalsApprove, deny, send back as configured
ActionsComplete task forms / required work
To DosAcknowledge / complete instructional items
Checklist itemsComplete grouped onboarding/offboarding tasks
Other questionnaires / tasksAs 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.

RoleWhoHow determined
InitiatorUser who starts the BPMust have Initiate on the BP Security Policy (and succeed at initiation)
SubjectWorker the BP is aboutThe person being hired, changed, terminated, compensated, etc.

Common confusions

Stem languageCorrect 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.

SymptomLikely runtime cause
Item never appears for user ASecurity/routing; or serial wait on earlier step; or wrong definition
User A completed; event still In ProgressParallel sibling still open; or subprocess still open
Wrong person received approvalRole assignment / routing / constrained org context
Subprocess tasks appear "inside" hire storyNested BP working as designed

Completing Tasks: Practical Sequence

  1. Identify the event type (Hire, Change Job, Terminate, Propose Compensation…).
  2. Open My Tasks item; read instructions / help text if present.
  3. Enter required data for Actions; choose approve/deny for Approvals.
  4. Submit to complete your step.
  5. Confirm whether the overall event completed or advanced to someone else.
  6. 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.

OperationWhen available (conceptual)What it does
CancelBP still in progress (not successfully completed)Stops the incomplete event so it does not complete as a successful transaction
CorrectIn progress or completed, where supported by BP type and securityEdits supported event data without fully unwinding the event
RescindBP completedReverses 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 statementReality
"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

NeedWhere it lives
See My Tasks itemRouting + membership + BP permissions
Complete ActionBP policy rights for that action + domain access to fields
ApproveApprove on BP policy + routing
Cancel / Rescind / CorrectSpecific BP policy permissions + event state
Nested compensation taskChild 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

  1. Initiator HR Partner starts Hire for Subject Taylor (Position Management vacant seat).
  2. Subprocess Propose Compensation opens for Compensation Partner (Action/approval work on child BP).
  3. Parallel Manager Approval and HR secondary review both appear.
  4. Manager completes approval; Hire still waits on HR parallel step.
  5. HR completes; onboarding Checklist items land in Manager and IT My Tasks.
  6. Event completes; Worker History shows full path.
  7. Next day, HR notices wrong location on the completed hire: Cancel unavailable → Correct if appropriate, else carefully evaluate Rescind.

Study Checklist for Runtime Mastery

  1. Use My Tasks as the completion surface for BP steps.
  2. Name Initiator vs Subject without hesitation.
  3. Predict parallel wait vs serial wait symptoms.
  4. Apply Cancel / Correct / Rescind from event state first, operation second.
  5. 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.

Test Your Knowledge

What is the function of My Tasks (Inbox) in Workday?

A

It is the user's actionable queue of awaiting Business Process steps such as approvals, Actions, and To Dos assigned to them

B

It is the tenant-wide catalog of every BP definition for all companies

C

It permanently stores all Domain Security Policies for activation

D

It replaces Search as the only way to open Supervisory Organizations

Test Your Knowledge

What is the difference between the Initiator and the Subject on a Business Process?

A

They are always the same person by definition

B

The Subject is always the system administrator; the Initiator is always Payroll Partner

C

The Initiator is the user who starts the BP (per Initiate permission); the Subject is the Worker the BP is about

D

The Initiator only exists on reports; the Subject only exists on integrations

Test Your Knowledge

When can Cancel be used on a Business Process event?

A

Only after the BP has successfully completed

B

Only after Rescind has already failed

C

Only by the Subject worker on self-service events

D

While the BP is still in progress and not yet successfully completed, subject to BP Security Policy

Test Your Knowledge

A Change Job Business Process completed successfully, but HR entered the wrong effective date and downstream tasks already ran. Which statement is correct?

A

Use Cancel immediately because Cancel always works on completed events

B

Cancel is no longer available; use Correct to edit limited completed-event data or Rescind to reverse the completed event and unwind downstream effects

C

Only Delete Worker can fix effective dates on completed Change Job events

D

Suspend is required before any completed Change Job can be researched in Worker History

Sections you finish are checked off in the contents.