Optimization - Negotiation Guidance 1.2.1
This document summarizes fixes introduced in the Accelerate Negotiation Guidance Package release version.
Version | 1.2.1 |
---|---|
Release Date | Jul 28, 2023 |
Fixed Issues
Bug Description | ID |
---|---|
In Step 4 Segmentation on the Optimization Setup, tab the strategy coefficients are not required but if they are not set, the optimization strategy cannot be applied. | PFPCS-6950 |
When Negotiation Guidance Accelerator was deployed from PlatformManager, the fields in the Definition step do not have values from the setting in PlatformManager (as they should). | PFPCS-6985 |
When calling the elasticity model, labels of the segmentation levels are used. But the Segments table still uses the segmentation levels names and so the batch query returns no value if some segmentation levels labels differ from their names. | PFPCS-6987 |
After deploying Negotiation Guidance 1.2, models built with version 1.1 return an error. | PFPCS-6994 |
Link to the Optimization - Negotiation Guidance documentation in PlatformManager does not work. | PFPCS-7002 |
The error "Cannot invoke method div() on null object" does not say which row/column is impacted or whether this concerns the whole Datamart. | PFPCS-7055 |
"Execute all next steps" functionality does not compute the configurator and so some required inputs are not computed. To fix this issue, every input will be given a default value. | PFPCS-7154 |
When Datamart contains a field with the same name as a column which Negotiation Guidance needs to create, you get an error. | PFPCS-7155 |
Â