Override Engine (APM Rule Evaluation)

The Override Engine is part of the Advanced Pricing Module (APM), which replaces legacy FX CPQ functionality. If you’re currently using legacy FX CPQ features, we recommend transitioning to APM and the Override Engine to take advantage of the latest features and improvements.

Override rules are one of several rule types available in APM. Other rule types (such as Required Item, Recommended Item, and Prohibited Item rules) may also affect item behavior.

Introduction

In Advanced Pricing Module (APM), the "Override Engine" refers to the rule evaluation system that applies pricing and enforcement logic based on defined rules. Override rules are one type of rule within this framework.

In APM, price and cost adjustments are applied using rule-based logic that evaluates defined conditions.

This feature helps enforce pricing rules and apply consistent pricing behavior based on defined conditions.

APM uses a rule-based framework where different rule types determine how pricing and item behavior are enforced.

Prerequisites

To use the Override Engine, you need to:

Have these user licenses Have these permissions Complete these tasks and review these topics before continuing

In Mobile deployments, rules apply only when required data (such as price books and rule conditions) is included in sync profiles.

Price/Cost Override Rules

Price/Cost Override rules define how item pricing is adjusted when specific conditions are met.

APM uses rule types, including price and cost override rules, to determine how item pricing is adjusted when specific conditions are met.

Example 1. Examples

  1. Apply a cost override rule when a job is in a remote location.

  2. Apply a price override based on the rule’s effective and expiration dates.

You can apply override rules to quote items, ticket items, and/or invoice items.

Override rules evaluate defined conditions and adjust pricing when those conditions are met.

Rule Evaluation Behavior

The following section describes how APM evaluates rules and determines which actions to apply.

When a job, ticket, or ticket item meets the defined rule conditions, FieldFX automatically evaluates all applicable Advanced Pricing rules. Each rule’s actions (such as pricing adjustments, recommended items, or prohibited items) are enforced on the quote, ticket, or ticket item.

  • If multiple rules apply, each applicable action is evaluated independently, based on its configured conditions

  • Taxes and environmental fees are applied as separate line items on the ticket and invoice

  • If a rule includes a Prohibit Item action, that action takes precedence and prevents the item from being added

  • Required and prohibited actions are enforced before ticket completion

In FieldFX Mobile, applied pricing actions (such as taxes, fees, or prohibited items) are enforced automatically. Field users cannot remove or modify these actions unless their assigned role allows overrides.

Override Rules in the APM Rule Framework

Override rules define how item price or cost is adjusted when rule conditions are satisfied within the APM rule system.

Example 2. Example Override Rule Application

Updates to a price of a ticket item when a job is for a specific customer.

When a rule applies, APM evaluates the rule and applies the corresponding pricing or enforcement behavior.

Considerations

  • When a rule applies, the resulting action is enforced according to the configured rule behavior

  • When you add a new price/cost override rule:

    • Rule applicability depends on defined conditions, such as effective dates and the values on the record being evaluated

    • Rules are evaluated when relevant actions occur, such as item creation or updates

  • When you update a price/cost override rule:

    • The previous version of the override rule applies to items added before the rule’s effective date

    • The new version of the override rule applies to items added after that date.

How the Override Engine evaluates rules

The Override Engine evaluates rules during key record interactions to determine applicable actions, such as price or cost override rules. The following sections provide examples of how the Override Engine processes rules during different interactions:

Add an Item

When you add a quote item, a ticket item, or an invoice item, this happens:

  1. Add the item.

  2. Select a price book item.

  3. APM evaluates applicable rules and applies any resulting actions, such as overriding price/cost or enforcing item conditions.

  4. Save the item.

Process diagram showing how override rules are applied when adding an item

Update an Item

When you update a quote item, ticket item, or invoice item, this happens:

  1. Edit the item.

  2. Make changes.

  3. The override engine re-evaluates rules and applies any applicable rule actions based on the updated data.

  4. Save the item.

Graphical display of the process of editing an item

Update a Parent Record

When you update a quote, a job, a ticket, or an invoice, this happens:

  1. Edit a parent record.

  2. Make changes.

  3. Save changes.

  4. The override engine re-evaluates rules and applies any applicable rule actions based on the updated data.

  5. The updated items reflect any rule-driven changes after evaluation.

Graphical display of the process of editing a parent item

Recommended Reading