5.3 To-Do Steps, Checklists & Integration Steps

5.3 To-Do Steps, Checklists & Integration Steps

Quick Answer: The Business Process Framework orchestrates both human and automated operations through specialized non-approval step types. To-Do steps assign manual or off-system tasks (e.g., "Issue facility security badge") that require a user to acknowledge completion without updating Workday data fields. A To-Do placed before the completion step blocks event finalization, whereas a To-Do placed after the completion step allows the transaction to reach Successfully Completed while remaining an open inbox item. Checklists bundle multiple To-Dos and tasks across multiple assignees for major lifecycle transitions like Onboarding. Integration steps trigger automated data interfaces (such as EIBs or Document Generation) directly within the workflow. Service steps execute core background Workday logic (such as account provisioning) without human interaction.

---

To-Do Steps: Manual & Off-System Task Orchestration

Real-world enterprise business events often require actions that cannot be executed directly within Workday. For example, a new worker may require a physical office key, an external IT ticket may need to be created in ServiceNow, or an HR specialist may need to physically inspect Form I-9 identity documents. Workday models these external activities using To-Do steps.

Anatomical Structure of a To-Do Step

When an administrator configures a To-Do step, they define the following attributes:

1. Title: A concise description of the task (e.g., Provision Laptop and VPN Access).
2. Instructions: Detailed operational guidance, standard operating procedures (SOPs), or embedded hyperlinks directing the user to external ticketing portals or facility management systems.
3. Assignee: The security group or assignable role responsible for completing the task (e.g., IT Service Desk, Facilities Partner, HR Representative).
4. Due Date Calculation: An offset rule that dynamically calculates when the task must be completed (e.g., 2 business days after step initiation or 1 day prior to effective date).

No Database Field Mutation

A vital architectural characteristic of the To-Do step is that it does not mutate Workday database fields. When an assignee completes a To-Do in My Tasks, they simply click Done (or enter an optional confirmation comment). The system marks the step as Completed in the Process History, but no attributes on the Worker, Position, or Organization objects are modified.

Pre-Completion vs. Post-Completion To-Dos

The relative placement of a To-Do step in relation to the Completion Step fundamentally alters business process behavior and event status.

PRE-COMPLETION TO-DO: Blocks event completion
[Step a: Initiate] --> [Step b: To-Do (Verify I-9)] --> [Step c: COMPLETION STEP] --> [Successfully Completed]
                       ^ Process paused here;
                         Event remains 'In Progress'

POST-COMPLETION TO-DO: Non-blocking operational tracking
[Step a: Initiate] --> [Step b: COMPLETION STEP] ----> [Successfully Completed] --> [Step c: To-Do (Order Badge)]
                                                       ^ Event is complete;         ^ Remains open in inbox
                                                         Worker is active;            as an active reminder
                                                         DB committed

Pre-Completion To-Do (Blocking Behavior)

• Placement: The step order letter precedes the designated Completion step (e.g., Step b where Step c is Completion).
• Behavior: The business process event remains in In Progress status. The transaction will not finalize, database changes will not commit, and downstream staffing statuses remain pending until the assignee opens the To-Do and clicks Done.
• Use Case: Mandatory compliance checks that must be validated before employment legally takes effect (e.g., mandatory background check clearance or executive sign-off).

Post-Completion To-Do (Non-Blocking Behavior)

• Placement: The step order letter follows the designated Completion step (e.g., Step d where Step c is Completion).
• Behavior: Once Step c finishes, Workday immediately marks the business process event as Successfully Completed. All database updates commit, the worker's operational record becomes active, and payroll integrations can consume the new record. Meanwhile, Step d spawns independently in the assignee's My Tasks inbox as an active tracking item.
• Use Case: Administrative housekeeping tasks that should not delay the legal hire date or employee system activation (e.g., scheduling a 30-day check-in, ordering business cards, or enrolling in facility parking).

---

Checklists: Orchestrating Multi-Role Lifecycle Bundles

While a single To-Do step handles an isolated task, complex talent events involve dozens of coordinated tasks across multiple departments. Workday orchestrates these through Checklists.

Checklist Mechanics and Architecture

A Checklist is a coordinated framework that deploys a package of To-Do steps, document reviews, and self-service action tasks to multiple recipients based on worker attributes and lifecycle triggers.

• Multi-Role Distribution: A single onboarding event triggers distinct, concurrent checklist items to:
  • The Worker (Self): Complete emergency contacts, review the employee handbook, input direct deposit details, submit photo.
  • The Direct Manager: Assign a team onboarding buddy, prepare 30-day milestone objectives, schedule introductory 1-on-1s.
  • IT Support: Provision email credentials, ship mobile hardware, configure single sign-on (SSO).
  • Facilities: Program security badge, assign desk space, allocate parking permits.

Tracking and Auditability

Workday provides dedicated operational reporting dashboards (such as Track Onboarding, Checklist Status Report, and Workers on Leave) that allow HR Partners to monitor overall checklist completion percentages across hundreds of concurrent workers, identifying operational bottlenecks before a new hire's first day.

---

Integration Steps: Automating Downstream Systems

Modern enterprise HCM environments require continuous synchronization with external enterprise systems—including identity providers (Okta, Azure AD), third-party payroll engines (ADP, CloudPay), enterprise asset managers, and benefits carriers. Rather than relying on nightly batch batch-jobs, Workday embeds Integration steps directly into the Business Process Framework.

Two Primary Forms of BP Integration Steps

1. Automated Document Generation

Integration steps frequently trigger Workday's native Document Generation engine:

• When a Hire or Job Change event reaches the integration step, Workday automatically pulls transactional metadata (e.g., Worker Name, Title, Base Pay, Start Date, Sign-on Bonus) into a pre-configured template (built via Workday Docs or BIRT).
• The engine renders a secure, unalterable PDF document (such as an Employment Offer Letter or Non-Disclosure Agreement).
• The workflow immediately passes the rendered PDF to an integrated eSignature step (utilizing native Workday eSignature, Adobe Acrobat Sign, or DocuSign) for electronic worker signature.

2. Enterprise Interface Builder (EIB) Outbound Integration

An integration step can automatically launch an outbound Enterprise Interface Builder (EIB) or Workday Studio integration:

• Event Context Passing: The business process automatically passes the specific Event WID or Worker WID into the integration's launch parameters.
• Targeted Payload: The integration extracts data specific strictly to the transaction that just occurred, generates an XML, JSON, or CSV file, and delivers it securely via SFTP, REST, or SOAP API to an external endpoint (e.g., immediately provisioning an account in Active Directory upon hire completion).

Synchronous vs. Asynchronous Integration Execution

Administrators configure how the BPF engine behaves while the integration executes:

• Synchronous (Wait for Completion): The business process pauses at the integration step until the integration completes its external handshake. If the integration succeeds, the BP advances. If the integration errors out, the BP halts, alerting the integration administrator.
• Asynchronous (Fire and Forget): The BP launches the integration job in the background and immediately advances to the next step without waiting for external confirmation.

---

Service Steps: Core System Automation

While Integration steps interact with external systems or generate documents, Service steps execute internal, automated Workday system processing.

The Anatomy of a Service Step

• Zero User Interaction: A Service step never routes to any user's My Tasks inbox. It generates no notifications and requires no human clicks.
• Engine Execution: When the workflow encounters a Service step, the core Workday application engine runs a specific calculation, establishes an object association, or creates a dependent business object in RAM.

Typical Delivered Service Steps

• Create Workday Account: Automatically provisions system login credentials, user names, and security profile links for a newly hired worker.
• Calculate Compensation Range Spread / Compa-Ratio: Re-calculates internal pay equity metrics and salary range positioning immediately following a compensation adjustment.
• Assign Default Pay Group: Maps a worker to their corresponding payroll processing group based on country, company, and pay rate type.
• Maintain Employee Contract: Updates contract expiration dates and legal staffing attributes in global jurisdictions.

---

Auxiliary Step Types Comparison Matrix

---

Common Exam Traps & Pitfalls

1. The Post-Completion Illusion: An exam question presents a scenario where a newly hired employee is actively working, receiving payroll, and logging hours, but the recruiter claims "the Hire process is not finished because the IT badge To-Do is still open." The exam tests your understanding that if the To-Do is configured post-completion, the business process event is already Successfully Completed; the open To-Do is merely an uncompleted tracking item.
2. To-Dos as Data Entry Tools: Workday certification questions frequently trick students by suggesting that an administrator can use a To-Do step to "prompt the manager to enter the worker's new bonus percentage." A To-Do cannot accept data inputs for business objects. Entering or editing business data requires an Action step.
3. Confusing Service Steps with Integration Steps: Service steps run inside Workday's core platform to manage internal records (like provisioning a user account). Integration steps connect outward to external systems or document formatting engines.