This document summarizes fixes introduced in the Accelerate Negotiation Guidance Package release version.
|
Version |
2.2.0 |
|---|---|
|
Release Date |
June 26, 2025 |
New Features and Improvements
|
New Feature Description |
ID |
|---|---|
|
The batch evaluation accepts undefined inputs for the source query and all the mapping fields. Default values from the model’s Definition step are used in such cases. |
PFPCS-9197 |
|
All calculations for the unit margin target are now available. |
PFPCS-9226 |
|
The Indicators tab in the Segmentation step displays the minimum set of field values needed to define a segment – typically including the product and customer fields. |
PFPCS-9230 |
|
The |
PFPCS-9231 |
|
Segment values are now displayed in the right panel under a new “Segmentation Level” section. |
PFPCS-9481 |
|
Default segmentation thresholds have been updated. |
PFPCS-9619 |
Fixed Issues
|
Bug Description |
ID |
|---|---|
|
Alignment optimization fails when the same product–customer pair appears in multiple segments. |
PFPCS-7552 |
|
Segmentation: Numbers in charts are improperly formatted. |
PFPCS-8118 |
|
In some queries, integer values are cast as text, causing subsequent calculations based on them to fail. |
PFPCS-9268 |
|
The Price Drivers calculation times out when processing datasets that are too large. |
PFPCS-9271 |
|
Segment score calculation fails when the segment’s average optimization target is zero. |
PFPCS-9342 |
|
The batch evaluation fails if only the first segmentation levels are provided, but the last ones are missing. |
PFPCS-9414 |
|
The default maximum bound of the optimization target is always 0.95 and cannot be unset, even for an optimization target of type “unit margin”. |
PFPCS-9451 |
|
Volume, profit, and revenue projections fail with a division by zero error when elasticity is zero. |
PFPCS-9487 |
|
Alignments without matching segment pairs cause the Recommendation portlet to throw a |
PFPCS-9507 |