Yes. Sub-workflows are an established IdentityIQ workflow-design mechanism for decomposing a large business process into smaller, reusable units. Instead of placing provisioning, approval, initialization, policy-checking, notification, and other logic into one oversized master workflow, an engineer can move logically independent functions into workflows designated as Subprocess workflows. The parent workflow then invokes those subprocesses at the appropriate processing steps.
SailPoint specifically identifies simplification of the master workflow as one of the benefits of subprocess workflows. The design also improves maintainability because individual subprocesses can be understood, tested, modified, and reused independently. Reusability is particularly important in Lifecycle Manager implementations because several business processes can require the same approval, provisioning, or initialization behavior. IdentityIQ workflow steps can use a Subprocess action to launch another defined workflow and wait until it completes. Variables and results can also be exchanged between parent and subprocess workflows.
The statement is therefore technically correct: subprocesses are not merely permitted; breaking complex workflows into manageable reusable components is a core reason for using them.
References/topics: IdentityIQ Engineer — Workflow Basics, subprocess workflows, master workflows, reusable business processes, Workflow Step action types.
=======
