Content Comparison

...

• groovyLibraryName – name of the library that stores the Activated Formula Types Calculation Methods Groovy Code.

• customBlocksGroovyLibraryName – name of the library that contains definitions of Custom Blocks (functions).

• customInputBlocksGroovyLibraryName – name of the library that contains definitions of Input Blocks.

• deploymentLogicName – name of the logic that runs after the Formula Type has been Activated, this logic creates all necessary Company Parameter tables and deploys the Calculation Methods.

• excludedParameters – unsupported

• additionalInfoFields – defines additional connectors to the result block. This allows introduction of new fields that can be returned from the calculation method, for example, to be saved on Condition Records.

• additionalParameters – defines additional calculation parameters that can be passed to the calculation engines. Remember that the calculation parameters need to be assigned to the engine first (see How to Add New Calculation Parameters to Calculation Engines).

...

If there are any inputs used by the Formula Type, then their respective Input Generation tables need to be created. This process follows the same principle as for regular inputs.

1. First the Input Generation table is created by following the pattern defined by: libs.AGR_ProcessingLib.ConstConfig.FORMULA_DESIGNER_CONFIG.INPUT_GENERATION.PRICE_PARAMETER.NAME_PATTERN, which by default is AGR_YourFormulaName_InputDefinitions.

2. The Input Generation table is filled based on the meta of the Input block.

   1. An important step is that the meta block is saved as one of the attributes of the table. This allows meta to be accessed by the generation function of the input, which can be handy.

   2. Meta is also extended by two additional entries: inputId and params (which are user-filled values).

...