Rule Manager

Prev Next

⚠️  DEPRECATION NOTICE

Rules Templates is being deprecated and replaced by Rule Manager. Migration is automatic.

Rule Manager enables you to manage rules across multiple queues efficiently from a single centralized location. It replaces the previous Rules Templates functionality, allowing you to view and configure all your rules and actions - whether they are shared across multiple queues or with just one specific queue - from one place.

Overview

The Rules Manager provides a comprehensive view of all rules configured within your organization. When you select a rule, you are presented with details organized into two main tabs:

  • Rules & Actions Detail: Configure the rule's conditions and actions (identical to how you would configure it on the queue level)

  • Linked Queues: Manage which queues the rule applies to, perform batch actions, and easily distribute the rule to new queues

Key benefits

  • Centralized management: Update rules across all queues from a single location

  • Consistency: Ensure identical rule behavior across multiple queues

  • Flexibility: Choose which queues to update while maintaining visibility of local modifications

  • Time savings: Deploy rules to new queues instantly without recreation

How to use Rules Manager

Step 1: Access Rules Manager

  1. Navigate to Settings > Rules Manager in your workspace

  1. You will see a list of all rules and actions across all your queues

  2. Click Add rule to create a new one, or click on an existing rule to edit it

Step 2: Configure the Rule

When creating or editing a rule, the Detail view offers the same configuration options found at the queue level (Identification, Conditions, and Actions).

Identification

  • Label: Short, descriptive name

  • Description: Detailed explanation of the template's purpose

Condition

  • Define conditions using TxScript

  • Use the AI Edit condition feature with natural language

  • The selected test queue provides context for field references

Actions

  • Add one or more actions to execute

  • Configure action-specific settings

  • Enable/disable actions as needed


NOTE

When creating a rule centrally, you may need to select a test queue to provide context for field validation.

Step 3: Test your rule

Use the Test rule section to validate your template against real documents from the selected test queue.

Step 4: Manage Linked Queues

Once your rule logic is defined, navigate to the Linked queues tab to determine where the rule will be applied.

This tab lists all the queues where the rule is currently present. Simply adding a queue to this list links the rule to it. You can also bulk remove Rule from the selected Queues.

To ensure the rule works correctly on the selected queues (which may have different schemas or field IDs), you must verify the configuration:

1. Add Queues: Click the Add queues button to select one or multiple queues where this rule should run

2. Validate the Rule: Click the Validate button in the top right corner. This triggers an immediate check of the rule's code against the specific configuration of each linked queue

3. Review Results: A "Validation" column will appear next to the queue names:

 Green Checkmark: The rule is valid and compatible with the queue's schema

 Red Warning: The rule is invalid for that specific queue. Hover over the error icon to view a detailed message (e.g., AttributeError: Field 'amount_due' is not defined), which provides hints on how to fix the incompatibility

Best practices

  • Test thoroughly: Always validate templates in your test queue before publishing

  • Review before publishing: Check the distribution list to avoid unintended updates

  • Preserve customizations: Use distribution toggles to maintain queue-specific requirements

Common use cases

  • Standardized validation: Deploy consistent data validation rules across all queues

  • Company-wide policies: Implement universal business rules (e.g., approval thresholds)

  • Multi-region operations: Maintain identical processing rules across geographic queues

  • Phased rollouts: Test rules in specific queues before company-wide deployment

Requirements

  • Access to Rules Manager in the Settings section (typically administrators and managers)

  • At least one queue selected for testing context

  • Valid Rules & Actions configuration before publishing