Does having too many Rule Bases in an Order Guide affect performance?

[Derek Tran]

I am building an onboarding solution using Order Guide.  Our company has about 150 applications and we decided that we will have individual catalog items for each app due to the fact that most of the apps have unique fields. 

I have heard from multiple sources that having more than ~25 rule bases will affect the performance.  Does anyone have more than 25 rule bases in their order guides?  Do you notice any performance issue? (etc. slow once Submitted order guide)

Thanks,

Derek

[DanielCordick]

Hey Derek,

I’m not sure performance wise but Maintenance wise this could turn into a nightmare in the future. If one or multiple catalog items get deprecated it could be very tedious to remove it from the rule base

We had an on-boarding order guide with 20 different rules and it turned into a rats nest.  Ended up scraping the whole thing and starting fresh. Just my 2c

Please mark helpful or correct 🙂

[Adam43]

we have an onboarding order guide with 14 rules/unique items, 3 of which are inactive items currently.  we're now getting a healthscan finding.  Each of our items has one unique rule, so it's not a case where we have multiple rules to the same item.  We just have that many items to include.

The number of rules associated with an order guide should be kept to a minimum

To reduce performance issues with order guides, limit the number of rules associated. One way to reduce the number of rules is to condense existing rule conditions into other rules using the condition builder. The "OR" operator would allow the same rule to manage more than a single condition.

https://docs.servicenow.com/csh?topicname=t_CreateARule.html