Optimization - Negotiation Guidance 2.4.0

This document summarizes fixes introduced in the Accelerate Negotiation Guidance Package release version.

Version

2.4.0

Release Date

Mar 10, 2026

New Features and Improvements

New Feature Description

ID

You can now use Unit Price as an optimization target, including unit‑price–based segmentations and KPIs.

PFPCS-9227

Price Drivers Setup now shows a Dimension column so you immediately see which features are DataMart dimensions and can plan segmentation accordingly.

PFPCS-10007

The Segmentation → Indicators tab now displays a pooled Standard Deviation per level, plus a link to indicator definitions, making tree quality easier to assess.

PFPCS-10014

Negotiation Guidance now supports out‑of‑the‑box recency weighting of transactions, so fresher data can have more influence on recommendations.

PFPCS-10051

A new Review dashboard in the Results step provides a consolidated view of model quality and key metrics.

PFPCS-10056

The Indicators tab now opens by default in the Segmentation step, bringing the most relevant diagnostics to the front.

PFPCS-10065

A detailed Review dashboard in Results adds a metrics table and drill‑down charts, helping you analyze performance for specific segment levels.

PFPCS-10193

The Normal Distribution fit scatter chart is now color‑coded, so segments with poor fit stand out at a glance.

PFPCS-10252

The UI for configuring minimum values now provides one input per line, making complex setups easier to read and maintain.

PFPCS-10284

Unit Price target type now uses quantity as the default weight, aligning averages with typical business expectations.

PFPCS-10299

Floor, target, and ceiling values now use default weights when computing percentiles, keeping weighted metrics consistent across the model.

PFPCS-10300

Target recommendations based on score are refined so that the score more accurately drives the suggested target levels.

PFPCS-10338

Currency handling in Negotiation Guidance is improved, reducing issues in multi‑currency environments and Datamart scenarios.

PFPCS-10402

You can now use Price Index as an optimization target, enabling NG setups built around index‑based pricing.

PFPCS-10427

Editing in the Optimization Setup tab no longer triggers unnecessary auto‑refreshes, making configuration noticeably smoother.

PFPCS-10429

The Tree View Distribution and Optimal Target charts now rely consistently on default weights, preventing mismatches between charts and tables.

PFPCS-10432

For Margin % targets, the optimization engine now uses historical revenue as a constant weight, stabilizing weighted indicators across recalculations.

PFPCS-10433

When you duplicate a model, newly introduced advanced parameters are now automatically populated, so copied models are ready to run.

PFPCS-10447

Models using Datamart sources now benefit from stricter currency‑conversion validation, helping catch configuration issues early.

PFPCS-10478

The Distribution and Optimal Target charts are rescaled for clearer visuals, making it easier to interpret segment behavior and optima.

PFPCS-10547

Fixed Issues

Bug Description

ID

The divergence‑to‑normality indicator can report lower divergence scores for clearly non‑normal segments than for visually better‑fitting distributions.

PFPCS-7357

Price drivers calculation in Configuration fails with a “math domain error” when a selected text price‑driver field contains only "NA" or "N/A" values.

PFPCS-9087

Price gaps shown during configuration (Price Gaps / Selection Alignments) do not match the price gaps shown in Results/Recommendations for the same alignments and segments.

PFPCS-9533

Running the Configuration step without any segmentation dimensions selected shows a low‑level formula error instead of a clear validation message.

PFPCS-10165

In some Salesforce‑based Negotiation Guidance models, mapped Product ID and Customer ID fields are not detected, triggering warnings that product and customer hierarchies are missing.

PFPCS-10223

Creating the KPI table with CreateKPITable fails with a “Division undefined” error when some segCount values are zero.

PFPCS-10251

The Distribution chart uses the optimized Target average instead of the initial Target average as the mean, so the curve changes after optimization.

PFPCS-10253

Price drivers calculation fails with “cannot set WRITEABLE flag to True of this array” when processing large datasets (around 1.4M transactions).

PFPCS-10318

After copying a model, some Review/Results dashboards reference a field that no longer exists and display an “unavailable field in dashboards” error.

PFPCS-10417

For Discount % target type, values in the Impact Overview portlet are always zero because required discount‑based revenue measures are missing from the query.

PFPCS-10428

When user‑defined weights are configured, some target metrics in Tree View still rely on default‑weighted values, causing inconsistent averages and indicators.

PFPCS-10511

On core versions earlier than 16, the optimization post‑processing step updates the Transactions table without the Segment Name column, which clears existing segment names.

PFPCS-10540

The Projected Revenue x Target column in the Impact table uses Revenue x Target instead, so optimized opportunity metrics are incorrect.

PFPCS-10546

For non‑percentage optimization target types, the Optimal Target chart can pick an incorrect optimal target and render curves that do not match the actual target range.

PFPCS-10549

On core versions earlier than 16, internal use of a generic name column in segmentation logic conflicts with an existing Name column in the Transactions table and clears its values.

PFPCS-10557

Optimal target search for Margin % extends beyond the actual segment target range (for example above 100%), which causes “Unable to compute revenue from a margin % of 1.0” errors.

PFPCS-10588