Hey Ben, thanks for the feedback. I understand what you’re saying, but in my testing the complete override/replacement is necessary so that you get the proper dialog message. Otherwise, the standard dialog still appears. I may be missing something so if you can get it to work in the way you describe I’d be happy to add it. I agree it’s the better way if it will work.

It’s better to just subscribe to the event with:

if(window.addEventListener)
window.addEventListener(‘beforeunload’, myfunc, false);
else if(window.attachEvent)
window.attachEvent(‘onbeforeunload’, myfunc);

Your management needs to understand that they’re playing with fire being that far behind the curve on ServiceNow upgrades. I’m surprised you haven’t been forced to upgrade yet. The message comes from the underlying code (which you don’t have access to). It points to the message record, but if the message record doesn’t exist, it supplies the default. You can compare to the message record in the demo instance to make sure you’ve got the correct one.

You can just create that message record. As long as it has the correct ‘Key’ value, the message will show up however you want. You can access the ServiceNow demo environments at demo.service-now.com. By the way, if you’re on that old of a build, you’re in serious need of an upgrade. That should probably be your first priority.

I just tested this on the ServiceNow demo site and it all works correctly there. I’m guessing that you don’t have the dirty form property turned on. Navigate to your ‘sys_properties’ table and make sure that the ‘glide.ui.dirty_form_support’ property exists and that it is set to a value of ‘true’.

There is one problem with this dirty form alert message………

after getting alert messages/error messages from client script or business rules if we try to navigate away from user form this dirty form popup is not working….for eg:
1.user is filling incident form and had forgot to fill one mandatory field.
2.when he clicks the submit button an alert box will come saying that field is mandatory .
3.now if he tries to navigate away from the form ,it is allowing the user…. ..No dirty form popup alert is coming ….No alert message to the user saying “data has been modified and are you sure you want to leave this page..?”

Thanks for sharing this! I think eventually I’d like to come up with a solution where you didn’t have to target each specific variable individually. This approach works for an individual catalog item fine, but it’s not something that’s practical to deploy across the entire catalog.