Broadleaf Microservices
  • v1.0.0-latest-prod

Admin Metadata Release Notes for 3.0.0-GA

Important Updates

Spring Boot Upgrade

  • As of Broadleaf Release Train 3.0.0-GA, all microservices have been upgraded to support Spring Boot 4.1 and Java 25.

Requirements

  • JDK 17 is required for Broadleaf release trains 2.0.0-GA, and beyond.

Notable Changes

Automatically Add Augmentations for Characteristics That Are Targetable in Rule Builders

Important
Requires Catalog Service 3.0.0 (Release Train 3.0.0)

What Changed

When a Product Characteristic is created, updated, or deleted, the Catalog Service now publishes a CharacteristicModifiedEvent message. The Metadata Service consumes this event and automatically creates, updates, or deletes the corresponding Metadata Augmentations (under the catalog:products:update container) based on whether the characteristic has been flagged as "targetable in rule builders."

Supported characteristic value types (STRING, DECIMAL/NUMBER, INTEGER, ENUM, BOOLEAN) are automatically mapped to their respective Admin UI field types, with ENUM values being dynamically populated as select options.

Benefits

  • Zero-Touch Automation: No manual creation or deployment of Metadata files to expose characteristics in rule-builders (e.g., target item rule builders for pricing, campaigns, or promotions).

  • Frictionless Syncing: Any changes to characteristic names, types, or enumeration values are automatically and dynamically synchronized with their corresponding Metadata Augmentations in near real-time.

  • Reduced Human Error: Eliminates the risk of misconfiguring JSON augmentation payloads or missing manual configuration steps during administrative updates.

How to Use

This feature works out-of-the-box with zero required code changes or manual configurations. * In the Admin Console: Simply enable the Targetable in Rule Builders option when creating or updating any Product Characteristic. The Catalog and Metadata services will handle the rest in the background. * Infrastructure Configuration: If you customize or override default messaging bindings, ensure that the Catalog Service output binding characteristicModifiedOutput and the Metadata Service input binding characteristicModifiedInputMetadata are both connected to the same messaging destination (defaults to characteristicModified).