broadleaf:
orderoperation:
orderprovider:
summary-by-payment-id-subpath: ""
summary-by-payment-ids-subpath: ""
summary-by-fulfillment-id-subpath: ""
- v1.0.0-latest-prod
Support new concepts introduced to other services in the 2.2.0 Release Train
Add mechanisms to interact with InventoryServices to support preorder and backorder concepts. See the 2.1.0 Inventory Service release notes for more details.
A Preorder is an order for an item which has never had available stock but will become available at a later date.
A Backorder is an order for an item which has run out of stock but has plans to become available again at a later date.
This includes mechanisms to split the fulfillment if necessary and update the fulfilment for future-stock items to PENDING_INVENTORY
This includes mechanisms to set an inventoryLastUpdated attribute on fulfillments after inventory services emits a message indicating pending inventory may now be available.
This is surfaced in the admin metadata.
Ensure recurring/usage pricing details are passed between CartItem and OrderItem in DefaultCartOrderGenerationService
Updated the GET endpoints for retrieving a FulfillmentCaptureClaimSummary to utilize a new set of endpoints with discrete uri mapping. See the Order Service release notes for more details.
If you are updating Order Operation Services to version 2.1.0+ (Release Train 2.2.0+) but not Order Services, you will need to manually set the uri path properties of these endpoints to an empty string. This will call the old endpoints in Order Services.
The properties, once updated should look like:
broadleaf:
orderoperation:
orderprovider:
summary-by-payment-id-subpath: ""
summary-by-payment-ids-subpath: ""
summary-by-fulfillment-id-subpath: ""See the configuration documentation for more details.
Order items are now generated from the cart with additional pricing information, specifically the concepts of Recurring price and Usage price.
Recurring price will be utilized by an item that requires payment at an interval; e.g. a subscription.
Usage price will be utilized by an item that requires payment per some usage metric e.g. cost per API call for a website or usage of data on a phone plan.
See the 2.1.0 Pricing Service release notes for more details.
Update DiscriminatedProperties to utilize CaseInsensitiveMap when binding application and tenant ID property key prefixes
This ensures properties supplied via YAML vs environment variables are not treated as separate properties purely due to a case mismatch.
This affects OrderOperationPaymentProperties (broadleaf.orderoperation.service.payment.*)
Updated requests to ReturnOperationEndpoint to utilize application information to allow for Tenant level requests.
Fixed an issue with a null customer name which prevented billing addresses from being correctly persisted.
Fixed an issue with paged requests and responses not being correctly serialized and deserialized.
Fixed an issue where deeply nested (at least 3 levels) dependent order items were not correctly hydrating information, causing a null value for the Order Item’s refundAmount.