Unable to submit the catalog item on Service portal.

[Swathi P]

Hi All,

While trying to submit the request through portal. It just says Submitting..... When i inspect the portal it says on console that could not find UI Action.

Please suggest what is the error. I am not able to get the error.

[Allen Andreas · Accepted solution]

Hi,

It looks like maybe some sort of command (possibly issue with a g_form line) is causing issues in maybe the UI Action for submit? I would investigate this UI Action and see if anything was altered with it, if so, evaluate/troubleshoot and/or go back to OOB version.

Also try with another request item and see if you get the same result.

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

[thughes]

I'm also experiencing this. I'm on London with a cloned widget, with the only change being that I've set the auto_redirect option to "false". Any insight into how you resolved this issue would be incredibly helpful.

[benanderson]

Hey all. We have a HI ticket open with ServiceNow in regards to this issue. But I have found the root cause -

It seems something to do with this widget has been changed so that errors or minor issues do not fail silently anymore and cause errors that result in the order being stuck trying to submit.

The core issue stems from an object mismatch when using .setValue in scripts. For instance, trying to set a checkbox like so -

g_form.setValue('v_ams_ext', false); will cause the error and the form be unable to submit. If you change this to be g_form.setValue('v_ams_ext', ''); it will submit properly.

Another example is a single text field variable. If you pass an integer directly into this field it will fail - something like g_form.setValue('text_field', int); whereas if you do something like g_form.setValue('text_field', int.toString()); it will allow the form to submit without a problem.

[benanderson]

ServiceNow has advised that this is an intended change and a bug fix from how the widget functioned under Kingston. You will need to make sure you are setting the expected variable object type when using g_form.setValue