Release 4.0.0-beta

[4.0.0-beta]

May 5th, 2023

New Features

The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting
enabled through integration with Optimizely Data Platform (ODP) (#474,#481,#482,#483,#484,#485,#487,#489,#490,#494).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex
real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important
for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can
be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and
make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.

This version includes the following changes:

• New API added to OptimizelyUserContext:
  • fetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.
  • When an OptimizelyUserContext is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.
• New APIs added to OptimizelyClient:
  • sendOdpEvent(): customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

For details, refer to our documentation pages:

• Advanced Audience Targeting
• Server SDK Support
• Initialize Java SDK
• OptimizelyUserContext Java SDK
• Advanced Audience Targeting segment qualification methods
• Send Optimizely Data Platform data using Advanced Audience Targeting

Breaking Changes

• OdpManager in the SDK is enabled by default, if initialized using OptimizelyFactory. Unless an ODP account is integrated into the Optimizely projects, most OdpManager functions will be ignored. If needed, OdpManager to be disabled initialize OptimizelyClient without passing OdpManager.
• ProjectConfigManager interface has been changed to add 2 more methods getCachedConfig() and getSDKKey(). Custom ProjectConfigManager should implement these new methods. See PollingProjectConfigManager for reference. This change is required to support ODPManager updated on datafile download (#501).

Release 3.10.3

[3.10.3]

March 13th, 2023

Fixes

We updated our README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack (#506).

Release 3.10.2

[3.10.2]

March 17th, 2022

Fixes

• For some audience condition matchers (semantic-version, le, or ge), SDK logs WARNING messages when the attribute value is missing. This is fixed down to the DEBUG level to be consistent with other condition matchers (#463).
• Add an option to specify the client-engine version (android-sdk, etc) in the Optimizely builder (#466).

Release 3.10.1

[3.10.1]

February 3rd, 2022

Fixes

• Fix NotificationManager to be thread-safe (add-handler and send-notifications can happen concurrently) (#460).

Release 3.10.0

[3.10.0]

January 11, 2022

New Features

• Add a set of new APIs for overriding and managing user-level flag, experiment and delivery rule decisions. These methods can be used for QA and automated testing purposes. They are an extension of the OptimizelyUserContext interface (#451, #454, #455, #457)
  • setForcedDecision
  • getForcedDecision
  • removeForcedDecision
  • removeAllForcedDecisions

• For details, refer to our documentation pages: OptimizelyUserContext and Forced Decision methods.

Release 3.9.0

[3.9.0]

September 16th, 2021

New Features

• Added new public properties to OptimizelyConfig. [#434] (#434), [#438] (#438)

  • sdkKey
  • environmentKey
  • attributes
  • events
  • audiences and audiences in OptimizelyExperiment
  • experimentRules
  • deliveryRules

• OptimizelyFeature.experimentsMap of OptimizelyConfig is now deprecated. Please use OptimizelyFeature.experiment_rules and OptimizelyFeature.delivery_rules. [#440] (#440)

• For more information please refer to Optimizely documentation: [https://docs.developers.optimizely.com/full-stack/docs/optimizelyconfig-java]

• Added custom 'closeableHttpClient' for custom proxy support. [#441] (#441)

Release 3.8.2

[3.8.2]

March 8th, 2021

Fixes

• Fix intermittent SocketTimeout exceptions while downloading datafiles. Add configurable evictIdleConnections to HttpProjectConfigManager to force close persistent connections after the idle time (evict after 1min idle time by default) (#431).

Release 3.8.1

[3.8.1]

March 2nd, 2021

Switch publish repository to MavenCentral (bintray/jcenter sunset)

Fixes

• Fix app crashing when the rollout length is zero (#423).
• Fix javadoc warnings (#426).

Release 3.8.0

[3.8.0]

February 3rd, 2021

New Features

• Introducing a new primary interface for retrieving feature flag status, configuration and associated experiment decisions for users (#406, #415, #417). The new OptimizelyUserContext class is instantiated with createUserContext and exposes the following APIs to get OptimizelyDecision:

  • setAttribute
  • decide
  • decideAll
  • decideForKeys
  • trackEvent

• For details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/v4.0/docs/java-sdk.

Fixes

• Close the closable response from apache httpclient (#419)

Release 3.8.0-beta2

[3.8.0-beta2]

January 14th, 2021

Fixes:

• Clone user-context before calling Optimizely decide (#417)
• Return reasons as a part of tuple in decision hierarchy (#415)