Why don't I see the Condition Operator and Values for my Catalog Item Variable in Decision Builder?

shawnclune
ServiceNow Employee
ServiceNow Employee

I am trying to use Decision Builder to build a Decision Table to then use in Flow Designer to assign the correct fulfiller to a catalog item.

I am working in a PDI running ROME.

I have created the Decision Table (see below):

find_real_file.png

 

I have created the INPUT - essentially want to look at RITMS (see below):

find_real_file.png

 

I selected "Add condition column" and built it out to use a Variable (see below):

find_real_file.png

 

The result of which is shown below:

find_real_file.png

 

So the full build out at this point with the Answer Table = [sys_user_group] looks like this (see below):

find_real_file.png

 

When I try to create a Condition under the first column, I do not see the "Condition Operators" (e.g., is, like, =, etc.) nor do I see any of the multiple choice values from the Variable.

find_real_file.png

 

What is the issue?

I am using Multiple Choice variable types in the catalog item so I'm wondering if that is the issue - incompatible "data" types between Service Catalog and Decision Builder.

Thoughts?

3 REPLIES 3

Allen Andreas
Administrator
Administrator

Hi,

I believe each line is considered be =. so x = y.

Whatever field name and field value is for one column, then another column is another field name and field value.

Each additional column is AND to the previous condition.

Example:

find_real_file.png

So that's the Billable field with a value of false, which equates to Billable is false or Billable = false.

Multiple choice, you should be able to state the field, and then the selection value that is relevant to your scenario.

Please mark reply as Helpful/Correct, if applicable. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Manuel Stimac
Mega Sage

Hi @shawnclune,

I researched further more but nothing related to be found. I opened a case and it seems to be "Expected Behavior" which is mentioned in PRB1572621.

 

The only Workaround I could think of is to change the Input of the Decision Builder from the Requested Item to a valid Type and to pass the values via Flow designer into the decision. For example:

ManuelStimac_0-1678888688458.png

 

And pass it as following in the Flow:

ManuelStimac_1-1678888958821.png

 

This is not a nice solution but as long as the Problem is not addressed we have to work a bit around.
Hope this helps all the others coming across this one 🙂

 

If this answer helps you please mark it as Helpful/Solution.
Thanks & Regards - Manuel 

 

 

 


If my answer helped you, please mark it as Helpful/Solution.
Thanks & many Regards - Manuel 

Hi @shawnclune,

did my answer help you? If my answer helped you, please mark it as Helpful/Solution so other will find it too.


Thanks & many regards - Manuel 

 


If my answer helped you, please mark it as Helpful/Solution.
Thanks & many Regards - Manuel