1.2

Jun 8, 2023

There is now a warning that some transactions in the data have null values for the targeted metrics.

PFUN-13773

Is is possible now to define default mapping during the Accelerator deployment. Then you can just adapt the values if needed when defining a new model. 

PFUN-16354

There is a new chart “Quantity chart” which displays the relationship between optimization target and quantity.

PFUN-16614

Feature importance by permutation (on top of a Machine Learning model) has been introduced in Negotiation Guidance Model Classes – to allow users to rely on this value to get recommendation of segmentation dimensions.

PFUN-16654

To speed up the process of segmentation, there are now recommendations for segmentation attributes, including the order of the attributes.

PFUN-16716

To unify naming, in NG_Lib all elements have now the suffix "Utils" (instead of "Lib").

PFUN-17212

For better navigation, the "Owner" column has been added to the Data Profile step.

PFUN-17261

Percentile calculation is now more precise as 100 bins are used instead of 20.

PFUN-17899

The projected revenue impact has not been calculated correctly for discounts. To fix the issue, the following formula is now used: 
Projected revenue = Revenue / (1 - Current Discount %) * (1 - Projected Discount %)

PFUN-17952

To get a more realistic assessment and better understanding of the impact, there are now two new features:

• In Segmentation > Optimization Setup there are 'Strategy' inputs to define how the projected revenue has to be adjusted relatively to floor/target/ceiling.

• In Results > Impact there is 'Realization' input that is directly applied to the dashboard.

PFUN-18102

For better usability, Negotiation Guidance now displays Datamart field labels in all steps. Labels are typically much clearer to users than the field names (used previously).

PFUN-18214

To provide better guidance, there are now warnings if inconsistent values are used for revenue, margin and discount. 

PFUN-18262

It is possible now to calculate correlation between features. The output is feature interactions, shown as a table in Step 3. 

PFUN-18323

To be able to better assess the segmentation, there is now displayed segments count at each level of the segmentation tree - in the column "Number of segments" in the Segmentation Overview table.

PFUN-19342

In Step 2 on the Price Drivers tab, you can now select numerical price drivers (such as Quantity) and have their importance and correlations computed. This allows you to know the impact of different numerical values on your transactions, even if they cannot be used for Segmentation.

PFUN-19833

To show more clearly how reliable your metrics and importance measure are, in the Configuration step there is new information "Explained Variance".

PFUN-20397

In a segmentation model based on the Segmentation Model Class, in the step Segmentation on the tab Optimization Setup, there is a portlet called Segments that displays the table Segments. There is a checkbox for each row but it serves no purpose here. It should be removed.

PFUN-16327

When generating segments, those with negative or nul CoV were filtered out, so if they had children with positive CoV, then these children were not filtered out, leading to orphan segments. Segments with negative or nul CoV are now kept in the segmentation tree.

PFUN-16650

Segmentation fails with an  error: "Elasticity : Unable to calculate metrics based on elasticity. Please consider disabling such calculation. Cause: Execution of NG_Lib[CustomLib] timed out after 300 units."

PFUN-17383

In the first step, Definition, there are transactions in the scope and filtered-out transactions, depending on the defined filters. But there are some missing transactions that are neither in the transactions in the scope nor in the filtered-out transactions.

PFUN-17478

Once a Negotiation Guidance model is created and linked to a Datamart, it does not pick up new dimensions added to the Datamart. The new dimension is visible in the Data Profile tab along with the old ones, but not in the Price Drivers Setup tab.

PFUN-18193

Segmentation is not correct when dimensions with empty string values are used.

PFUN-18760

Segmentation Overview table is not properly sorted when there are more than 10 segmentation levels.

PFUN-18847

In some segments, during the Segmentation calculation, there is the error "value out of range: underflow". It is due to very small values in the SQL formula (around 1E-87).

PFUN-19299

Impact calculation was done at a segment level, using the target average in the segment and applying the strategy to it. As this was not optimal, the process has been completely modified to compute results and impact at transaction level.

PFUN-20263

When you use a batch query on an Negotiation Guidance model, the query does not work if the parameter otherFields is empty.

PFUN-20393