Policy status aggregation in a multi-product release

reference brazil Updated Sep 10, 2026 1 min read dpr-policy-status-aggregation.md
Raw file servicenow.com

In a multi-product release, the policy run status of releases for all primary and included products are rolled up to the policy status of the main release.

Example of a policy status aggregation

Consider a release with a primary product or service and three related products. Each phase has policies mapped to it. You can run policies on the current phase from the main release or from an included product release.

Note: Removing a policy from an in-progress phase triggers automatic re-evaluation of the remaining policies. The aggregated policy status for the phase is recalculated based on the remaining policies.

When a product is added to a multi-product release after the release starts, the policy status of its phase is included in the aggregated status using the same precedence order. The release automatically advances to the next phase once all products, including newly added ones, are compliant.

The following table shows how the aggregated status is calculated from the status of each release.

Status for primary product or service Status for Included product 1 Status for Included product 2 Status for Included product 3 Aggregated status on the main release
In progress Compliant Compliant Compliant In progress
Not run Not run Not run Not run Not run
Not run Non-compliant Non-compliant Non-compliant Not run
Not run Compliant Compliant Compliant Not run
Non-compliant Compliant Compliant Compliant Non-compliant
Compliant Compliant Compliant Compliant Compliant
Compliant Compliant Compliant Compliant with exception Compliant with exception

Parent Topic:Digital Product Release reference

Search documentation
Search document titles and file paths on the brazil branch