Data Tracking Release Notes for 2.0.1-GA

Table of Contents

Important Updates

Now allows disabling only Catalog tracking based on the context info.
- This is to support reading Catalog entities that belong to a different type of Catalog (e.g., Search Group) during a request targeting Catalog entities for a different Catalog type (e.g., Product). An example of this is during Search Requests, where the Catalog on the request applies to Products not to Search Settings which must also be read to determine appropriate facets and sort options.
Workflow transition performance refactoring. See Workflow Transition Performance.
DefaultTrackablePolicyUtils now accepts sandbox-scoped requests with the authority ADMIN_SCOPED_SERVICE_CLIENT, intended to allow authenticated service clients to have access to sandboxable entities.
Added a BulkOperationContext to hold onto configuration properties for the current thread context.
- These properties in BulkOperationContextConfigurationProperties enable or disable entity validation and persistence messaging during entity persistence. These properties can either be set globally or per operation type for bulk operations.
  - broadleaf.tracking.bulk-operation.context.{global-default-config | set_some_operation_type}.entity-validation-enabled=false
  - broadleaf.tracking.bulk-operation.context.{global-default-config | set_some_operation_type}.user-sandbox-persistence-notification-enabled=false

Filter out unwanted classes during model mapper cache creation. These sometimes caused NoClassDefFoundError problems during application start.
Ensure cached singleton instance of JpaNotificationStateService is reset on Spring context refresh
Removed logic in SingleIndexRequestMessageFactory preventing indexing of global (non-application) sandbox changes. This supports use-cases such as Solr-powered admin views at the tenant level.