Required Item Rules: Advanced Pricing vs CPQ

Both modules (Advanced Pricing Module (APM) and FX CPQ (legacy) allow administrators to enforce contract logic by adding items automatically when certain conditions are met. However, the Advanced Pricing Module introduces broader compliance capabilities and Mobile enforcement that go beyond CPQ’s Back Office-only approach.

With Advanced Pricing you can ensure real-time compliance in the field, reducing missed billable items and enforcing contract rules at every stage of the quote-to-cash process.

When to Use Each Rule Type

Use APM Required Item rules when enforcement is needed in the field.

Use FX CPQ (legacy) rules only when quote-time guidance is sufficient.

Key Differences

The key differences between APM and FX CPQ (legacy) are summarized in this table:

Feature Advanced Pricing Module FX CPQ (Legacy)

Enforcement

Back Office and Mobile

Back Office only

Actions Supported

Required, Recommended, Prohibited, Override (with Mobile enforcement)

Required (via rule), Override

Conditions

Job/ticket-level + field conditions (e.g., temperature, pressure, waste type)

Quote-level only

Compliance

Prevents ticket completion without required items

No Mobile compliance

Setup Tool

Admin Tool – Conditional Pricing

CPQ Rule Engine

Highlights

  • These rules apply across Back Office and Mobile workflows.

  • They can have compliance actions that include:

Capability Advanced Pricing Module FX CPQ (Legacy)

Workflow coverage

Back Office and Mobile

Back Office only

Required item enforcement

Yes (blocks ticket completion)

Yes (quote-time only)

Recommended items

Supported

Not supported

Prohibited items

Supported

Not supported

Price or cost override

Supported (with Mobile enforcement)

Supported (Back Office only)

Condition scope

Job, Ticket, Ticket Item, and field conditions

Quote-level attributes only

Compliance actions

  • Add Required Item

  • Recommend Item

  • Prohibit Item

  • Override Price/Cost

Rule Evaluation Behavior

Required item rules are enforced after prohibited rules but before recommended or price override actions. Tickets cannot be completed until all required items are present.

Scope and Limitations

Required Item rules:

  • Enforce compliance

  • Prevent ticket completion without required items

  • Auto-add items to the ticket

  • Are mandatory and cannot be ignored by users

Use Recommended Item rules for optional but value-added services or consumables.

Step-by-Step Setup Guide

Complete these sections in order.

1. Confirm Prerequisites

Licenses

  • FieldFX Base Managed Package

  • FieldFX E‑Ticketing

  • Advanced Pricing Module (purchased separately)

Installed Components

  • Latest FieldFX Managed Package

  • FieldFX Mobile app with connected app configuration

User Permissions
System

API Enabled, Customize Application, View Setup and Configuration

Object Access

FX5__Price_Book__c, FX5__Price_Book_Item__c, FX5__Field_Rule__c, FX5__Field_Action__c, FX5__Staged_Data__c

Apex Class Access

all FX5 pricing and sync classes

Visualforce Page Access

all FX5 admin pages

Admin Tool Permission Sets

  • AdminTool_Conditional_Pricing

  • AdminTool_Price_Book_Rules

  • AdminTool_Sync_Profile_Wizard
Process

  1. Ensure there is an active Advanced Pricing Module license.

  2. You have correctly configured Price Books and items in Back Office.

  3. Sync Profile configuration for Mobile enforcement:

    • Job and Price Book Dispatch enabled

    • Staged data permissions validated for Mobile users

  4. FieldFX Managed Package and Mobile app installed and updated.

Continue with 2. Navigate to Conditional Pricing.

2. Navigate to Conditional Pricing

  1. In Admin Tools Dashboard, open Conditional Pricing.

  2. Click New Rule to create a pricing rule.

  3. Continue with 3. Define Rule Conditions.

3. Define Rule Conditions

  1. Select the narrowest context possible for the rule to avoid unintended rule execution across unrelated tickets or items:

    • Job-level, Ticket-level, or Ticket Item-level.

  2. Add conditions that trigger the rule:

    • Example: Waste Type = "Hazardous"

    • Example: Downhole Temperature > 200°F

      Conditions can include operational attributes, location, or service type.

Rule Evaluation Behavior

See Rule Evaluation Behavior for how required item rules are evaluated in relation to other compliance actions.

Continue with 4. Add Compliance Action.

4. Add Compliance Action

  1. Under Actions, choose:

    • Add Required Item.

  2. Select the item(s) from the price book to auto-add when conditions are met.

  3. You can optionally combine with other actions:

    • Recommend Item

    • Prohibit Item

    • Override Price/Cost.

  4. Continue with 5. Save and Activate the Rule.

5. Save and Activate the Rule

  1. Review the rule logic and linked items.

  2. Set the rule status to Active.

  3. Ensure the rule is associated with the correct price book.

  4. Continue with 6. Configure Mobile Enforcement.

6. Configure Mobile Enforcement

  1. Open Sync Profile Manager.

  2. Include Job and Price Book Dispatch.

  3. Validate staged data permissions for Mobile users.

    Sync profiles must push updated price books and rules to Mobile.

  4. Continue with 7. Test the Rule.

7. Test the Rule

Back Office Mobile

Create a quote and confirm required items auto-add.

  1. Create a ticket under the same conditions.

  2. Verify required items appear automatically and ticket cannot close without them.

What Users Experience

Back Office Mobile

See required items auto-added during quote or ticket creation.

Cannot complete a ticket if required items are missing.

Compliance messages explain why the item was added and what action is required.

Continue with 8. Document and Audit.

8. Document and Audit

  1. Maintain a reference sheet for rule conditions and linked items.

  2. Periodically review compliance actions for accuracy and business alignment.

Best Practices

  • Use Required Item rules only for contractually or safety-mandated items

  • Avoid combining too many required items in a single rule—use multiple targeted rules instead

  • Always test Mobile enforcement before activating rules in production

  • Document rule intent and conditions for audit and troubleshooting