Dev guideAPI Reference
Dev guideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In

Updating usage from older versions

This topic describes how to update from older versions of the Optimizely Full Stack Ruby SDK.

Decide and Track Event Code examples

This section provides code examples for how we recommend leveraging our new Decision and Event Tracking APIs. All existing methods and implementation are still included and supported and will only be removed after deprecation marking and with a future Major version.

We recommend adopting the new Decide, Decide All and Track Event methods as more flexible and easier to use replacements for cases where you currently use isFeatureEnabled, getFeatureVariable, getAllFeatures or Track calls within your implementation.

Refer to an earlier version of the SDK reference guides for earlier methods.

The following are some examples of how to migrate older methods to newer methods.

# -------------------------------
# Prereq for new methods: create a user
# ------------------------------
attributes = {"is_logged_in" => true}
user_id = "user_123"
user = optimizely.create_user_context(user_id, attributes)

# -------------------------------
# Is Feature Enabled 
# ------------------------------
# old method
enabled = optimizely_client.is_feature_enabled("price_filter", user_id)

# new method
decision = user.decide('flag_1')
enabled = decision.enabled

# -------------------------------
# Activate & Get Variation 
# ------------------------------
# old method
variation_key = optimizely_client.activate('my_experiment_key', user_id, attributes)
# new method
variation_key = decision.variation_key

# -------------------------------
# Get All Feature Variables 
# ------------------------------
# old method
all_var_values = optimizely_client.get_all_feature_variables('my_feature_key',
  user_id, attributes)
# new method
all_var_values = decision.variables

# -------------------------------
# Get Enabled Features 
# ------------------------------
# old method
enabled_features = optimizely_client.get_enabled_features(user_id, user_attributes)

# new method
decisions = user.decide_all([Optimizely::Decide::OptimizelyDecideOption::ENABLED_FLAGS_ONLY])
enabled_features = decisions.keys
# -------------------------------
# Track 
# ------------------------------
# old method
event_tags =  {"purchase_count" => 2}
optimizely_client.track('my_purchase_event_key', user_id, attributes, event_tags)

# new method
user.track_event('my_purchase_event_key', event_tags)

Activate method and A/B Tests

Like the existing Is Feature Enabled method, the Decide methods are based on feature flag keys, and do not support standalone A/B tests or Multi-armed Bandits. We are working to unify the data models and interfaces for our application longer term to mitigate the need to maintain multiple different access methods. In the meantime, you can still use the Activate and Get Variation methods for standalone A/B tests in your legacy projects alongside the Decide methods.