13.1 Mass and Individual BP Management

13.1 Mass and Individual BP Management

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: After you design definitions and steps, you still must operate live events. Individual management works one Hire or Change Job at a time—status, reassign, cancel. Mass management applies the same recovery to many events when inboxes flood or a role leaves mid-process. Task T55 is operational fluency: see status clearly, move work safely, cancel only when allowed, and unstick events without breaking completed history.

Business processes are in the current HCM Core scope; their current exam weight and passing threshold are not public. Earlier BP chapters covered the framework, step types, and configuration. This section closes the operational loop: how administrators and authorized operators manage events that already exist—individually and in bulk—and how to troubleshoot when an event appears stuck.

Why BP Management Is an Exam Topic

Configuration questions ask “what step type?” or “which definition fires?” Management questions ask:

• Who is waiting on this Hire, and can we move it?
• Fifty Change Jobs sit on a manager who left—what tool do we use?
• Is this event still cancelable, or is it completed?
• Why does status say Awaiting Action when “nothing is wrong”?

T55 expects you to choose the right management surface (individual vs mass), the right action for event state (Cancel vs Correct vs Rescind), and a logical diagnosis path for stuck work—not to invent new definitions under pressure.

Event State Before You Touch Anything

Every management decision starts with event state and current step.

 In progress ──► Cancel (stop without completing)
                 Reassign (change who owns current step)
                 Complete step (normal path)

 Completed ────► Correct (edit allowed completed data)
                 Rescind (reverse event; unwind effects)
                 ✗ Cancel no longer available

Exam trap: “Cancel the completed Hire so the wrong start date goes away.” Wrong tool. Completed events are not canceled; use Correct for limited field fixes or Rescind to reverse the event and unwind downstream effects (subject to security and process design).

That Cancel / Correct / Rescind triangle appeared in step runtime (Chapter 11). T55 reuses it as the management decision tree when you operate from admin tasks and Related Actions rather than as the everyday approver.

Individual BP Management

Individual management means you open one business process event and act on that instance.

Where you work

View status (first skill)

View status / process history answers:

1. Which definition ran (default, org-specific, rule-based result)?
2. Which steps completed, skipped, or are current?
3. Who is the awaiting person (or group of candidates)?
4. Is the event still in progress or successfully completed?
5. Were any steps denied, sent back, or parallel-waiting?

Without status, reassignment and cancel are guesses. In practice, stems that describe “stuck for three days” almost always expect you to inspect awaiting persons and step type before mass-canceling half the tenant.

Configuration/ops scenario: Contoso’s HRIS opens a Hire event Related Actions → Business Process → views status. History shows Manager Approval completed, Propose Compensation subprocess Awaiting Action for the Compensation Partner on Engineering. The Hire is not broken; it is waiting on a nested subprocess actor. Fix: complete compensation proposal or reassign that step—not cancel Hire casually.

Reassign (individual)

Reassign moves the current outstanding step from one worker (or from an empty/invalid assignee situation) to another authorized person so the event can continue.

Use reassign when:

• The assignee left the company or is on long leave.
• The step routed to the wrong person because of a temporary role gap.
• A backlog must clear before a hard effective date.

Reassign does not:

• Rewrite the BP definition permanently.
• Grant the new assignee security they lack (if they cannot Approve per BP policy, reassign may still fail or leave them unable to complete).
• Replace Cancel when the business wants the event dead.

Exam trap: “Reassign always bypasses BP security.” False. The destination user still needs the appropriate BP permission (for example Approve) and domain access to finish the step. Reassign changes who holds the task, not the security policy catalog.

Cancel (individual)

Cancel stops an in-progress event so it does not complete. Typical reasons:

• Hire was started for the wrong position.
• Change Job was initiated in error.
• Business withdrew the request before approvals finished.

Cancel is state-gated: available while in progress; unavailable after successful completion. Authority is security-gated: BP security policy (and admin domains) control who may cancel—not merely “I initiated it,” though initiators are often designed into cancel permissions.

Correct and Rescind (individual events and permitted states)

Ops scenario: A Terminate completed with the wrong last day of work. HR cannot Cancel. If policy and step design allow, Correct the date fields; if the termination should never have happened, evaluate Rescind (with awareness of payroll, benefits, and position vacancy side effects).

Mass BP Management

Mass management applies operational actions across many events in one administrative pass. Exam language: use mass and individual tasks to manage business processes—not only the happy-path My Tasks click.

When mass tools are the right answer

Mass task patterns (conceptual)

Workday provides administrative tasks and reports that let authorized users:

1. Find / filter business process events by type, status, date, organization, step, or awaiting person.
2. Select a set of matching events.
3. Apply an action such as reassign current steps or cancel eligible in-progress events.
4. Review results (success/failure per event).

Mass is still state- and security-aware:

• You cannot mass-cancel completed events with Cancel semantics.
• You cannot reassign to a user who is not a valid participant under security/routing design and expect magic completion.
• Filters matter: mass actions on the wrong status set cause production incidents.

 Mass workflow (mental model)
   1. Report / find events (type + status + awaiting person)
   2. Confirm business intent (reassign vs cancel)
   3. Confirm each selected event is still eligible
   4. Execute mass action
   5. Spot-check remaining stuck items individually

Configuration/ops scenario: Global Retail’s West Region HR Partner resigns with 37 in-progress Hire and Change Job approvals. The security admin does not open 37 events by hand. They run a mass reassignment of awaiting approval steps from the former partner to the interim partner (who already holds HR Partner on the same supervisory span and has Approve on those BP security policies). Events continue; definitions are untouched.

Exam trap: Mass reassign rewrites the default Hire definition. False. Mass management operates on events (runtime instances), not on the definition catalog (configuration). Changing who completes today’s steps is not the same as Maintain Step Conditions on the definition.

Individual vs Mass Side by Side

Troubleshooting Stuck Events

A stuck event is an in-progress business process that is not advancing—often with aging Awaiting Action status. “Stuck” is a symptom, not a diagnosis.

Diagnosis checklist (memorize)

1. Confirm state — Still in progress? If completed, Cancel will not apply.
2. Read process history — Which step is current? Action, Approval, Approval Chain, Subprocess, To Do, Integration?
3. Identify awaiting person(s) — Empty assignee? Terminated worker? Wrong role holder?
4. Check parallel vs serial — Parallel siblings may all need to finish before the process continues; waiting can look like a freeze.
5. Check nested subprocess — Parent Hire may wait on Propose Compensation or another nested BP.
6. Security — Does the awaiting user have Approve/Action permission and domain View/Modify for required fields?
7. Role / org context — Did a reorg remove Manager or HR Partner from the Supervisory Org so routing has no valid participant?
8. Conditions — Entry/validation misconfiguration can block or skip unexpectedly (Chapter 12); validate with Rule Tester when logic is suspect.
9. Integrations / system steps — Integration steps may wait on external systems or exit conditions.
10. Choose remedy — Complete step, reassign, fix role/security, fix data validation, cancel if business withdraws, or escalate definition defects.

Stuck-event symptom table

Worked scenario A — false stuck
Change Job shows Awaiting Action for three days. Status reveals a parallel To Do for IT provisioning still open while Manager already approved. Remedy: complete the To Do (or cancel the event if the change is abandoned)—not mass reassign Manager approvals that already finished.

Worked scenario B — real assignee gap
Twenty Hires await a Compensation Partner who transferred without role reassignment. Remedy: assign Compensation Partner on the correct orgs, then mass reassign remaining compensation steps to the new partner.

Worked scenario C — wrong tool after completion
Hire completed yesterday with wrong job profile. Support ticket says “cancel and redo.” Correct answer path: Cancel unavailable; evaluate Correct vs Rescind (and whether a new Change Job is cleaner than Rescind). Management literacy includes refusing Cancel on completed work.

Security and Governance of Management Actions

BP management is not unrestricted superuser theater. Effective operators need:

Exam trap: “Anyone in My Tasks can mass-cancel any process in the tenant.” False. Mass administration is privileged. Everyday approvers complete their tasks; administrators with proper domain and BP permissions perform cross-event recovery.

Document mass cancels and reassigns the way you document security activation—silent bulk actions without business approval create audit findings.

Common Confusions Table

Study Drill for T55

For any management stem, write four lines:

1. State: in progress or completed?
2. Scope: one event or many?
3. Action: view status / reassign / cancel / correct / rescind?
4. Root cause if stuck: assignee, parallel, subprocess, security, validation, integration?

That drill helps resolve older-guide T55 scenarios systematically and prepares the security-interaction diagnosis in the next section.