Recommended Item Rules

Both the Advanced Pricing Module (APM) and the FX CPQ modules 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.

Recommended Item rules suggest non-mandatory items but commonly paired with selected services. They help improve upselling opportunities and operational completeness without enforcing compliance.

Key Differences

Capability Advanced Pricing Module (APM) FX CPQ (Legacy)

Enforcement

Back Office and Mobile

Back Office only

Actions Supported

Required, Recommended, Prohibited, Override

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

  • Ensure recommended items exist in the price book with valid rates

  • Use clear conditions to avoid over-suggesting items

  • Combine Recommend Item with Override Price/Cost for promotional bundles

  • Test in Mobile to confirm recommendations appear as non-blocking suggestions

  • Validate sync profiles and staged data permissions for Mobile users.

Highlights

Advanced Pricing Module FX CPQ (Legacy)

  • Rules apply across Back Office and Mobile workflows.

  • Compliance actions include:

    • Add Required Item

    • Recommend Item

    • Prohibit Item

    • Override Price/Cost

  • Supports field-condition triggers for dynamic pricing and compliance.

  • Requires Mobile sync profile configuration to dispatch price books and staged data.

  • Rules apply only during quote creation in Back Office.

  • Focused on applicability and pricing overrides.

  • No support for prohibited or recommended actions.

  • Conditions limited to quote-level attributes (e.g., account, segment, geography).

Rule Evaluation Order

Rule evaluation order:

  1. Prohibited Item rules

  2. Required Item rules

  3. Recommended Item rules

Recommendations are informational only and never override required or prohibited enforcement.

Scope and Limitations

Recommended Item rules:

  • Do not enforce compliance.

  • Do not prevent ticket completion.

  • Do not auto‑add items to the ticket.

  • Are advisory only and can be ignored by users.

Use Required Item rules when regulatory, safety, or contractual enforcement is needed.

Step-by-Step Setup Guide

Complete these steps 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. Navigate to FieldFX Admin Tools → Conditional Pricing.

  2. Click New Rule.

  3. Define rule conditions, for example:

    • Service Type = "High-Pressure Pump"

    • Job Location = "Offshore"

  4. Continue with 3. Define Rule Actions.

3. Define Rule Actions

  1. Under Actions, select:

    • Recommend Item.

  2. Choose the item(s) from the price book to recommend when conditions are met.

  3. Optionally combine with other actions (e.g., Override Price/Cost).

  4. Save and activate the rule.

    See Rule Evaluation Behavior for details on how this rule will be evaluated in relation to other rules.

  5. Continue with 4. Configure Sync Profiles.

Rule Evaluation Behavior

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.

4. Configure Sync Profiles

  1. Configure sync profiles to dispatch updated price books and rules to Mobile.

  2. Continue with 5. Test Rule.

5. Test Rule

Test in Back Office and Mobile:

  • Verify that recommended items appear as suggestions during quote or ticket creation.

  • Confirm that technicians can accept or ignore recommendations without blocking ticket completion.

User Experience Behavior

Back Office FieldFX Mobile

Recommended items appear during quote or ticket editing.

Recommendations appear as non‑blocking suggestions.

Technicians can accept or ignore recommendations without validation errors.

Best Practices

  • Use recommendations for optional but value-added services or consumables.

  • Avoid overloading users with too many suggestions—keep rules targeted.

  • Document logic for audit and training purposes.

  • Use these rule naming conventions for consistent audits and troubleshooting:

    • Example: REC-Offshore-HighPressure-HoseKit for a rule that recommends a hose kit when the service is a high-pressure pump at an offshore location.

For more information, see:

FieldFX Documentation PTC ServiceMax Help Center Salesforce Documentation

Not Applicable

Not Applicable