Skip to main content
All CollectionsExport data and download filesUnderstanding OpenWater's condition builder
Create filters by understanding OpenWater's report condition builder
Create filters by understanding OpenWater's report condition builder

Build complex reports and price rules with advanced filtering

Zack Schwartz avatar
Written by Zack Schwartz
Updated over a week ago

The OpenWater condition builder is used throughout many aspects of the platform. Understanding its core concepts is immensely valuable and allows you to run reports with complex filtering, create advanced price rules, etc.

When the condition builder is empty like this:

For a report, this means that the report will output all submissions in the program. For a price rule, it means that the fee would be applied to all submissions.

No conditions have been set, so no filtering takes place.

[all] and [any]

The key to understanding the condition builder are the two sections -- [all] and [any]. If multiple conditions are added to the [all] section, then that means the submission must match the criteria set for every condition in that section in order to pass the filter. On the contrary, if there are multiple conditions in the [any] section, then so long as one of the criteria is met, the submission will be included.

You can chain conditions in both [all] and [any] sections. For example, if I wanted a report that included only submissions that are in the Sedan category and are either status Pending or Complete, my conditions would look like the following:

If I wanted to take a step further and say that I only wanted the above submissions that were submitted after January 1st, 2018, I would add another condition Submission Finalized At is greater than January 1st, 2018.

Available Conditions

We have many conditions available, but the options may differ depending on where you are in the platform. In a typical report or price rule, you can run conditions over any field in the submission form, user profile, as well as Others which are system determined functions such as:


Most common are Application Category, Application Won, Submission Finalized At.

But choosing fields based on how applicants answered questions on the submission form is very common. Choose Submission Fields when building a condition and then run through the drop down prompts. Here is an example of running a report on a question that asks the applicant if they are a member.

We encourage you to play round with the different conditions and functionality we have available. Ask your support representative if you have questions about how to setup certain conditions.


โ€‹

Did this answer your question?