Service portal widget 'Form' Save button not working

[Mclane]

Hey All,

I have a custom page on our service portal that has only one widget on it (Form). When any user pulls up the form in the Service Portal and makes a change to a form, there is an option to save using the button called 'Save (Ctrl + s)'. When clicked, the button isn't saving any changes to the form at all. The page doesn't attempt to reload so it seems as if the button is broken. Basically I need to allow users to change the State field to Closed Complete on a catalog task and then save the form. They can change the state, but cannot save.

I have seen a few posts about the JSON option in the widget 'Disable UI Actions on Form' needs to be unchecked but the value needs to be false. I tried cloning the widget and making one with this line commented out in the server side script, but no dice:

data.disableUIActions = options.disableUIActions || false;

I've seen this works for several others but it's not working for me. I made sure that the widget I cloned is now on the page replacing the OOB widget I was using.

Any ideas?

Thanks

[Josh Virelli]

Hi Mclane,

When you clone an OOB widget, make sure you add back the Dependencies and Angular Providers. You'll also have to create new Angular ng-templates and replace their names in the widget. That being said, you really shouldn't have to clone this widget, so the issue is probably elsewhere.

Can you switch the widget on this page back to the OOB form widget and tell me if there any javascript errors that pop up in the console? Do these users have write access on the sc_task table?

Thanks,

Josh

[Brad Tilton]

+1 For checking for JS errors in the console

[Mclane]

Hi Josh,

I'm back on the OOB widget: Here is the error I get in console (Chrome). My coding knowledge is pretty weak, but hopefully this helps: 

js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:12319 TypeError: Cannot read property 'submit' of undefined
at eval (sp-variable-editor.js:20)
at _runSubmitScripts (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:59601)
at GlideForm.submit (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:59113)
at eval (widget-form.js:79)
at Scope.$eval (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:14789)
at Scope.$digest (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:14697)
at Scope.$apply (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:14816)
at HTMLButtonElement.<anonymous> (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:17122)
at HTMLButtonElement.dispatch (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:3003)
at HTMLButtonElement.elemData.handle (js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:2877)
(anonymous) @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:12319
(anonymous) @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:11029
$digest @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:14699
$apply @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:14816
(anonymous) @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:17122
dispatch @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:3003
elemData.handle @ js_includes_sp.jsx?v=08-15-2018_0923&lp=Fri_Sep_07_07_25_20_PDT_2018&c=5_50:2877

As far as write access, yes all users I've tested with have write access. Even I as an admin cannot save the form.

[Josh Virelli]

Hi Mclane,

I'm not able to recreate the issue unfortunately. I think you'll need to open a HI Ticket on this one, seems like a very strange and irregular issue. I did find a Known Error on the HI Portal that seems very similar to yours : KB0692706

I really think enlisting the support of the ServiceNow team is going to be your best bet here. Sorry I couldn't help further!

Josh