Yes. Reusing appropriate standard Lifecycle Manager subprocesses is a sound IdentityIQ workflow-design practice because those subprocesses encapsulate established processing for common lifecycle and provisioning operations. Building every custom provisioning workflow entirely from scratch duplicates tested logic and makes future maintenance substantially harder.
SailPoint describes subprocess workflows as a way to divide complex workflows into smaller components that are easier to manage and can be reused by multiple master workflows. Standard LCM workflows make extensive use of this pattern for initialization, approval processing, provisioning, policy checking, identity-request handling, notifications, and related activities. A custom workflow can call an existing subprocess and provide the input/control variables required by that subprocess.
However, “as much as possible” does not mean blindly invoking every standard LCM subprocess. The engineer must understand the subprocess contract, including expected inputs, returned values, workflow variables, provisioning-plan assumptions, and release-specific behavior. Custom logic should only replace or extend standard processing when business requirements genuinely require it.
Therefore, leveraging standard LCM subprocesses where their behavior fits the requirement is a valid best-practice approach.
References/topics: IdentityIQ Engineer — LCM workflows, subprocess reuse, reusable business processes, workflow variables, provisioning customization.
=======
