function onSubmit() {
	
var grp = new GlideRecord('sys_user_grmember');
grp.addQuery('group', g_form.getValue('ad_group'));
grp.addQuery('user', g_form.getValue('ad_user'));
grp.query(groupMemberCallback);
   
function groupMemberCallback(grp){
//If user is a member of selected group
    if(grp.next()){
        //Do something
		g_form.showErrorBox("ad_user", "Error: user is already a group member " + 'ad_user.name' );
		g_form.submitted = false;
		return false;
    }
  
}

}

Basically I have a catalog item with two variables, a username and group name. I’m checking to see if the user is already a group member and if they are I’m displaying an error around the user variable and preventing the form from submitting, of course if the user is not a group member the form should submit. I can identify if the user is a group member but cannot prevent the form from submitting. Any insight you can offer is appreciated!

Try commenting everything else out but ‘return false;’ within your ‘if’ statement and adding an ‘Alert’ message right before ‘return false;’. Does the script show the alert? Does it prevent the submission? If it shows the alert and stops the submit correctly then your problem is probably with ‘g_form.showErrorBox’, which I don’t think is available in catalog client scripts and will need to be removed.

Great to hear. Thanks!

This was just what I was looking for. Thank you!

It’s not possible to suppress that message unfortunately. You’re stuck with it so the best thing you can do is include an additional info message to clarify what it means.

Normally you could use the javascript ‘scrollIntoView’, but I can’t get this to work in ServiceNow in my testing. You can google that and research it though and give it a try yourself.

I have a long form, and in the middle of it there is a checkbox which has to be true when submit.
The script I use is the first one mentioend in the article, on submit client script. Works good!

I wonder how can I do that after the submit button and the alert popup the screen navigates on the form where the checkbox is placed? I mean scrolling up until the checkbox. Even some higlight error message would be nice under that checkbox there to say that please select this.

Thank you!

You’re not doing anything wrong, but I think you’ve stumbled upon a ServiceNow bug that has probably been around since the beginning. ServiceNow has a ‘g_form.submitted’ check that goes along with ‘g_form.modified’ to make the dirty form capability work. That isn’t being set correctly when you abort with your client script. The solution is to set ‘g_form.submitted = false;’ right before your ‘return false;’ line in your script. I’ve updated the example script above with this fix. Thanks for the feedback!

if(g_form.getActionName() === 'sysverb_check_save'){
		
        if(g_form.modified){
            alert('Changes have been made. Save the form.');
            return false;
        }
}