Configuration Options (Strategy Designer)
- Jana Volencová (Deactivated)
- Ioana Kocurova
Strategy Designer’s additional configuration is stored in its configuration JSON in the pfxExternalApp_visual_configuration_strategy_designer entry in the Advanced Configuration Options. The value is a JSON object.
A default configuration looks like this:
{
"name": "strategy-designer",
"label": "Strategy Designer",
"url": "https://apps.pricefx.com/visual-configuration/1-0-0/#/strategy-designer",
"businessRole": "StrategyDesigner",
"configuration": {
"advancedConfigurationStateEntry": "visual_configuration_psp_state",
"stateLookupTableName": "StrategyDesignerState",
"dependencyConfigurationTable": "DependencyConfiguration",
"priceListLogicName": "IndependentPriceListLogic",
"priceSettingDimensionsTable": "PriceSettingDimensions",
"strategyDefinitionTable": "StrategyDefinition",
"livePreviewDependencyLevel": "Global",
"groovyLibraryName": "CustomPricingStrategiesLib",
"customBlocksGroovyLibraryName": "StrategyDesignerCustomBlocks",
"excludedParameters": [],
"additionalParameters": {}
}
}
You can only specify the parameters you want to change. Others will use their default values.
Values of name, label, url, and businessRole are needed for Pricefx in order to display Strategy Designer in the menu.
name – Unique name among the external applications which will be part of the URL. Make sure it is unique among all
pfxExternalApp_entries.label – Text of the menu item. You can safely change this.
url – Points to the server where Strategy Designer is deployed.
businessRole – Specifies the business role that the user has to have assigned to see the menu item.
configuration – Application-specific configuration, in our case it contains the configuration options for the Strategy Designer.
Here is a list of options you can specify within the configuration object, with their default values and a description. A default value is used when you omit the option.
Option | Default Value | Description |
|---|---|---|
|
| Key in the Advanced Configuration Options where the deployed state of the Strategy Designer is stored. Change this if you want Strategy Designer to store its deployed state elsewhere, or load it from elsewhere. |
|
| Company Parameter where the draft state of the Strategy Designer is stored. |
|
| PSP table where dependencies are configured. Unless you have a custom PSP deployment, you should not need to change this. |
|
| Name of the PSP’s IndependentPriceListLogic. Unless you have a custom PSP deployment, you should not need to change this. |
|
| PSP table where dimensions are configured. Unless you have a custom PSP deployment, you should not need to change this. |
|
| PSP table where strategy definitions are configured. Unless you have a custom PSP deployment, you should not need to change this. This is where the custom strategies are written when they are deployed. |
|
| Default dependency level for the Live Preview. It became obsolete in version 1.0.0 where you can pick the level yourself from a drop-down. |
|
| Name of a Groovy Library which contains the custom strategies' generated code. It does not have to exist; it will be created during the first deployment. |
|
| Name of a Groovy Library which contains definitions of custom blocks. Learn how to define custom blocks in Create Custom Blocks in Groovy (Strategy Designer). |
|
| List of default PSP parameters you want to exclude. Specifying them will hide the blocks from the workspace. For details see Exclude Out-of-the-box PSP Parameters (Strategy Designer). |
|
| List of additional PSP parameters you want to see as blocks. Typically, you would need to specify any additional parameters you created in your customized PSP logic. For details see Include Additional PSP Parameters (Strategy Designer). |
Â