In Workday, a subprocess is a step type used within a business process definition to initiate another, independent business process . The purpose of a subprocess is to trigger a set of predefined steps from a separate process that runs as part of the main (parent) process. This provides modularity and reusability across multiple BPs.
For example, when configuring a Hire process, you might add a Request Compensation Change subprocess to automatically launch once the hire is initiated. This avoids duplicating configuration work and ensures consistency in how related actions are handled across events.
Option A is incorrect because approvals are managed through Approval Steps , not subprocesses.
Option C is incorrect — background processes are system-managed and not user-configured through subprocesses.
Option D refers to To-Do or Notification Steps , which are informational, not subprocess-driven.
Thus, subprocesses are a way to embed or chain additional processes into an event flow, promoting flexibility and maintainability.
Reference (Paraphrased Source):
Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Subprocess Step Type and Configuration Best Practices.”
