You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Flexible Rollout strategy supports multiple options for stickiness, used to define how we guarantee consistency for a gradual rollout.
Today it support the following options:
default (Unleash chooses the first value present on the context in defined order userId, sessionId, random.)
userId
sessionId
random
We have now extended the protocol to support any field in the unleash context. In addition It can be any of the predefined context field, in addition to any custom properties the user has defined.
This means that the "stickiness" parameter in the strategy configuration can now be any field on the context, and the SDK should use the specified context field to calculate the "hash" which determine whether the activation strategy should evaluate to true or false.
How it looks in the UI:
Edge case:
If the specified context field is not specific the activation strategy should evaluate to false.
* move default to "default" and add default resolve from ctx
* userid/sessionid are now resolved from context
* Add quick info on configuring custom stickiness
The Flexible Rollout strategy supports multiple options for
stickiness
, used to define how we guarantee consistency for a gradual rollout.Today it support the following options:
default
(Unleash chooses the first value present on the context in defined order userId, sessionId, random.)userId
sessionId
random
We have now extended the protocol to support any field in the unleash context. In addition It can be any of the predefined context field, in addition to any custom properties the user has defined.
This means that the "stickiness" parameter in the strategy configuration can now be any field on the context, and the SDK should use the specified context field to calculate the "hash" which determine whether the activation strategy should evaluate to true or false.
How it looks in the UI:
Edge case:
To guide the implementation we have:
The text was updated successfully, but these errors were encountered: