- v1.0.0-latest-prod
Fixed issue where updating the active end date would result in a NPE.
Fixed the MonetaryException issue when there are two offers (one which has applicable to items on sale as FALSE and the second which has applicable to items on sale as TRUE along with stackable as TRUE and having an offer currency which is not the same as system default) and both offers are applied to the same item.
Fixed issues where an OfferCodes were considered to be used multiple times when they should not.
OfferCodes will now count as being used once across an entire offer when applied in certain situations, preventing the maxUsesPerUser flag from triggering incorrectly. An example is when a single OfferCode is used across multiple items in a cart, it counts as a single offer usage.
Changed to count OfferCode usages based on OfferAuditDetail transactionReferenceId.
Previously, if an OfferCode was applied to an Order that has an ItemOffer applied to all items, one OfferAuditDetail is created for each use (which is expected), but when checking for OfferCode usages, it was counting all the OfferAuditDetails.
Fixed an issue where maxUsesPerUser wasn’t being correctly persisted for generated campaign codes and provided a default value for maxUsesPerUser on the domain.
Addressed backwards and forwards compatibility for Spring Boot 3.1.x and 3.2.x.
Updated the extensibility of many Jpa classes in Offer by formatting them in line with other calls to the getManagedType() method.