Feature/Notable Change | Related Services | Links |
---|---|---|
Removed qualifier criteria from order and fulfillment group offers |
OfferServices |
|
Moved offer qualifier details to adjustments and use adjustments to represent offer target details |
CartOperationServices, OfferClient, OfferServices, OrderOperationServices, OrderClient, OrderCommon |
|
Updated offer proration type default value to |
OfferServices |
|
Added tiered discount support for order offer based on eligible discount cart subtotal |
OfferServices |
Added support for item criteria rules generated by fulfillment group item offer types when retrieving marketing messages |
Issue | Related Services |
---|---|
Updated marketing message resolver to avoid gathering marketing messages for offers without qualifier criteria |
OfferServices |
Fixed offer minimum subtotal and qualifying total requirements |
OfferServices |
Fixed index names for Oracle database changelogs |
AdminServices, AuthenticationServices, CartServices, CatalogServices, CustomerServices, ImportServices, JpaCommon, OfferServices, OrderServices, SandboxServices, SearchServices, TenantServices |
Fixed issues where the products are not distinguished as qualifier or target when building marketing message response |
OfferServices |
Added configuration to prevent benign exceptions during tests related to being unable to determine datasource route |
CampaignServices, OfferServices |
Fixed marketing messages NPE when product is on sale and offer does not apply to sales |
OfferServices |
Added logic to filter out marketing messages for offers that have been used the maximum times |
OfferServices |
Fixed issue with percent off tiered order offers |
OfferServices |
Fixed metadata configuration for default values and conditionals for free gift and voucher offers |
OfferServices |
Additions/Updates |
Removals |
|
|
The offer qualifier and target details were introduced in 1.6, but the payloads and the structure of the details are refactored in 1.7.
Since these payloads are only passed to CartOperationServices and OrderOperationServices and the payloads are never persisted in OfferServices, the data migration only needs to be considered for CartServices and OrderServices. For more details on the migrations, please see the CartServices release notes and OrderServices release notes.