TechNow Ep 12 | Condition Fields

Chuck and Andrew - Great video and very helpful.   I already have a variety of places where I can use this in our ServiceNow instance, plus make my life a whole lot easier.

Hello Chuck

I've been working with the condition builder field based on your presentation.   The business rule I've implemented is successfully matching conditions in my rule table and completing a correct Incident assignment.   However, if no condition is found, the script seems to be defaulting to the last rule (either by Order or by last created).   Is this expected behavior or should the business rule simply drip out if now match is found?   My business is below:

checkRules();

function checkRules(){

  var rule = new GlideRecord('u_nimsoft_routing_rules');

  rule.addNotNullQuery('u_condition');

  rule.orderBy('u_order');

  rule.query();

  while (rule.next()) {

  var match = GlideFilter.checkRecord(current, rule.u_condition);

  if(match)

  gs.addInfoMessage("Match is " + match);

  current.assignment_group = rule.u_assignment_group;

  }

}

Thanks

Rick Mann

Rick,

If no conditions match, you shouldn't get anything. I always recommend a default condition in that case (e.g. set a property and use that if you didn't get any hits.

That being said, I see your issue... you don't have curly braces on your if statement so despite the indentation, you're if will only do the gs.addInfoMessage() if it 's matched. The current.assignment_group will be run ALWAYS for every record.

Try this..

if (match) {

gs.addInfoMessage('Match is ' + match);

current.assignment_group = rule.u_assignment_group;

}

Chuck,

Thanks for the clarification on my "if" statement.   I have another question regarding case on a "contains" condition.   Does the condition builder field handle case they same way as a standard condition builder?   For some reason, my rules are case sensitive.

For example, I have a rule to assign an incident to our Linux team if the incident short description contains "vRanger".   The rule will not match for "vranger" or "VRANGER", it only matches on "vRanger"

Again, probably something simple I'm missing.   Thank you for any advice.

Rick Mann

Rick,

That one surprises me. I would have though the contains searches were case insensitive like the list filters are. You may want to contact support to find out more. I don't have an answer for you at this time. Sorry.

Chuck

Thanks again for the help.   Looks like the case sensitivity is fixed with Eureka.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0535640

Hi Chuck,

This is a very interesting feature.

Is there any possibility by chance to replicate the same mechanism for catalog variables ?

Just to explain,

Basically I need to create Asset/CI when a requested item is fulfilled.

Depending on variables condition I need to map or not some variables to some fields

I would like to put all this logic into configuration instead of scripting.

Example:

Thanks,

Régis

The condition builder is great! Making customisation so much easier for those with little knowledge

Hi Regis,

Have you managed to achieve this? I am faced with a similar requirement.

Many thanks in advance :=)

Rilinda