Skip to main content

We use many rules for assigning tickets, creating subtickets, assigning SLAs, sending Webhooks, etc, which has been great, but we have gotten to a point where we have 75+ “When Created” rules, which all affect tickets differently. Part of it is on us, we are trying to simplify and reduce the number of rules, but we also just have many rules that do different things, so not all can be simplified.

 

All that being said, my question is this: How do you keep track of your rules, what does what, and making sure new rules are placed correctly? Do you use rule names to do it? or do you have another method? I feel like there is an easier way to do it, but maybe I’m missing something. Thank you for the response!

@AWhipple This is a great question and the perfect way to start the new year! The iiQ Rules Engine is so powerful, but as you mentioned, can be complicated and confusing if not well organized. One of my recommendations is to name your rules well by being descriptive and also make sure to use initials after to ensure other iiQ Admins know which admin wrote which rule. This helps if others have questions or something else stops working, they know who to communicate with. Descriptive rule names are also helpful when using compact mode!  I also recommend keeping similar rules together. 

Also keep in mind that rules are cascading, meaning they will run from the top of the page to the bottom of the page, so order matters!

Lastly, don’t forget the ever important radio buttons: continue processing or stop processing. This goes along with the order of the rules and can be used to decide if you want a ticket to keep running through the rules or if you want it to stop looking at all other rules once that one has been completed. 

Hope this helps and would love to hear other districts chime in and share how they keep their iiQ Rule Engines squeaky clean!


Reply