---
title: What's New - Policies
description: Alert policies
documentId: whats-new-policies
locale: en-US
---

In previous versions of Flexible Actions, alerts were API-based.

To configure an alert for the same set of operations but for multiple APIs, it was necessary to create several alerts, one by one, for each API.

The concept of policies changes this scenario.
Now you can monitor multiple resources with just one registration.

<Callout type="tip" title="TIP">
[See how to configure a policy](/docs/flexible-actions/creating-runtime-alerts) and set the parameters that will trigger the alert and the APIs that will be part of this policy.
</Callout>

## Fixed or dynamic settings (All or Any)

The **All** and **Any** options define whether the policy is fixed (the characteristics that trigger the alert are always the same as you configured/edited) or dynamic (the characteristics are automatically updated when the API is updated).

- **All**:
  by selecting **all items of the API** (in Environment, Resource, and Operation) to be monitored by a policy, all these items selected at the time of policy creation or editing will be considered for triggering the alert. Items created after this definition will **not** be included in the monitoring.

- **Any**:
  by selecting **any item of the API** (in Environment, Resource, and Operation) to be monitored by a policy, any item will be considered for monitoring, including additions and changes that occur **after** the policy is defined.

Using the **Any** option gives greater dynamism to monitoring, as it will be automatically updated when new operations are created in the API.

The **All** option allows you to keep the monitoring parameters fixed as they were initially configured.
New additions to the APIs must be manually configured to be included in alert triggers.

<Callout type="tip" title="TIP">
See an [example of how to use the Any option](/docs/flexible-actions/creating-runtime-alerts#fixed-or- dynamic-settings-all-or-any).
</Callout>