Broadleaf Microservices
  • v1.0.0-latest-prod

Offer Release Notes for 1.7.5-GA

New Features & Notable Changes

Feature/Notable Change Related Services Links

Introduce validation to ensure offer’s currency is specified if any MonetaryAmount fields are defined

OfferServices

See Offer Validation Properties

Bug Fixes

Issue Related Services

Fixed currency mismatch issue when applying offer onto a cart in a locale that has different currency

OfferServices

Upgrade Guide

Configuration Properties

Added Properties

  • broadleaf.offer.service.validate-offer-has-currency

    • Description: Whether validations to ensure that Offer#currency is specified if any of its MonetaryAmount fields are defined, such as Offer#cartSubtotal, Offer#maxSavingsPerOrder, etc.

    • Default value: false

Method Signature Changes

Class/Method Description

DefaultOfferEngineResponseBuilder#getFulfillmentGroupResponse

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used

DefaultOfferEngineResponseBuilder#getItemResponse

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used

DefaultOfferEngineResponseBuilder#getItemResponseDetail

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used

DefaultOfferEngineResponseBuilder#getAdjustment

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used

DefaultOfferEngineResponseBuilder#addOrderCodeToAdjustmentIfUsed

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used

DefaultOfferEngineResponseBuilder#getItemAdjustment

Now takes in Codes instead of Set<String> codes, so that Adjustment#codeUsed is properly set when campaign is used