APM Rule Configurations

Rule configurations define how Advanced Pricing Module (APM) overrides are applied, including:

  • which records are affected

  • which fields are updated

  • what criteria trigger overrides

  • how multiple overrides are resolved

Rule configurations are divided into Records Updated by Overrides, Fields Updated by Overrides, Override Criteria, and Handling Multiple Overrides.

These configurations are set when defining override actions in the FieldFX Admin Tools → Conditional Pricing.

Ensure that:

  • The target fields exist on both Override and item objects

  • Rules are included in a Sync Profile for Mobile use

Use consistent API naming and limit the number of override conditions to improve performance and maintainability.

Records Updated by Overrides

Use the Applies to SObject field to define which record type the override applies to.

You can apply overrides to quote items, ticket items, or invoice items.

Back to Override Configurations

Fields Updated by Overrides

Use the Override Fields field to specify which field values are replaced when the override is applied.

Enter the API name of the field(s) to which overrides apply.

When entering the field API names, separate each value by a comma.

The field(s) you enter must exist on the Override object and the relevant item object.

Example 1. Example of Price object fields

Enter FX5__Price__c to apply overrides to the Price field on ticket items.

If you want to define your own overrides, you can use custom fields.

Custom fields must have the same API name on both the Override object and the target item object so that the system can correctly evaluate field mappings in the Filter Clause.

Back to Override Configurations

Override Criteria

Override behavior is applied in both Back Office and Mobile when the rule is included in a Sync Profile.

See Sync Profile Manager Admin Tool for more information.

The Filter Clause field contains the criteria that triggers overrides if a record meets the criteria.

You can set up overrides for any quote item, ticket item, or invoice item field.

The Override Criteria maps fields on the Override object to fields on the object to which overrides apply.

In APM, this logic is typically defined using rule conditions instead of manual clause expressions. The Filter Clause is primarily used for direct override matching.

These fields determine how the system evaluates and selects overrides when multiple records match the criteria.

Example 2. Mapping the Customer Account field on the Override object to the Customer Account field on the object to which overrides apply.

Consider the following example:

FX5__CustomerAccount__c==$FX5__CustomerAccount__c

The expression compares: * The field on the Override record (left side) * The corresponding field on the target item (right side, prefixed with $)

Structure

  • The first field is the Customer Account field on the Override object.

  • The second field is the Customer Account field on the object to which overrides apply.

  • You must separate the fields with a $ sign.

To require all conditions to match, use &&.

To match any condition, use ||.

Example: Matching by Catalog and Customer
(FX5__Catalog_Item__c==$FX5__Catalog_Item__c) && (FX5__CustomerAccount__c==$FX5__CustomerAccount__c)

The expression compares: * The field on the Override record (left side) * The corresponding field on the target item (right side, prefixed with $)

AND is also supported, but && is preferred. Lower case letters in the operator, such as and, are not supported.

To require items match an override in any of the specified fields, use the || function .

 
(FX5__Catalog_Item__c==null || FX5__Catalog_Item__c==$FX5__Catalog_Item__c) && (FX5__CustomerAccount__c==null || FX5__CustomerAccount__c==$FX5__CustomerAccount__c)

The expression compares: * The field on the Override record (left side) * The corresponding field on the target item (right side, prefixed with $)

Use || instead of OR (although it is supported). Lower case letters in the operator, such as or, are not supported.

Back to Override Configurations

Handling Multiple Overrides

You can apply multiple overrides to an item. To handle this, you must add logic to decide which override to use.

Complete the following fields to handle multiple overrides:

Field Description

Sort Clause

Enter the sort order of applicable overrides.

  • Enter FX5__Price__c DESC to sort overrides in descending order (highest to lowest) by price

  • Enter FX5__Catalog_Item__c, FX5__CustomerAccount__c to sort overrides in order by catalog item and then customer account

AVG, MAX, MIN, SUM

Enter AVG to use the average of all applicable overrides
Enter MAX to use highest applicable override.
Enter MIN to use the lowest applicable override.
Enter SUM to use the total for all applicable overrides.

Limit

Enter the number of overrides to consider:

  • "1" only if the first applicable override will be considered.

  • "5" only if the first five applicable overrides will be considered.

InAggregation

Select InAggregation when using aggregation functions such as AVG, MAX, MIN, or SUM in the Sort Clause.