...
Logic API
Logic Nature: rebateAgreementHeader
Logic Type: Calculation/Pricing
Execution Types:
Standard - standard execution of this header logic is done 2x, the executions being called phases. They have different purpose, so you must distinguish those executions in the code by checking, which execution it is right now:
pre-phase - the first execution called pre-phase - to create input fields on header, folders or items, and to create/remove the items/folders
post-phase - and second execution is called post-phase - to calculate summary info of items and store them on header, folder or items
Information provided to the logic
binding variables:
raProcessor: RebateAgreementBuilder
CAUTION: when using Classic or Unity non-React user interface, then during pre-phase, the
raProcessor.rebateAgreementView
will NOT contain values of Outputs. The only exception are "overridable" outputs. This limitation is because of performance optimization of amount of data being sent between user interface and backend.
Expected logic execution outcome
none - the results of the logic elements are not stored nor displayed anywhere (with exception when testing the logic in Studio)
content of
api.global
created by pre-phase header logic, will be persisted and available to the Rebate Item Logic, when calculating the line items
Setup
As you can have potentially more rebate agreement header logics, you must select the one, which will be used, when user is working with rebate agreement document.
This is done in Advanced Configuration Option called defaultRAHeaderFormula, the content of this option is the name of the header logic to be used.
The option can be also set up on page
, via setting Default RA Header logic, and then fetched to the project as configuration file....