Inside Activate
...
Grouped Services
Grouped Service - Separate Order Processes?
3 min
this document answers common questions about ordering behaviour for grouped services in activate overview grouped services allow multiple related services to be ordered and managed together through a single parent service the ordering behaviour for grouped services is intentionally constrained to ensure consistency and predictable workflow execution can a grouped service have a separate order process per child service? no the order process is defined and executed only on the parent grouped service child services within a grouped service do not support their own independent order processes why separate order processes are not supported allowing individual child services to run separate order processes would introduce ambiguity and increase the risk of inconsistent provisioning behaviour by enforcing a single order process at the parent level, activate ensures a clear and predictable execution flow consistent validation and approval handling reduced complexity in workflow design and support recommended approach design the order process on the parent grouped service to account for all required logic across its child services where conditional behaviour is required use activate expressions to branch logic within the parent order process evaluate selected child services or service options at runtime control downstream actions based on grouped service configuration this approach keeps grouped services aligned with supported design patterns and avoids unsupported workarounds