When the user adds a new contract item to the contract document, they always select of which contract term type the new item will be.
The contract term type defines
-
which logic will be used for calculation of the item of this contract term type,
-
and parameters, which can be used by that logic
-
Configuration
To configure, navigate to page .
The contract term types are defined based on project needs, and their meta definitions must be stored in version system together with other configuration.
Fields
-
uniqueName - the name, which will be used in the contract line item as a foreign key, to identify the contract term type used
-
label - the description, which is meaningful description of the process for a user, when they select the contract term type while creating new contract line item
-
formulaName - name of the logic used for calculation of the contract items. Note that this logic is not used for folders, their inputs or results can be calculated by the contract header logic.
-
attribute1..30 - these fields can be used as parameters for the contract term logics - e.g. if two contract term type logics have majority of the calculations the same, you can make single logic, and when the logic is executed, it can read the contract term type attributes to understand, which specific calculations it’s supposed to be doing on the actual item.
-
waterfallElement - you can use this field to keep the name of the waterfall element (don’t confuse it with a logic element), into which you plan to store the result value of the contract term type calculation in a waterfall (e.g. in a datamart field, or when you calculate a quote) This value is NOT processed anyhow automatically, it’s up to you when and how you will use the value.