Configuration Options (Strategy Designer)
Strategy Designer’s additional configuration is stored in its configuration JSON in the strategyDesigner
entry in the Advanced Configuration Options. The value is a JSON object.
A default configuration (as of PSP 2.6) looks like this:
{
"groovyLibraryName": "CustomPricingStrategiesLib",
"customBlocksGroovyLibraryName": "StrategyDesignerCustomBlocks",
"excludedParameters": [],
"deploymentLogicName": "StrategyDesignerDeployment",
"livePreviewDependencyLevel": "Global",
"dependencyConfigurationTable": "DependencyConfiguration",
"priceListLogicName": "PSP_PricingLogic",
"additionalParameters": {
"SECONDARY_KEY": {
"label": "Secondary Key",
"tooltip": "Secondary Key",
"type": "string"
}
}
}
You can only specify the parameters you want to change. Others will use their default values.
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 |
---|---|---|
|
| 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). |
|
| The name of the Groovy logic is called by the Strategy Designer when a strategy is activated. This logic acts as a hook for the PSP to intercept the activation event. Its main responsibility is to update the StrategyDefinition PP, and it may also include additional custom code that is executed upon strategy activation. |
|
| Default dependency level for the Live Preview. It became obsolete in Unity v12 where you can pick the level yourself from a drop-down. |
|
| 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 pricing logic. Unless you have a custom PSP deployment, you should not need to change this. This logic is used by the Live Preview functionality. |
obsolete |
| PSP table where dimensions are configured. Unless you have a custom PSP deployment, you should not need to change this. It became obsolete in Unity v12 where strategy selection functionality was removed. |
|
| 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. |
|
| 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). |