Skip to main content

Enforce unique numbering - avoid duplicates on child tables of task

Enforce unique numbering - avoid duplicates on child tables of task

useful reading here:


https://docs.servicenow.com/bundle/xanadu-platform-administration/page/administer/field-administration/concept/c_EnforcingUniqueNumbering.html


for my solution I went for the recommended business rule solution, and defined the business rule to run on "task" table and inherited by child tables (incident etc)

still trying to get to the bottom of how exactly the issue of duplicate incident numbers being generated on the incident form arises, but in the meantime no more duplicate tickets in our instance!

examples of how the transaction logs might be checked for the issue:

/syslog_transaction_list.do?sysparm_query=sys_created_onBETWEENjavascript%3Ags.dateGenerate('2018-05-03'%2C'12%3A50%3A00')%40javascript%3Ags.dateGenerate('2018-05-03'%2C'12%3A50%3A59')%5EurlSTARTSWITH%2Fincident%5Esql_count%3E0%5Eresponse_time%3E25%5Esys_created_by%3DSmith

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            },