Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 19 additions & 7 deletions modules/ROOT/pages/exp-governance-create-strategy.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ Also decide whether you need validation-only monitoring or active runtime enforc
== Open the Strategy Workflow

. Log in and go to *Governance* > *Governance Strategies*.
. Select *Create Governance Strategy* to start the setup flow.
. Select *Create governance strategy* to start the setup flow.

The setup flow guides you through type, scope, rules or policies, and activation.
The setup flow guides you through type, scope, *What to Apply*, notifications, name and description, and review.

== Select Strategy Type

Expand All @@ -40,7 +40,7 @@ Configure scope criteria to identify the services that the strategy governs. All

Set these filters:

*Service Type*::
*Service Types*::
Select one or more service types to govern.

*Tags*::
Expand All @@ -64,22 +64,34 @@ Use *Preview Governed Scope* to see which services currently match your criteria

In the enhanced experience, your existing Anypoint profiles appear as controls. Controls offer expanded capabilities, such as governing new services and providing rules to control service and AI state behavior.

Depending on the strategy type, select the controls or policies the strategy enforces:
Depending on the strategy type, select the controls or policies the strategy enforces in the *What to Apply* step:

* For *Controls*, select controls from the catalog available in your tenant.
* For *Controls*, select controls available in your tenant.
* For *Automated Policy*, define runtime details such as gateway runtime, endpoint type, and environment.

Available options depend on your earlier selections and your organization's enabled products.

== Configure Notifications

Optionally configure automated conformance notifications for the strategy.

Set *Enabled* or *Disabled* for nonconformance notifications. When enabled, configure:

* *Recipients*: Select API Contact, API Publisher, or Others (specify email addresses).
* *Condition*: The notification triggers when the latest version of an API becomes nonconformant.
* *Channel*: Email.

You can change notification settings after the strategy is created.

== Name and Describe the Strategy

Enter a clear *Strategy Name*, such as "PCI Compliance Rules". Add a *Description* that states what the strategy enforces and why.

== Review and Activate

Review your selections: strategy type, scope, rules or policies, and general information.
Review your selections: strategy type, scope, rules or policies, notifications, and general information.

Select *Create and Activate Strategy*.
Select *Create Strategy*.

Strategies are active by default. To disable a strategy, go to *Governance Strategies*.

Expand Down