Feature/Notable Change | Related Services |
---|---|
Introduced ability to execute capture & refund payment transactions in preferred orders for fulfillment & return interactions |
|
Improved durability of order-generating CheckoutCompletionListener to better handle cases where the event is handled multiple times due to the server going down |
CartOperationServices |
Updated fulfillment, cancellation, & return interaction workflows to support async payment transaction results |
PaymentTransactionServices |
Issue |
---|
Fixed bug where the fulfillment total for the fulfillment items is zero was causing all shipping cost proportions to be 0% |
Fixed NPE where order item is null for dependent items and offerRef is null for bundled product adjustments |
Added rounding logic for OrderFulfillmentItem#getMerchandiseRefundAmount() to fix an issue where the return amount is incorrectly calculated when the items are returned one by one |
Fix issue where PaymentRefundPackage’s payment version becomes out-of-date while processing multiple refund payment transactions for the same payment |
broadleaf.orderoperation.service.payment.capture-payment-gateway-priorities
Description: A list of payment gateway types defining the order by which payments will be captured.
broadleaf.orderoperation.service.payment.refund-payment-gateway-priorities
Description: A list of payment gateway types defining the order by which payments will be refunded.
broadleaf.orderoperation.async-payment-transaction-support.enabled
Description: Declares if components required to handle asynchronous capture and refund payment transactions are enabled. This should only be enabled if your project includes a payment gateway that only returns capture and refund transaction results asynchronously.
Default value: false