Follow

LeadConduit: Rules

« Previously: Flow Management

What is a LeadConduit Rule?

Rules are the backbone of LeadConduit's decision-making engine. They provide a powerful, flexible way for non-programmers to exercise logic-based control over LeadConduit flow events, mappings, filters and lead intake acceptance.

In its simplest form, a LeadConduit rule consists of a Target datum to be tested, an Operator that describes what test is being performed, and in most cases a Criteria value that the operator tests the target against. Here are some examples:

Target

Operator

Criteria value

email

Is not blank

 

state

Is equal to

WV

DOB

Is not within the last

18 Years

Age

Is less than

65

Postal Code

Is included in

17201,95616,90210

Currently Insured

Is true

 

Program of Interest

includes

Nursing

 

How to configure rules

Rule configuration starts with a three-column form, much like this one found in Source acceptance criteria:

rules-blank.png

First, select the Target from the Left-Hand Value menu. This menu will offer all flow fields, system fields, step outcomes and appended data available at that point in the flow.

Once you've selected the Target, the middle drop-down will present you with a selection of Operators that are appropriate to the type of data contained in the target. Certain operators are only meaningful for date-type targets, for instance, and will not be available if a string-type Target is selected.

The right-hand column accepts the Criteria value or reference identifier. This column may disappear if the Operator you've chosen (such as "is blank") does not recognize any additional Criteria:

rules-dob-future.png

If a "+" sign appears in the Criteria column, clicking it will display a list of available flow fields, system fields, step outcomes, and appended data:

rules-dob.png

You may also type in text or numbers if your Criteria is a constant rather than a field or appended-data value:

rules-multiple-2.png

If your operator works with multiple values, you can type those values in individually:

rules-state.png

Multiple Rules

Add additional rules to a group by clicking the rules-add-new.png button. Delete a rule by clicking its rules-delete.png button:

rules-add-delete.png

When you are evaluating more than one rule, you may choose whether all, or just any one of them need to be met for the entire rule to be considered "conditions met":

rules-any-all.png

Nested Rules

You may add a second, "nested" layer to any rule by clicking rules-nested-good.png. The original rule is known as the "Parent" and the second layer is known as the "Child". In order for the parent to evaluate as "conditions met", its child layer's rules must also, taken as a group, evaluate as "conditions met":

rules-nested-example.png

Only parent-level rules may have nested children, so the maximum number of nested layers is two.

Rule Sets

You can convert a top-level rule to a group of rules that is evaluated as if it were one, called a "Rule Set", by clicking rules-ruleset.png. For instance, let's say you want to create a group of rules that evaluate BabyDue Date. Beginning with this:

rules-ruleset_example.png

Append additional Baby Due Date rules to evaluate as a group:

rules-rule-set-multiple.png

Copying Rules and Rule Sets

You can make a copy of a rule or rule set by clicking rules-copy.png :

rules-copy-1.png

After copy:

rules-copy-2.png

Next: Filters »

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

You must be logged in to comment.