Price Setting Package 2.3.0

This document summarizes fixes introduced in the Accelerate Price Setting Package release version.

Version

2.3.0

Release Date

Jul 9, 2024

In this document:

Upgrade Notes

  • Default dependency mapping has been disabled; i.e. in the DependencyMappingConfig PP the Type is now set to None for new installations. However, dependency columns in the data are kept as unused and old configurations are still valid. (PFPCS-5322)

  • Custom Engines: Removed the distinction between static and dynamic parameters in AdditionalCalculatorParameters; all parameters must now be closures for dynamic execution. (PFPCS-7297)

  • The internal components of the wizard have been reworked, so if you have a customized wizard, it will not work after you upgrade. (PFPCS-7854)

  • Description has been added to most of the tables. This is just QoL change, however it is too big to be stated as Manual Change.

Manual Changes

After finishing the upgrade:

  • Go to Price Parameters PriceSettingConfig and update keys from “Independent Manual Override Allowance” to “Parent Manual Override Allowance”.

  • Go to Price Parameters PriceSettingConfig and update keys:

Old key

New key

Old key

New key

Independent Manual Override Allowance

Parent Manual Override Allowance

Attribute

Name

Label

Attribute

Name

Label

attribute2

ParentLevelOnly

Parent Level Only

attribute3

ParentLevelPriority

Parent Level Priority

  • Update attribute’s name of the StrategySelection Price Parameter:

Attribute

Name

Label

Attribute

Name

Label

attribute29

Prioritize Parent Level Price

Prioritize Parent Level Price

  • If you have added a custom parameter in the price list logic, check it and update based on .

  • There is a new feature “Configurable Lookups”. Go to Price Parameters and create LookupConfiguration with JSON type.

    • It needs to have these columns:

      • key1Field

      • checksConfig

      • customFilter

      • selectedFields

      • userSourceName

      • userSourceType

      • isUsingDependencyLevelHierarchy

      • sortByField

      • key2Field

      • key1Transformation

      • key2Transformation

    • Entries of this PP can be filled by going through each PSP wizard. For more complex implementations, follow .

    • Standard config of previous versions of PSP is reflected by this file

  • Some of PriceSettingConfig configuration has been moved to LookupConfiguration – now it can be removed from the original table:

    • Cost,* can now be removed

    • Price Exception,* can now be removed

    • Strategy Exception,* can now be removed

    • Rounding Rules,* can now be removed

    • Stock,* can now be removed

    • Actual Price,* has changes

      • If value of attribute2 was “PX”, now it should be renamed to ConfigurableLookup.

      • Every value after attribute2 can be cleared.

  • CostTypeDefinition PP – Part of the Advanced Cost module has been changed. Now it points to the LookupConfiguration table where lookup is defined. New columns are:

    • attribute1: CalculationEngineSuffix

    • attribute2: Type

    • attribute3: CalculationMethod

    • attribute4: LookupName

    • attribute5: DependencyField

    • attribute6: DependencyType

    • attribute7: MappingSourceField

New Features and Improvements

New Feature Description

ID

New Feature Description

ID

Default dependency mapping has been disabled; i.e. in the DependencyMappingConfig PP the Type is now set to None for new installations.

PFPCS-5322

Configurable Lookups: There is now a lookup framework that allows you to define PX/PP/PCOMP lookups in a Price Parameter table, enabling you to modify existing lookups without any Groovy coding and add new ones with minimal Groovy required.

PFPCS-5968

Strategy Designer configuration has been moved to a separate repository and now functions as a dependent package to PSP.

PFPCS-6941

Custom Engines: Removed the distinction between static and dynamic parameters in AdditionalCalculatorParameters; all parameters must now be closures for dynamic execution. 

PFPCS-7297

To make PSP work well with EngineCalulator, the calculatePrice method of engines returns now a Map (instead of BigDecimal). 

PFPCS-7462

STRATEGY_RESULTS key has been added as an optional parameter for the Engine calculator. It is a list of maps where each map represents a value returned from the calculate() function. This key allows for composite pricing strategies and optional final price selection based on previous strategy results. Additionally, it introduces the option to reverse the order of strategy calculations, ensuring the most relevant strategy is considered.

PFPCS-7499
PFPCS-7808

The internal components of the wizard have been reworked, so if you have a customized wizard, it will not work after you upgrade. To be able to proceed with the upgrade, you need to agree that the wizard will override your custom changes.

PFPCS-7854

Tooltips have been added to configuration PPs to provide guidance to users.

PFPCS-7922

In the PriceSettingDimensions Price Parameter table, the following columns have been renamed to reflect their contents better:
Field Name column => Dimension
Dimension column => Dimension Type

PFPCS-7924

Implemented a new runtime fallback for StrategySelection to handle missing */*/* keys and products without defined strategies. Improved error handling and notifications for scenarios with no strategies or final prices, avoiding issues during bootstrapping.

PFPCS-8029

In PSP documentation, a new article on setting up a Custom Dimension Lookup has been added.

PFPCS-8032

The term "Independent" has changed to "Parent" in:

  • DependencyPriceListLogic

  • Price Parameters tables

  • Configuration wizard

PFPCS-8105
PFPCS-8106
PFPCS-8107

Fixed Issues

Bug Description

ID

Bug Description

ID

PSP deployment fails when CPQ is already deployed and has global preferences on the Product Cost table.

PFPCS-7923

There is a “zombie column” when the number of secondary keys decreases during bootstrapping.

PFPCS-8088

Fallbacks in hierarchic lookups do not work.

PFPCS-8292

When you open the wizard, select Core Module and click configuration, you get an error.

PFPCS-8346