This page tells you what parameters can be changed afterwards without redoing deployment or configuration.
Here is some general advice on how to handle configuration Company Parameters:
-
All configurations work based on attribute ID. They do not work based on column labels (UI name) or label translations – meaning that you can change them freely.
-
Column names of sample data can be freely changed assuming that the configuration will be properly adjusted (data lookups may be configured based on column names).
-
Values of dynamically created Company Parameters can be changed without redeployment. They act as standard Pricefx Company Parameters. The full list can be found here. Values can be added/removed as needed. If the user wants to handle all products without fallback to another DependencyLevel, we recommend to have one value with an asterisk "*" on every key. It provides a fallback without leaving the scope of the current Dependency Level configuration.
-
Changing dynamically created Company Parameters requires caution, but can be done using a wizard.
-
PriceSettingConfig and other configuration CPs should be changed with extreme caution. Technically every configuration can be changed during the system run but changes can affect a lot of things. That is why you should be careful here and customers are not even recommended to do this on their own in PROD environments without testing changes on some QA instance.
-
Making changes to price setting levels might require creating new Price Lists / Live Price Grids (recalculating the old ones might not be sufficient). See Adjustments after Changing the CP PriceSettingLevel.