When the user creates a new rebate agreement document, they always select of which rebate agreement type the new document will be.
The rebate agreement type defines
-
which logic for summary calculations of the rebate agreement header
-
which logic will be used to filter the available Rebate Types, when user is adding new item to the agreement
-
and which logic will build the approval workflow steps for the rebate agreement
-
and which logic will build the approval workflow steps for the rebate record
Configuration
The rebate agreement types are defined based on project needs, and their meta definitions must be stored in version system together with other configuration.
To configure, navigate to page .
You can look at the sample configuration file of Rebate Agreement Type.
Fields
-
uniqueName - serves as a unique identification of this type. This name will be used in the rebate agreement document as a foreign key, to identify the rebate agreement type used
-
headerFormulaName - name of the logic used for building inputs and calculating results for the rebate agreement header, but can also manipulate the items and folders.
-
workflowFormulaName - name of the approval workflow logic, which will build the approval steps for the rebate agreement document
-
recordWorkflowFormulaName - name of the approval workflow logic, which will build the approval steps for the rebate records
-
rebateTypeFilterFormulaName - name of logic, which will be used to filter the available Rebate Types, while the user is adding new item to the agreement
-
configuration - configuration (as JSON string) of the detail page. You can configure e.g the additional tabs on rebate agreement detail page, which will show information in form of a dashboard. See definition of the Dynamic Tabs for more details.
-
attribute1..30 - these fields are typically used as parameters for the rebate agreement logics - e.g. if two types of rebate agreement have majority of the item calculations the same, you can use single logic (in this case likely for header), and when the logic is executed, it can read the rebate agreement type attributes to understand, which specific calculations it’s supposed to be doing on the actual document.