3.17.2

Tomcat upgrade 10.1.40 (CVE-2025-31650)

The mapping of the transaction descriptor provided to PIE has been enhanced to also consider the parent merchandise hierarchy group(s) of an item, which were previously resolved by PCE.

The triggerIDQualifier in the RetailTransactionPromotionRecommendationFulfilledTrigger is optional by definition. However, it was marked as mandatory in the GK transaction DB model by mistake. Since it can no longer be marked as optional in a fully compatible way, it was decided that the PCE should always provide a non-null value to avoid issues when persisting transactions.

Therefore, from now on, the PCE provides a dummy value __N/A__ whenever there is no other meaningful value to be used in the RetailTransactionPromotionRecommendationFulfilledTrigger.triggerIDQualifier field. As a result, this field always contains a non-null value in GK contexts, regardless of which PCE API is used. This change does not affect the SAP ClientAPI format in any way.

Whenever a line item-related or result-related promotion price derivation rule which consumes one or multiple coupons is applied, the appropriate line item gets the coupon reference(s) (SaleReturnLineItemModifierCoupon). This entity has a field modifierSequenceNumber, which refers to the modifier added by that promotion to the given line item. If a single promotion price derivation rule produces two or more modifiers to the same line item and one or more coupon references, then all said coupon references will always refer to only one (the same) modifier in the scope of the given line item. After the correction, in such scenarios the coupon references will always refer the last modifier in the sequence that was created for the promotion price derivation rule, regardless of the type of promotion.

A regular transaction-related promotion with a threshold eligibility did not consider externally applied retail price modifiers coming from line item-related promotions. This bug has been fixed.

The maximum possible item price calculation has been corrected for return items which have a customer-specific price increase assigned. With the correction, the possible price increase is also considered for eligibility evaluation, in same way as for sold items.

PCE did not consider externally applied retail price modifiers that increase the price during eligibility validation. This could lead to some promotions not being applied. This bug has been fixed.