Overview
We wanted to clarify how the Affected Subsidiaries field works on Change Requests — specifically whether it populates automatically or requires manual input.
Description
No manual work needed! The Affected Subsidiaries field is automatically populated based on detected usage of the customizations in scope for the Change Request. If the platform can demonstrate that a customization is being used by a specific subsidiary, that subsidiary will be included in the field automatically.
Why does this matter? If your organization uses Subsidiary Approval Policies, this becomes even more powerful. Platform Governance lets you set subsidiary-specific approval policies so that when a change affects a subsidiary, the right approvers for that subsidiary are automatically included in the approval cycle — no manual tracking of who needs to sign off on what.
In short: the system identifies which subsidiaries are impacted, and your policies take care of routing approvals to the right people automatically.