I haven’t dived into the specifics of it, but there isn’t always a UI page that corresponds with a dialog. A lot of times ServiceNow will store the logic in a back-end XML file by the same name. If it’s working and you don’t see a UI page it’s probably back-end XML.

I checked event and error logs, but nothing is showing up there. Also, if there is a failure in some thing else, all the users should be affected. But only this specific user is affected and for this particular user it is working on other browsers but not on IE8. He is facing this error after this implementation.

I haven’t seen that issue but if I had to guess I would say it is because of a failure somewhere else in one of your client scripts. Check the event log to see if there are any errors.

This works great. Thanks for the solution.
But for some users who uses IE this is not working, and these users use IE8. Did you see the issue before.

It can be. You just need to use a ‘Client’ type of UI action to call the function containing the loading dialog. I think the challenge will be hiding the loading dialog once it is loaded though. You’ll have to figure out when and how you can initiate that trigger. Maybe if you used a synchronous ajax call you could initiate the loading dialog, make the ajax call, and then wait until the call came back to hide the dialog, all in the same UI action script.

Thanks for any help.

Rick

I’ve tried this suggestion to change the dialogue window title, and it works great – Thanks Mark.

Brian

Good question. I haven’t tested this extensively, but it looks like you can by using the long-hand way of initiating the dialog and including ‘setTitle’. Let me know how this works…

loadingDialog = new GlideDialogWindow("dialog_loading", true);
loadingDialog.setPreference('table', 'loading');
loadingDialog.setTitle('Hello World!'); //Set the loading dialog title here...
loadingDialog.render();