Advanced Pricing Module Override Rules
This topic explains how to configure override rules, including rule configuration, null-value overview and override criteria.
|
Before configuring override rules:
|
Override rules are evaluated when APM processes pricing for quote, ticket, or invoice items.
Rule Configurations
For details about configuring APM rules, see APM Rule Configurations.
Overriding values with null values
Select the Apply Null checkbox to clear the value in a field when an item meets the override criteria.
Use this option when you want the override to remove an existing value instead of replacing it.
Overrides
Overrides define the conditions under which rule actions are applied, including optional date range constraints.
|
In APM, a single rule can include multiple actions, such as overriding price and recommending additional items. |
Override Criteria
You can set up overrides for any quote item, ticket item, or invoice item field. Override criteria map fields on the Override object to corresponding fields on quote, ticket, or invoice items.
In this example:
FX5__CustomerAccount__c==$FX5__CustomerAccount__c
This criteria maps the Customer Account field on the Override object to the same field on ticket items. See Customer Custom Field.
You can use the following standard fields in override criteria without additional configuration:
-
Catalog Item
-
Customer Account
-
Office
|
These fields are managed fields available on the Override, Quote Item, Ticket Item, and Invoice Item objects. |
You can also use custom fields in override criteria, provided the field has the same API name on both the Override object and the item object.
If you want to define your own overrides, use custom fields.
Date Ranges
You can limit overrides to a specific date range.
To configure a date range, enter values in the Effective Date and Expiration Date fields.
|
The Quote or Ticket’s Date field must meet both conditions:
|