5.3 Step Configuration, Order & the Completion Step

Workday Pro Platform Administrator Certification Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The Workday Platform

1.1 Workday Products, Functional Areas & Product Touchpoints 1.2 The Object Management Model & Business Objects 1.3 Navigation & Search Techniques 1.4 Organizations in Workday

2 Chapter 2: Tenants & Release Management

2.1 Tenant Types & Tenant Management Tasks 2.2 Releases, Adoption, System Testing & Support

3 Chapter 3: The Configurable Security Framework

3.1 Components of the Configurable Security Framework 3.2 Core Security Group Types: Workday-Assigned, User-Based & Role-Based 3.3 Advanced Security Group Types

4 Chapter 4: Security Policies, Assignment & Troubleshooting

4.1 Domain Security Policies & Permissions 4.2 Assigning Roles & Security Group Membership 4.3 Troubleshooting Security Access Issues

5 Chapter 5: Business Process Definitions & Steps

5.1 The Business Process Framework & Definitions 5.2 Business Process Step Types 5.3 Step Configuration, Order & the Completion Step

6 Chapter 6: BP Security, Condition Rules & Troubleshooting

6.1 Business Process Security Policies 6.2 Creating & Testing Condition Rules 6.3 Using Reports to Troubleshoot Business Processes

7 Chapter 7: Report Foundations & Custom Reports

7.1 Business Objects, Fields, Related Business Objects & Data Sources 7.2 Standard Reports, Custom Report Types & the Report Writer 7.3 Worklets, Dashboards & Sharing Reports

8 Chapter 8: Calculated Fields, Alerts & Report Administration

8.1 Identifying & Maintaining Calculated Fields 8.2 Configuring & Testing Alerts 8.3 Scheduling Reports, Report Groups & Transferring Ownership 8.4 Troubleshooting Report Data & Access Issues

9 Chapter 9: Integration Architecture & Security

9.1 Workday Integration Architecture & Web Services 9.2 Workday Integration Tools & Choosing the Right One 9.3 Integration System Users & Integration System Security Groups

10 Chapter 10: Enterprise Interface Builders

10.1 Creating & Launching an Inbound EIB 10.2 Creating & Launching an Outbound EIB 10.3 Troubleshooting EIB Data Loads & Access Issues

5.3 Step Configuration, Order & the Completion Step

Key Takeaways Explain This Topic AI

Business process steps execute in alphabetical order because Workday sorts letters, so letters rather than numbers are used for the Order column.

All business processes start with step a, the Initiation step, and additional letters such as a, b, ba, bb, c are used to insert steps into an existing order.

Per-step configuration is reached from each step's Related Actions while viewing the definition, and includes Maintain Step Conditions, Maintain Step Delay, Maintain Advanced Routing, and step label and help text overrides.

The completion step designates when data is committed and made available to other areas of Workday; all approval and review steps must come before it.

A business process can have only one completion step, and if none is set the process completes when the last step finishes.

Last updated: August 2026

Ordering is alphabetical, and that is deliberate

Configure the order in which steps execute using letters , because Workday sorts alphabetically . Workday explicitly recommends letters over numbers, and the reason is a sorting quirk worth remembering: with numbers, 10 and 100 sort before 2, and 2,000 sorts before 3 .

The conventions:

All business processes start with step a, the Initiation step.

Use multiple letters to insert new steps into an existing order. The sequence a, b, ba, bb, c runs in exactly that order.

Skip letters if necessary. a, b, d runs in that order.

Use all lowercase or all uppercase. Mixing cases complicates the order: lowercase-lettered steps list before steps with the same letter in uppercase, but they still run in parallel regardless of case. a Initiation ← always first, cannot be removed

b Action: Propose Compensation
ba Approval: Manager ← inserted later, runs after b
bb Approval: HR Partner ← and before c
c Service: Create Workday Account
d To Do: Submit W-4 ← letter skipped; still runs in order

Parallel versus sequential. Steps with the same order letter run in parallel . That is the mechanism for "the manager and the HR partner should approve at the same time" - give both steps the same letter rather than consecutive ones.

Per-step configuration

Much of business process configuration is done by editing the steps themselves. Each step has its own Related Actions menu , and you can configure a step while viewing the business process definition .

Configuration option What it does

Create Condition Rule Creates a condition rule and saves it to a library of rules. It does not add the condition to the step

Maintain Step Conditions Selects and applies a condition rule to the step
Maintain Step Delay Builds a delay in time before the next sequential step executes

Maintain Advanced Routing Prevents approvals on one's own behalf if the approver is the initiator, a prior approver, or the subject of the event

Maintain Step Label Override Defines a label overriding how the step displays in My Tasks
Maintain Step Help-Text Configures instructional text guiding users through the step
Set as Completion Designates the step as the completion step

The two-task trap. Create Condition Rule and Maintain Step Conditions are separate operations. Creating a rule only adds it to the library; the step is unaffected until you apply it with Maintain Step Conditions . Administrators who create a rule and stop are the classic case of "I built the condition and the step still runs every time."

Advanced routing is a segregation-of-duties control

Maintain Advanced Routing prevents someone approving their own transaction when they are the initiator, a prior approver, or the subject of the event. It is the answer whenever a scenario says a manager was able to approve their own pay change, or an initiator approved the event they submitted. Because role-based groups derive from organization assignments, a manager can legitimately be a member of the approving group for their own event - advanced routing is the control that closes that gap.

Step delays

Maintain Step Delay builds a wait before the next sequential step runs. Use it to space a notification from the event, or to give an integration time to complete before a dependent step fires.

The completion step

The completion step designates when to save or commit information to Workday . Completion makes the data in the business process available to other areas of Workday - payroll, the general ledger, downstream integrations.

The rules:

All Approval steps and Review steps must come before the completion step.

You cannot have more than one completion step in a business process.

If there is no completion step, the business process is marked complete when the last step finishes.

The process may contain steps after the completion step , and the status becomes Successfully Completed once the completion step has finished.

Set it from a step's Related Actions > Business Process > Set As Completion .

The consequence that shows up in real tenants

Workday's own example: a person is listed as hired even if they have not yet done several new-hire To Do steps, as long as the completion step has successfully finished.

That is the whole point of the design - and the whole source of confusion. Post-completion steps are genuine steps that genuinely need doing, but the business outcome has already happened. a Initiation

b Action: Hire Employee
c Approval: Manager ┐
d Approval: HR Partner ├─ must be before completion
e Complete ★ COMPLETION ┘ ← worker is now "hired"
f Service: Create Workday Account
g To Do: Submit W-4 ← still outstanding, hire already committed
h To Do: Enroll in Benefits

Placement decides what "done" means:

Completion step placed... Effect

Too early Data commits before approvals have been given - which is why Workday forbids approval and review steps after it

Too late Downstream systems wait. Payroll or the general ledger does not see the transaction until every To Do is finished

Not at all The process completes only when the very last step finishes - usually not what anyone intended

Exam framing to expect: "A worker shows as hired but has outstanding onboarding tasks" is not a defect. It means the completion step is placed before those To Dos, which is normal and correct design. The defect version of that question is the opposite - "payroll cannot see the new hire until all onboarding To Dos are complete," which means the completion step is too late.

Testing a definition change

Prove definition changes in a nonproduction tenant before Production. A workable sequence:

Confirm what the type allows with Business Process Configuration Options .

Make the change with an appropriate effective date .

Verify the security groups you routed to are on the business process security policy - the Group prompt only offers groups that are.

Initiate a test event and walk it end to end, using proxy to act as each assignee.

Check the process against View Definition for the date you are testing, so you know which version you exercised.

Confirm the completion step fires where you expect and that downstream data appears.