Enhancing Q-assign Selection Criteria with Additional Selection Criteria

Support for Multiple Child Object Queries & Polymorphic Relationships

Overview

Q-assign Selection Criteria traditionally allow filtering records based on fields on the target object (such as Lead, Case, or Opportunity) and standard lookup relationships. However, many real-world use cases require selecting records based on child or related objects, such as Tasks or Events.

To address this, Q-assign now supports Additional Selection Criteria, a powerful enhancement that allows Assignment Groups to further refine record selection using multiple related objects, including those connected via polymorphic lookup fields (for example, Task and Event relationships).

This enhancement enables advanced filtering scenarios such as:

• Assign Leads that have no Tasks

• Assign Cases that have at least one open Task

• Assign Leads that do not have any open Tasks

• Apply multiple child object filters within a single Assignment Group

What’s New: Additional Selection Criteria

Additional Selection Criteria introduce a secondary filtering layer that runs after the primary Selection Criteria.

This allows Q-assign to:

• Query related objects separately (including polymorphic ones)

• Progressively narrow down records using multiple child-object filters

• Support both “met” and “not met” logic

• Include or exclude records without any related child records

How It Works (High-Level)

1. Primary Selection Criteria runs first
   This identifies an initial set of target records (for example, Leads with Status = Open).

2. Additional Selection Criteria run sequentially
   Each configured related-object criterion filters the working set further.

3. Final Working Set proceeds to assignment
   Only records that pass all criteria are evaluated by matching rules and assigned.

💡 Best Practice: Place the most restrictive Additional Selection Criteria first to improve performance.

Max Records to Select (Important)

A new Assignment Group setting, Max Records to Select, controls how many records are fetched by the primary Selection Criteria before Additional Selection Criteria are applied.
 

Why This Matters

Additional Selection Criteria may filter out many records. This setting allows Q-assign to:

• Select a larger initial pool (e.g. 5,000 records)
• Process only the subset that matches all criteria (e.g. 200 records)
   

Default Behaviour

• If Max Records to Select is blank, Q-assign uses the existing Max Records Per Job setting
• This ensures full backward compatibility

How to Configure Additional Selection Criteria in Q-assign (Multi-Relationship Filtering)

What you’ll achieve

Using Additional Selection Criteria, you can filter records in an Assignment Group using child/related objects (for example Task or Event), including relationships via polymorphic lookups such as Task.WhoId (Lead/Contact).

Common example:

• Select Leads that have Tasks matching certain criteria (Priority = High, etc.)

• Optionally include Leads with no Tasks

Before you start

• You must have access to QA Assignment Groups (Q-assign admin/manager permissions).

• You should already have an Assignment Group created with:

  • Object = Lead (or your target object)

  • Source Queue/User configured (optional, depending on your design)
     

Step 1: Open the Assignment Group and locate “Manage Additional Selection Criteria”

1. Go to QA Assignment Groups tab

2. Open the relevant Assignment Group (AG)

3. Scroll to Selection Criteria area

4. Find the section called Additional Selection Criteria

You will see the "Additional Selection Criteria” section with the Manage Additional Selection Criteria button and a summary row.

• You can see the summary path like: Task > Name ID → Lead

• You can also see the “Include records without…” checkbox column in the summary table.

Step 2: Click “Manage Additional Selection Criteria”.

This opens the management pop-up, where you can view existing criteria or create new ones.

The “Additional Selection Criteria” pop-up with:

• A list/table of existing criteria (if configured)

• Button: New Additional Selection Criteria

• Column showing “Include Re…” (Include Records Without…)

Step 3: Create a new Additional Selection Criteria.

In the pop-up, click New Additional Selection Criteria

This opens the configuration screen “Define Additional Selection Criteria” page showing:

• Order

• Related Object

• Lookup to Object  (this is the key part for polymorphic relationships)

• Criteria mode: “met” / “not met”

• Criteria rows (Field / Operator / Value)

• Option: Include Leads without any Tasks

Step 4: Set the basic relationship (Related Object + Lookup)

On the “Define Additional Selection Criteria” screen:

1. Order

   • Enter the execution order (e.g., 1)

   • Best practice: put the most restrictive criteria first

2. Related Object

   • Select Task (or Event, or another child object)

3. Lookup to Lead/Other object

   • Select the lookup field that connects Task to Lead.

   • For the polymorphic Lead/Contact relationship, this is typically:

     • Name ID (this represents the Task WhoId relationship in your UI)

 This is what enables Task/Event filtering even when the relationship is polymorphic.

• Related Object = Task

• Lookup to Lead = Name ID

Step 5: Choose Criteria Mode (met / not met)

In the line that reads:

“Select Leads with Tasks where the following criteria are [met/not met].”

Choose one:

• met → Keep leads that have at least one task matching your criteria

• not met → Keep Leads where tasks do not match the criteria (often used to exclude “open tasks” etc.)

Step 6: Add your criteria rows (Field / Operator / Value)

1. Under the criteria grid, configure the child object filters (Task fields)

2. Example shown in your UI:

   • Field: Priority

   • Operator: equals

   • Value: (multi-select values supported)

3. To add more conditions:

   • Click Add Criteria Row

Step 7: (Optional) Use Filter Logic for multiple rows

If you add more than one criteria row, use Filter Logic to control how the rows combine.

1. Scroll down to Filter Logic

2. Enter logic like:

   • 1 AND 2

   • 1 AND 2 OR (3 AND 4)

Step 9: Save the Additional Selection Criteria and confirm

1. Click Save. The Additional Selection Criteria section should now show:

• Related object mapping row

• Criteria summary