Skip to main content

Using Logic-Based Conditions in Reporting and Workflows (CRM)

This section explains how logic-based conditions are used across Reporting, List Views, Workflow Automations, Smart Notifications, and Surveys to control visibility and trigger actions.

Updated over 3 months ago

Conditions are a core concept used throughout Dazos and apply across several key areas of the platform:

  • Reporting

  • List Views

  • Workflow Automations

  • Smart Notifications

  • Surveys

Understanding how to interpret and apply conditions is essential to getting value from the CRM and leveraging its advanced functionality.

In the screenshots below, conditions are demonstrated using a Report. While the examples reference reporting, the concepts and user experience are consistent across all areas where conditions are used.

923fd874-088c-4b07-a68c-7fc29dbcbf14.png

As you become more familiar with Dazos, if you’re unsure which conditions to select or how fields are named, open an individual record to view available data and field labels. This is especially helpful when building workflows, as workflows require a trigger or field change to activate.

What Are All Conditions?

When using the first + Add Condition button, you are adding filters to the All section.
The All section functions like an AND statement—every condition in this section must be met for a record to appear in a report or match a workflow.

Example 1:
To appear in the report:

  • The record must be created during the current week

  • The record must be assigned to Dazos Administrator

Boolean logic: Condition 1 AND Condition 2

99f987b0-96aa-41cc-bb18-cb3d2e16a578.png

Example 2:

To appear in the report:

  • The record must be created during the current week

  • The record must be assigned to Dazos Administrator

  • The Primary Phone field must not be empty

Boolean logic: Condition 1 AND Condition 2 AND Condition 3

4cdaac26-ce9f-42c0-912c-b019a55f5550.png

What Are Any Conditions?

When using the second + Add Condition button, filters are added to the Any section.
This section functions like an OR statement—if any one condition is met, the record will appear in the report or match a workflow.

If a report returns more records than expected, double-check whether conditions were added to the Any section, as this typically results in broader results.

Example 1:
To appear in the report:

  • The record was created during the current week
    OR

  • The record is assigned to Dazos Administrator

Boolean logic: Condition 1 OR Condition 2

9ac9ef0b-4368-4468-b79f-2bc716c03d35.png

In the above screenshot, to appear in the report, the record’s creation time must be in the current week, or the record must be assigned to Dazos Administrator.

In that example, you could see a record assigned to Dazos Administrator that was created 3 weeks ago, or a record created this week that is assigned to Agent 1. Because they met one (any) of the conditions, they’re able to show.

To introduce you to Boolean terms, this would be conditions 1 OR 2.

Example 2:
To appear in the report:

  • The record was created during the current week
    OR

  • The record is assigned to Dazos Administrator
    OR

  • The Primary Phone field is not empty

Boolean logic: Condition 1 OR Condition 2 OR Condition 3

Using All and Any Conditions Together

Dazos allows you to combine All and Any conditions within a single configuration.

In the examples below, we switch to the Intake Opportunity module, so you may notice different fields being used.

Example 1:
Objective: View Intake Opportunities for the Test Facility that were either:

  • Created this month

  • Scheduled for admission this month

Boolean logic:
Condition 1 AND (Condition 2 OR Condition 3)

Example 2:
Objective: View Intake Opportunities for the Test Facility that are:

  • Assigned to Dazos Administrator

  • Created this month or scheduled for admission this month

Boolean logic:
Condition 1 AND Condition 2 AND (Condition 3 OR Condition 4)

4efea4b1-3db4-45ff-9f3b-cffe14765dbd.png

Using Combination Conditions (AND / OR Toggles)

Next to each condition, you’ll notice AND and OR toggles. These allow you to create more advanced logic within a single section.

This example uses the Calendar (Tasks) module and demonstrates a more complex scenario.

Example:
Objective: Build a task list showing follow-ups for each agent.

To appear in the report:

  • The task must be assigned to the current user

  • The task status must be Not Started

  • The task must either:

    • Contain Alumni in the subject and be due this week
      OR

    • Contain Follow-Up in the subject and be due today

Boolean logic:
(1 AND 2) AND ((3 AND 4) OR (5 AND 6))

f728b846-6abf-4f4b-890e-dfcd1b8d24eb.png
Did this answer your question?