Decision Table "Default Answer" Issue

[Mukesh Khanna P]

I'm having a decision table which returns assignment group based on checking the condition using string input fields. The decision based on condition are working correctly and sends the assignment group to the script where it is called, but I'm having a requirement to have a default group when all the conditions are failed. I've setup the default value, but the decision table is returning empty/null value when all conditions fail, why is this happening! There is no complex logic/decision criteria involved in my scenario, but still the default answer which is OOTB functionality is not working correctly. 

I really appreciate any help on the above mentioned issue, thanks in advance!

[scottl]

The decision table "app" is clearly broken and has a bug as I am facing the same issue. Even with a basic test. It never returns a default answer.

One should NOT have to go into the app tables and change field values just to get it to work.  ServiceNow offers an app, it should work as expected.  If not, SN needs to stop releasing half developed and non tested apps on an enterprise level product.  This is WHY SN has become so bad, as people just accept these poor implementations. People pay ALOT of money for SN, so stop bending the knee, and start holding them accountable to start improving their QA.

[Mukesh Khanna P · Accepted solution]

I agree, there is a bug in decision table UI. If you make any changes to existing decision table, once publishing the drafted version, navigate to "sys_decision_question" table and search for the questions associated to your decision table, add "Active" field to the list view and validate if there is any questions marked as "Active = False".

If yes, make all the questions to "Active = True" and check it now, the decision table is returning the default answer.

This is definitely a bug that happens while publishing the drafted version for decision table which makes the decision questiosn as "Active = False".

[scottl]

That is unbelievable that was not picked up during testing. It's such a basic test and brings me to the question are they even properly testing these things??  Even the dev developing it should've seen that!!

So who at SN is being held accountable for this, on an enterprise level product? I think it's completely unacceptable that this is happening.

[scottl]

Found another bug, where there return values of referenced Choice values are the LABELS and not the actual values! /faceplam.

So for example if you wanted to align the States between the Request, Requested Item and Task, good luck using Decision tables.    

Decision table is a good idea and I can see alot of good uses for it, but what ever team coded it, and tested it should be let go because it STILL cannot be used. 

And as a side note, using Referenced choice fields when editing them has the ability to DELETE all the values in the Choice field, and there is zero reference in the system of those values being deleted.  With SN accepting that they were deleted but they had no clue how it happened, and it was not resolved.