Skip to main content

Catalog client scripts - puzzling behavior onsubmit with onchange

I happened to notice an issue which was particularly apparent in Service Portal view, and wasn't made easier by the fact that in Service Portal, test alert messages appear to get caught in a loop until you click out of the tab and back in...
I haven't got to the bottom of it yet, but I did notice in my scenario where the following was happening:

-onchange runs on a checkbox which sets a number of fields, and resets fields to blank if unchecked
-onsubmit vets whether the checkbox is ticked

that the onsubmit catalog client script was calling the onchange code, even though the checkbox was not being set in the onsubmit, merely it's value of true or false was being obtained

the problem was that the onchange was running and messing up the related fields...so,
I seem to have got round it by using the condition in the onchange:

if (newValue=='false'){
     //reset fields
     //...
     return;
}

Still investigating a better solution...and trying to figure out if there is a way to determine in an onchange script that the form is being submitted, to arrive at a solution like this:
if (<form_is_submitting>=='true'){

     //reset fields
     //...
     return;
}

Comments

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){

Service Catalog: variable advanced reference qualifiers

Call a script include to apply a reference qualifier on a catalog item variable: - variable reference qualifier dependent on another variable selection, in this case a variable referencing sys_user (requested_for) On the catalog item form. variable name to apply ref qual filter : retail_equipment variable reference qualifier (on cmdb table ): javascript : new  refqual_functions (). lostStolen_getAssignedCIs (); client-callable script include ( refqual_functions)  function : lostStolen_getAssignedCIs : function (){         //--called from variable set client script, for lost/stolen request (service catalog)     gs . log ( current . variables . requested_for , 'retail_lostStolen_getAssignedCIs' );         return ( 'install_statusNOT IN8,7^owned_by=' + current . variables . requested_for );             //owned_by=1269b79937f1060041c5616043990e41^install_statusNOT IN8,7            },