default answer not working in latest patch of servicenow decision builder

GUBBALA VEERA V
Tera Expert
Evaluator: com.glide.script.RhinoEcmaError: Cannot read property "result_elements" from null

hi community,

In decision table if condition does not match we will get default answer but after latest patch upgrade we are getting the above error.

Can any one know the solution for this.

if we give the correct license type i am getting the result as expected.




 

1 ACCEPTED SOLUTION

Hi @Amit Verma @OlaN

Thanks for you responses. I have deleted decision table record and created new one and now the functionality is as expected.

 

I am not sure what is the cause for my issue earlier.

 

Thanks.

View solution in original post

6 REPLIES 6

OlaN
Giga Sage
Giga Sage

Hi,

If it is a validated bug, then you should report the issue to support. (support.servicenow.com)

Maybe SN needs to learn how to code, and do actual testing before releasing it to ENTERPRISE customers. Because this Decision app is garbage.  I went to use it, and tried to implement a very simple condition, it crashed, corrupting it on first go. Then when I deleted it to start again, it DELETED the Choice table records referenced against the CMDB table I was using to set values for Hardware Status. Now my new one won't even bring back the Default values, in my own PDI when testing it. 

Even the Test trigger between Published and Test doesn't even work correctly. 

Unbelievable.  People need to be fired for the recent decisions at SN, especially around this so called "NEXT" experience.  

Amit Verma
Kilo Patron
Kilo Patron

Hi @GUBBALA VEERA V 

 

Can you please let me know on which version you are facing this issue ? I tried simulating it on Xanadu and it is working as expected. If possible, can you please share screenshot of the decision table. Also, can you validate whether your decision table is set to be accessible from all application scopes or from a specific application scope only.

 

Thanks and Regards

Amit Verma


Please mark this response as correct and helpful if it assisted you with your question.

Hi @Amit Verma @OlaN

Thanks for you responses. I have deleted decision table record and created new one and now the functionality is as expected.

 

I am not sure what is the cause for my issue earlier.

 

Thanks.