1. Formula Designer: Custom Inputs Meta access refactored
The way Custom Inputs Meta are exposed to Formula Designer has been refactored. A new access point was introduced in the AGR_FormulaDesigner_Gateway library.
-
A new element
CustomInputsMeta.groovywas added to AGR_FormulaDesigner_Gateway logic.-
If your custom inputs logic defined in
customInputBlocksGroovyLibraryNamekey offormulaDesignerAdvanced Configuration is different than the default (AGR_FormulaDesigner_CustomInputs), you need to change the logic that this element calls.
-
-
Custom Inputs Meta logic was moved to
AGR_FormulaDesigner_CustomInputs/MetaUtils.groovy-
If you have any custom inputs defined, you need to move their definition from
Meta.groovytoMetaUtils.groovy. You can just copy-paste them; the map structure is unchanged.
-
-
The legacy element
AGR_FormulaDesigner_CustomInputs/Meta.groovywas removed. -
A new element
InputGenerationFunctions.groovywas added to AGR_FormulaDesigner_Gateway logic-
If your custom inputs logic defined in
customInputBlocksGroovyLibraryNamekey offormulaDesignerAdvanced Configuration is different than the default (AGR_FormulaDesigner_CustomInputs), ingetCustomInputMetadataByType()method, replace theAGR_FormulaDesigner_CustomInputs.MetaUtils.getCustomInputsMeta()lib call with your custom logic.
-
⚠️ Verify that your configuration does not reference the removed Meta.groovy element.
2. Formula Designer Live Preview: Input generation enabled
Manual configuration update required in formulaDesigner > Advanced Configuration.
After deploying AGR ACC 1.4.0, update the configuration as follows:
{
"groovyLibraryName": "AGR_FormulaDesigner_Formulas",
"customBlocksGroovyLibraryName": "AGR_FormulaDesigner_CustomBlocks",
"customInputBlocksGroovyLibraryName": "AGR_FormulaDesigner_CustomInputs",
"gatewayLibraryName": "AGR_FormulaDesigner_Gateway",
"gatewayLibraryElements": {
"livePreviewInputGeneration": "LivePreviewInputGeneration",
"customInputsMeta": "CustomInputsMeta"
},
"deploymentLogicName": "AGR_FormulaDesigner_Deployment",
"excludedParameters": [],
"livePreviewEnabled": true,
"additionalInfoFields": [
{
"name": "formulaDetail",
"label": "Formula Detail",
"type": "string"
}
],
"additionalParameters": {
"SKU": {
"label": "Product Id",
"type": "string",
"meta": {
"name": "productInput"
}
},
"CURRENCY": {
"label": "Currency",
"type": "string",
"meta": {
"name": "stringInput"
}
},
"UOM": {
"label": "Unit of Measure",
"type": "string",
"meta": {
"name": "stringInput"
}
},
"AGREEMENT_START_DATE": {
"label": "Agreement Start Date",
"type": "string",
"meta": {
"name": "dateInput"
}
},
"AGREEMENT_END_DATE": {
"label": "Agreement End Date",
"type": "string",
"meta": {
"name": "dateInput"
}
}
}
}
3. Update Warning Configuration
An issue was fixed where Agreements logic attempted to access the first element of an empty list, causing runtime errors.
-
Additional error handling was introduced.
-
A new warning configuration parameter is required.
Manual configuration update required.
Add a new value to AGR_WarningConfig Company Parameters table:
MISSING_HISTORICAL_CALCULATION_PERIOD_DATA,Missing Historical Period data. Please check "Calendar" Data Source and ensure data for the selected date range is available,,true,Yellow,false,,,,,,,,,,,,,,,,,,,,,,,,
-
Open AGR_WarningConfig Company Parameters table.
-
Add the following records:
-
MISSING_HISTORICAL_CALCULATION_PERIOD_DATA
|
Field |
Value |
|
Exception Code |
MISSING_CALCULATION_DATA |
|
Alert Message |
Missing Historical Period data. |
|
Solution |
Please check "Calendar" Data Source and ensure data for the selected date range is available. |
|
Origin |
|
|
Display in Matrix |
True |
|
Alert Type |
Yellow |
|
Aborts Calculation |
False |
See also: Warning and Error Messages