Comments on: Condition Builder Attributes That Pack a Punch

By: Carleen Carter

Carleen Carter — Thu, 13 Jun 2024 22:02:08 +0000

In reply to Fred. Any number of places! In one of my PDIs, almost 50% of the condition builder fields (internal_type=conditions) do not have condition_builder=v2 in the Attributes. If there is a field where you must set up rules that frequently dot-walk through reference fields, the time saved on the drop-down reloading alone is worth it! If you are building a new application, condition fields are a powerful tool to make it more dynamic and data-driven. They also empower non-admin users by allowing them to configure rules. For instance, I recently built a table that enables process admins to automatically set the conditions to apply categories. This way, categories would be applied uniformly, increasing reporting accuracy and giving non-admin users a greater role in the process. If you are interested in using a Condition field in a new application, check out the GlideFilter API in the ServiceNow documentation. The methods in this API allow you to take the value of the condition fields and compare it to a GlideRecord to see if there is a match.

By: Keith Mildren

Keith Mildren — Thu, 13 Jun 2024 01:09:13 +0000

This is really good. I appreciate you sharing. Will definitely use it in the future .

By: Shu Liu

Shu Liu — Wed, 12 Jun 2024 21:03:50 +0000

Love it, Thank you for sharing

By: David Rosevold

David Rosevold — Wed, 12 Jun 2024 17:17:50 +0000

Displaying Condition Builder v2 as the default. Great info!

By: Fred

Fred — Wed, 12 Jun 2024 09:58:11 +0000

What field would you actually add these attributes to?

By: Trinny

Trinny — Tue, 11 Jun 2024 20:59:15 +0000

In reply to Dharma Liyanage. Wonderful tips and tricks you are sharing!

By: Dharma Liyanage

Dharma Liyanage — Tue, 11 Jun 2024 17:50:43 +0000

Thank you for sharing your knowledge.