Assignment Rulesets are an easy way to group Rules and Teams, so you can use them to quickly create routes and steps in Distro.
This article will cover the following:
- What are Assignment Rulesets?
- Creating and Updating your Rulesets
- Can you have "ownership fields" and "all fields" in the same Assignment ruleset?
What are Assignment Rulesets?
An assignment ruleset is a Rule or group of rules that will be leveraged to determine an assignment.
In the past, rules were a part of queues - we have decoupled them to make them a reusable asset across products.
Creating and Updating your Rulesets
Let's look at how to kick off and create and update your Assignment Rulesets!
At the top-right, you can click the "Create Assignment Rulesets" button to create a new one and start accommodating your Rules over there:
You can also re-order (drag & drop) your CRM and Non-CRM rules to decide in which order the rules will be evaluated:
Distro will evaluate the distribution in the Assignment Rulesets order and stop as soon as we have a match, so the order you'll display your rules is important.
Catch-All
The catch-all Rule can be used to distribute objects that have failed to match your other (CRM and Non-CRM) rules. This way, if you want to, you can ensure that all objects will be distributed, even if they haven't matched any rules.
The Catch-All will always be the last one evaluated, as it can be used to distribute objects that have failed to match your other (CRM and Non-CRM) rules. This way, if you want to, you can ensure that all objects will be distributed, even if they haven't matched any rules. The re-ordering possibility is not given because, since the Catch-All has no rules, accommodating it before any CRM or Non-CRM rules would become non-usable, as all objects would match the Catch-All before evaluating the remaining rules.
Below is a demo of Adding a catch-all ruleset in the Assignment Rulesets section:
Can you have Ownership and Non-Ownership Rules in the same Assignment ruleset?
Yes! Assignment Rulesets are an easy way to group Rules and Teams together, so you can use them to quickly create routes and steps in your other Chili Piper products.
You can have both Rule types in the same ruleset with an "OR" operator in your Rules to designate which Rule should match the evaluation. Alternatively, you can use an "AND" operator if you want Chili Piper to confirm if both rules are true.
As mentioned above, you can re-order the rules to decide which will be evaluated first. The evaluation of the ARs (Assignment Rulesets) is based on the order of the routes from top to bottom (so the ordering DOES matter)
For example:
Please note: Only published Rules and Teams can be used here meaning that the status can't be Draft.
For example:
Below is a table to help understand Statuses and their possible states.
Status | Possible States |
Draft | Inactive |
Published | Inactive, Active |
Published + New Draft | Inactive, Active * If the status is Active but shows Unpublished Changes, the most recently published version will remain live until the latest Draft is published. |