Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
this This is available since version Godfather 8.0 (GodFather).

When the user users creates a new rebate agreement Rebate Agreement document, they always select of which rebate agreement type which Rebate Agreement Type the new document will bebelong to.

The rebate agreement type defines:

  • which Which logic to use for summary calculations of the rebate agreement Rebate Agreement header.

  • which logic will be used Which logic to use to filter the available Rebate Types , when the user is adding a new item to the agreement.

  • and which Which logic will build the approval workflow steps for the rebate agreementand which Rebate Agreement.

  • Which logic will build the approval workflow steps for the rebate recordRebate Record.

Configuration

The rebate agreement types Rebate Agreement Types are defined based on project needs , and their meta definitions must be stored in the version system together with other configurationconfigurations.

To configure a Rebate Agreement Type, navigate to page Rebates  Rebate Agreement Types.

Fields

  • uniqueName - serves – Serves as a unique identification of this type. This name will be used in the rebate agreement Rebate Agreement document as a foreign key, to identify the rebate agreement type usedRebate Agreement Type used.

  • headerFormulaName - name – Name of the logic used for building inputs and calculating results for the rebate agreement header, but Rebate Agreement header. It can also manipulate the items and folders.

  • workflowFormulaName - name – Name of the approval workflow logic , which will build the approval steps for the rebate agreement Rebate Agreement document.

  • recordWorkflowFormulaName - name – Name of the approval workflow logic , which will build the approval steps for the rebate recordsRebate Records.

  • rebateTypeFilterFormulaName - name – Name of logic , which will be used to filter the available Rebate Types , while when the user is adding a new item to the agreement.

  • configuration - configuration – Configuration (as JSON string) of the detail page. You can configure e.g the additional tabs on rebate agreement the Rebate Agreement detail page , which will show information in the form of a dashboard. See definition of the Dynamic Tabs for more details.

  • attribute1..30 - these – These fields are typically used as parameters for the rebate agreement Rebate Agreement logics - e.g. . For example, if two types of rebate agreement Rebate Agreements have the same majority of the item calculations the same, you can use a single logic (in this case likely probably for the header) , and when the logic is executed, it can read the rebate agreement type Rebate Agreement Type attributes to understand , which specific calculations it’s supposed to be doing on the actual it should do for the current document.