Field-Condition Trigger Rules

Field-condition Trigger Rules allow administrators to enforce compliance and pricing logic based on real-world conditions captured at the job or ticket level. These rules automatically apply required, recommended, prohibited, or override actions when defined field conditions, such as temperature, pressure, or waste type, are met.

Field-Condition Trigger Rules are configured through the Conditional Pricing feature in FieldFX Admin Tools and apply only to Advanced Pricing Module (APM) environments.

Key Differences

Feature Advanced Pricing Module 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

Blocks prohibited items and prevents ticket completion if conditions are violated

No support for prohibited actions

Setup Tool

Admin Tool – Conditional Pricing

CPQ Rule Engine

Highlights

Advanced Pricing Module FX CPQ (Legacy)

  • Rules apply across Back Office and Mobile workflows.

  • Compliance actions include:

    • Prohibit Item (blocks item addition)

    • Add Required Item

    • Recommend Item

    • Override Price/Cost

  • Supports field-condition triggers for dynamic 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).

When to Use Field-Condition Trigger Rules

Use Field-Condition Trigger Rules when:

  • Compliance must be enforced during job execution

  • Mobile users must be blocked from adding prohibited items

  • Pricing or cost depends on real-world measurements

Common Use Cases

  • Enforce mandatory handling or safety items when field conditions exceed defined thresholds

  • Prevent the use of non-compliant or restricted items under hazardous operating conditions

  • Automatically adjust pricing or cost based on real-world measurements captured in the field

  • Require specialized services or materials when environmental or operational limits are met

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:

    • Example: Temperature > 200°F

    • Example: WasteType = Brine

  4. Continue with 3. Define Rule Actions.

3. Define Rule Actions

  1. Under Actions, select:

    • Prohibit Item, Add Required Item, Recommend Item, or Override Price/Cost.

  2. Enter details:

    • For override, specify target fields (Price or Cost).

    • Input override values or formulas (e.g., Price = 150, Cost = 100).

  3. Save and activate the rule.

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.

Continue with 4. Configure Sync Profiles.

4. Configure Sync Profiles

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

  2. Validate that staged data permissions are correct for field users.

  3. Continue with 5. Test the Rule.

5. Test the Rule

Test in Back Office and Mobile:

  • Create a sample job or ticket that meets the defined conditions.

  • Verify that compliance actions (e.g., prohibited or required items) behave as expected.

  • Confirm that overridden pricing appears correctly.

Continue with 6. Document and Audit.

6. Document and Audit

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

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

Example Scenario: Enforcing Brine Waste Handling

A waste disposal job records a Temperature > 200°F.

  • When the condition is met, the system automatically:

    • Requires a High-Temp Handling Fee

    • Prohibits standard disposal items

    • Overrides disposal cost

  • Mobile users cannot complete the ticket until requirements are met

Troubleshooting

Issue Steps

Rule not firing on Mobile

  1. Verify sync profile includes updated price books.

  2. Confirm staged data permissions.

Pricing override not applied

Ensure rule priority does not conflict with another active rule.

Best Practices

  • Use clear naming conventions for rules to simplify maintenance

  • Group conditions logically to avoid redundant overrides

  • Always define effective dates to prevent unintended enforcement

  • Test in a sandbox environment before deploying to production

  • Document logic for audit and training purposes

  • Review rules quarterly

  • Disable deprecated rules instead of deleting them

  • Maintain an audit log of prohibited items and overrides