3.15.14

Accept the TriggerSequenceAddend for externally applied manual promotions

The TriggerSequenceAddend is now considered for externally applied manual promotions. This means that the next promotion that could be applied internally must have a sequence that is greater than the sum of the sequences from an externally applied promotion and the TriggerSequenceAddend.

Transaction-related discount proration improved

The discount share proration of transaction-related monetary discounts has been improved. Previously, if the adjustment amount to be assigned to the last item was found to be invalid by the validation logic, then the proration failed all together. After the adjustments, the remaining amount is assigned to the rest of the proration items or if it not possible for a remaining amount to be assigned to any item, it will be accounted for in the shared rounding amount.

Scaling numeric values in ClientAPI response

Scaling of all numeric values returned by PCE in the ClientAPI response has been improved so that their representation does not depend on actual values used during promotion calculation. Improvements include removing trailing zeros and setting an appropriate scale for specific values. The default minimum scale is:

• No digit after the decimal point for quantity-related values where integers are expected only (for example Sale.Quantity, AdditionalBonusDiscountLineItem.TotalGrantedQuantity or Coupon.AppliedQuantity)
• One digit after the decimal point for quantity-related values where decimals can be expected (for example Sale.Quantity.Units or PromotionRecommendationMissingTrigger.MissingQuantity)
• One digit after the decimal point for amount-related values (for example RetailPriceModifier.ComputationBaseAmount or PromotionRecommendationMissingTrigger.MissingAmount)
• One digit after the decimal point for points-related values (for example FrequentShopperPointsModifier.PointsAwardedAmount)
• One digit after the decimal point for rounding-related values (for example RetailPriceModifier.Rounding)

If the actually returned value contains more valid digits after the decimal point than defined by the minimum scale above, then all of those digits are returned.

Due to this improvement, many expected values in the existing JBehaves have to be corrected. The full list of necessary changes is located in the subpage JBehave Changes for 3.15.14.RELEASE.

Refactor the LineItemRelease NotesValues

Refactoring has been performed to not mix the usage of fields appliedQuantity and calculationBaseQuantity. The logic that handles the BuyNGetM topic has been moved from AbstractRebateDistributionService to the implementation of AbstractNormalizedItemModifierCreator.