question gsftSubmit wait for dialog to close in Developer forum

gsftSubmit wait for dialog to close

Mike Edmonds1 — Tue, 27 Mar 2018 23:36:27 GMT

All,

I have a dialog window that renders successfully. I need to, wait till the user enters some data and submits the dialog window, then update the form. When I try the gsftSubmit(), the dialog render, the script keeps running, and the record is not updated after the dialog box is submitted. I have also entertained using an onSubmit() client script. Again the dialog is rendered but promptly closes with out allowing any data to be entered when the script gets to the g_form.submit() function. Any help is greatly appreciated.

Re: gsftSubmit wait for dialog to close

Rahul Jain11 — Tue, 27 Mar 2018 23:47:29 GMT

Hi,

You can wait for the dialog window to close before it execute the gsftSubmit().

The better way to achieve this is to write your logic in the UI Page which is used to open the dialog window based on the user action.

You can write the client script or server side script in the "processing script" of UI page.

You can look at the example for the same here: UI Page

Thanks,

Re: gsftSubmit wait for dialog to close

Mike Edmonds1 — Wed, 28 Mar 2018 13:03:58 GMT

Rahul,

The end goal would be something like this.

Interact with form / enter or change information on the form
Click UI action such as Save and Close
Render dialog
Input data to daialog window
When the dialog is closed the form is submitted from the client and commits the changes to the server

I need the record to update on the client to grab any new data and comit to the server. The dialog is used to capture information for a custom time tracking application, I am gathering information form the current record to populate fields on it. It seems the Processing Script can populate data back to the record on the server and update it there, which is why I was hoping to use gsftSubmit. Can you think of anything else that may work?

Re: gsftSubmit wait for dialog to close

Tristan Elmore — Fri, 24 Jan 2025 16:03:47 GMT

I realize this is an older post, but in case someone comes across this and is trying to find a way to use a GlideModal in an onSubmit client script and you're running into issues where it's either looping or submitting the record before the user has a chance to confirm/validate etc on the modal window, try this:

if(g_scratchpad._action_confirmed) { return true; } var dialog = new GlideModal('glide_modal_confirm', false, 300); dialog.setTitle(new GwtMessage().getMessage('Confirmation')); dialog.setPreference('body', new GwtMessage().format("Are you sure to save?")); dialog.setPreference('focusTrap', true); dialog.setPreference('onPromptComplete', doComplete); dialog.setPreference('onPromptCancel', doCancel); dialog.render(); return false; function doComplete() { g_scratchpad._action_confirmed = true; gsftSubmit(null, g_form.getFormElement(), g_form.getActionName()); } function doCancel() { }

Full credit to icerge on GitHub who came up with this one. I spun around with different ways to try to use gsftSubmit to get this to work.
Using modal windows in SN: GlideModal, confirm onSubmit · GitHub

Re: gsftSubmit wait for dialog to close

dc3itlearn — Sun, 07 Jun 2026 12:14:54 GMT

Hi @Tristan Elmore, I'm following you on the script code, but where to put it?

I tried in the UI Action of the triggering button and not honored.

For my use case, I have a UI Action Form button on the Incident table.

User clicks button and the modal pops the default form view for a custom table.

When the user clicks submit for the custom table, is when I want to trap the event and do what I need - in my case window.open and pass a custom built url to another system - yes I can go API call and all that jazz, but my preference is to go old skool with just a simple UI/UX open in a blank tab and allow the user to get an idea of what is going on in the other system. But I digress.

Where's the special sauce? Or am I as usual overthinking something?

I'm a bit new to ServiceNow, but 30 yrs in programming so, I have not figured out the page lifecycle yet of ServiceNow's architecture.

Here's my code if so desired.

Re: gsftSubmit wait for dialog to close

dc3itlearn — Tue, 09 Jun 2026 14:47:17 GMT

As I'm still trying to make my way around all the carved up access points in the ServiceNow Navigation Pane/Menu, Client Scripts offered the easiest solution.

1. Create a new Client Script

2. Select the table - for me it is the custom table u_generate_document - this is where the default form is pulling into the glide modal and the default submit button appears

3. I left UI Type as Desktop

4. The type dropdown value is set to onSubmit - this is the key because it taps into the submit event listener that is generated by the server side code on modal page render

5. I left the other options as defaults

6. In the Script block create the following function:

function onSubmit() { // Only run when the user is creating a new record if (!g_form.isNewRecord()) return true; // Capture values BEFORE the form submits var docType = g_form.getValue('u_document_type'); var generateDocID = g_form.getValue('u_number'); var incidentID = g_form.getValue('u_incident'); var url = "https://your.unique.url?incidentID=" + encodeURIComponent(incidentID) + "&gdID=" + encodeURIComponent(generateDocID) + "&docType=" + encodeURIComponent(docType); // Redirect the user - please note, you will want to use the top property of the window object to pop out of the modal window and get back to the core browser tab in order to open a new tab top.window.open(url, "_blank"); return true; }

7. Check the Isolate Script checkbox

This works for me in ServiceNow Australia version, personal developer instance, latest release as of the date of this post - hope this helps someone - thx!