4.8 KiB
| id | title |
|---|---|
| strategy_constraints | Strategy Constraints |
Strategy constraints allow you to set preconditions on activation strategies that must be satisfied for the activation strategy to take effect. For example, you might want a strategy to only trigger if a user belongs to a specific group or is in a specific country.
Constraints use fields from the Unleash Context to determine whether a strategy should apply or not. You can constrain on both standard context fields and on custom context fields.
To be able to constrain on a field, it must be listed under the Context Field menu. If a field isn't listed, you can add it. See the section on defining your own custom fields for more info.
How to add strategy constraints
To add a strategy constraint, you'll need a feature toggle with a defined strategy.
Then, use the "add constraint" button in the UI, choose your context field, and the appropriate values that you wish to constrain it to.
Constraining on standard context fields
To constrain on a standard context field, choose the field you wish to constrain on. If the context field you want to constrain on isn't listed, you'll need to add it manually via the Context Field menu. Follow the procedure as if you were defining custom context fields, but give it a name that matches the desired field in the Unleash Context. Note that context fields are case-sensitive.
Constraining on custom context fields
If you need context data that isn't available in the default Unleash Context, you can also constrain on custom context fields. A common use case is a multi-tenant service where you want to use a tenant identifier to control the feature rollout. This would allow you to decide which users should get access to your new feature based on the tenant.
Defining custom fields
Starting with Unleash-enterprise version 3.2.28 customers can define their custom context fields via the user interface.
You can also define custom context fields to use with strategy constraints. We have seen customers use multiple variants of custom context fields to control their feature rollout, such as:
regioncountrycustomerTypetenantId
Combining strategy constraints with the gradual rollout strategy would allow you to do a gradual rollout to a specific segment of your user base.
Step 1: Navigate to “Context Fields“
Locate “context fields in the menu"
Step 2: Define new context field
Next you can define your new context field. The minimum requirement is to give it a unique name. In addition, you can give it a description and define legal values.
What are “legal values”?
To constrain what values a user can enter for a context field in the Unleash Admin UI, you can use legal values. This is a set of predefined values that show up as a dropdown
A context field's legal values are a set of predefined values that you can
define all possible values for that context field. These values appear in the Unleash Admin UI to guide users when working with context fields to make sure they only use legal values.
[Deprecated]: Constrain on a specific environment
Before Unleash 4.3, using strategy constraints was the recommended way to have different toggle configurations per environment. Now that Unleash has environment support built in, we no longer recommend you use strategy constraints for this. Instead, see the environments documentation.