logo

NJP

ServiceNow get record last updated fields (e.g. incident)

Import · Jun 22, 2022 · article

ServiceNow get record last updated fields - GLOBAL scope

(for scoped app version see this article )

see https://www.servicenow.com/community/developer-forum/where-does-the-glidescriptrecordutil-come-from/m-p/1441264

and http://snamigos.blogspot.com/2017/11/how-to-get-changed-or-modified-fields.html

notes:

- may not work in scoped applications

copy below into an after business rule on incident update for example:

(function executeRule(current, previous /*null when async*/ ) {

gs.addInfoMessage('test br');

var gru = GlideScriptRecordUtil.get(current);

var sChgFields = gru.getChangedFields();

//var sChgFieldsNames = gru.getChangedFieldNames();

//var sChg= gru.getChanges();

gs.addInfoMessage(sChgFields);

//gs.addInfoMessage(sChgFieldsNames);

//gs.addInfoMessage(sChg);

https://www.youtube.com/watch?v=5rs6LimyuEI&t=13s

script include version - additional features:

this.si.getIncidentLastUpdatedFields(current);

getIncidentLastUpdatedFields: function (incGR) {

var gru = GlideScriptRecordUtil.get(incGR);

var changedFields = gru.getChangedFields(); //Returns an arrayList of changed field elements with friendly names

var changedFieldNames = gru.getChangedFieldNames(); //Returns an arrayList of changed field elements with database names

var changeds = gru.getChanges(); //Returns an arrayList of all change values from changed fields

gs.info("changedFields: " + changedFields.toString());

gs.info("changedFieldNames: " + changedFieldNames.toString());

gs.info("changeds: " + changeds.toString());

var changedFieldsF = j2js(changedFields);

var changedFieldNamesF = j2js(changedFieldNames);

var changedsF = j2js(changeds);

gs.info("Changed Fields: " + JSON.stringify(changedFieldsF));

gs.info("Changed Field Names: " + JSON.stringify(changedFieldNamesF));

gs.info("Changes: " + JSON.stringify(changedsF));

gs.info('ERROR'+ex.toString());

(ServiceNow )

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 )){

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }

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,7owned_by=' + current . variables . requested_for ); //owned_by=1269b79937f1060041c5616043990e41install_statusNOT IN8,7 },

View original source

http://www.cloudminus89.com/2022/06/servicenow-get-incident-last-updated.html