Skip to main content

ServiceNow Perspectium: work notes duplicates niggle

Scenario:
a duplicate worknote ends up getting written whereby an extra update transaction from Perspectium containing the following in the xml is sent


    <work_notes>_123STREAMENTRY321_original worknotes entered</work_notes>


Not too sure how this has come about but the steps to create it were reproducible


  1. Create problem ticket in ServiceNow instance 1 and send to ServiceNow instance 2
  2. Wait until number returned to ServiceNow instance 1 from ServiceNow instance 2
  3. Go into ServiceNow instance 2
  4. Enter a comment, cick ‘post’, then immediately change the state to <some value>, click save

fix:

include some error trapping in a try>catch within the inbound transform map to ultimately set the row to ignore=true


var iWN_err=source.u_work_notes.toUpperCase().indexOf('STREAMENTRY');
if (iWN_err>-1){
                        //--known error whereby the worknote has arrived as a duplicate jumbled string from TSFN
        sErrMsg='STREAMENTRY located in worknote string from TFSNow';
        sSessionErr=sErrMsg;
        throw (sErrMsg);
}

Comments

Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue' href=hr_profile.do?sysparm_query=number=" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown https://developer.servicenow.com/app.do#!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object