Broadleaf Microservices
  • v1.0.0-latest-prod

Release Notes for 1.7.2-GA


  • JDK 11 is now required for Broadleaf release trains 1.7.0-GA, and beyond.

New Features & Notable Changes

Feature/Notable Change Related Services Links

Introduced support updating ItemList name & attributes without also updating items

Introduced ability to execute payment transactions in a preferred order within the checkout workflow

Introduced endpoint to gather the set of available payment method options for your frontend checkout flow

Update the process used to reverse payment transactions related to incomplete/failed checkouts


Update checkout workflow payment activities to consider transaction amounts awaiting results. This is meant for payment gateway interactions, where the gateway leverages an async mechanism to provide transaction results - e.g. a webhook interaction.


Introduce the ability to lookup transaction results in the checkout workflow, following 3DS verification


Improve handling of CartFinalizationException, which can be thrown at the end of a successful checkout process

When updating or validating the cart, remove any cart items whose product is no longer active/present in the catalog.


Update how payment access restrictions are applied after a successful checkout


Move order and fulfillment group offer proration logic out of CartOps & into OfferServices


Bug Fixes


Fixed proration of fulfillment group adjustments when the group price is zero

Fixed adjustment amount for free-gift adjustments, so that it uses the item unit price, instead of the subtotal.

Upgrade Guide

API Changes

New Endpoints

Path Description

GET /checkout/{cartId}/payment-method-options

Get checkout payment method options

PATCH /item-list-ops/{listId}/name

Update ItemList name

PATCH /item-list-ops/{listId}/attributes

Update ItemList attributes

Configuration Properties

Added Properties

  • broadleaf.cartoperation.service.checkout.checkout-lookup-3ds-transactions-enabled

    • Description: Map of PaymentGatewayType to boolean, declaring whether to look up the results of pending 3DS transactions during the checkout workflow.

  • broadleaf.cartoperation.service.checkout.payment-gateway-priorities

    • Description: A list of PaymentGatewayTypes defining the order by which payments will be processed during checkout.

  • broadleaf.cartoperation.service.checkout.checkout-payment-method-options

    • Description: A list of configured payment method options that are available during checkout, declared in pairs of paymentMethodType & paymentMethodGatewayType

  • broadleaf.cartoperation.service.checkout.checkout-payment-method-validation-enabled

    • Description: Whether to validate payment methods during checkout activity workflow

    • Default value: false

  • broadleaf.cartoperation.cartprovider.send-rollback-event-uri

    • Description: The URI to send the checkout rollback event

  • broadleaf.cartoperation.cartprovider.send-checkout-completion-event-uri

    • Description: The URI to send the checkout completion event

  • broadleaf.cartoperation.paymentprovider.payment-transactions-uri

    • Description: The URI path for basic CRUD operations on payment transactions

  • broadleaf.cartoperation.paymentprovider.finalize-payments-uri

    • Description: The URI path for finalizing payments after checkout

  • broadleaf.cartoperation.paymentprovider.transfer-customer-payments-to-csr-uri

    • Description: The URI path for transferring a customer payment to a CSR

  • broadleaf.cartoperation.paymentprovider.transfer-csr-payments-to-customer-uri

    • Description: The URI path for transferring a CSR payment to a customer

  • broadleaf.cartoperation.paymentprovider.claim-transactions-for-request-uri

    • Description: The URI path to reset payment transaction reversal state

  • broadleaf.cartoperation.paymentprovider.lookup-3ds-transaction-result-uri

    • Description: The URI path to lookup 3DS payment transaction results from the gateway

New Permissions

There are new permissions and scopes for some service OAuth2 clients. Permissions and scopes can be added via admin or sql script.

See AuthServices release notes for more details.