Rebates Configuration Overview

This article summarizes of all of the configuration possibilities for Rebates.

Logics

Using logics you can implement all the rebates calculations you need.

  • Rebate Entitlement Filter logic, with Nature set to rebateAgreementEntitlementFilter

  • Rebate Template logic, with Nature set to rebateAgreementTemplate

Domain Model

The configured types of rebate agreements are stored in:

The configured types of Rebate Types / Condition Types are stored in:

The following entities are used to store data of the document and calculations:

See their relations in Rebates Entity Relationship Diagram.

The configured types of Rebate Agreement Templates are stored in:

  • Rebate Agreement Template (RAT)

  • Rebate Record Set Calculations (RRSC)

Advanced Configuration Options

There are many options, which can be set up in Configuration pages under Administration  Configuration and influence behavior of the application.

Values of those options are then stored in Advanced Configuration Options, which can be fetched to the project configuration files.

Feature Flags

Feature flags are settings in key-value form, which influences the application’s front-end behavior and appearance.

To change them, navigate to Administration  Feature Flags. Once modified, feature flags values are stored in advanced configuration option crm_config.

Approval Workflow

Both Rebate Agreement and Rebate Record are approvable documents, so they can have an approval workflow. For details see Approval Workflow Configuration Overview.

Access

You can configure access to:

  • List of Rebate Agreements, via:

    • Assignment of user roles

  • Detail of Rebate Agreement, via:

Interceptors

Interceptor is a mechanism developed mainly for integration of Unity UI with CRM systems. It allows the developer to enrich Unity UI with additional JavaScript code which is called pre or post certain actions.

Found an issue in documentation? Write to us.