Skip to main content

ServiceNow REST Table APIs and test harness

 https://xxxxx.service-now.com/api/now/table/incident?sysparm_fields=number

(note this may result in a http status of 206 as we are restricting the fields in the response)

this param returns the number in the response, rather than the whole incident info


useful harness:


and of course postman

CURL example
curl "https://XXXXXXX.service-now.com/api/now/table/incident?sysparm_fields=number" \
--request POST \
--header "Accept:application/json" \
--header "Content-Type:application/json" \
--data "{
    \"contact_type\": \"Alert\",
    \"category\": \"Data Issue\",
    \"subcategory\": \"Data or File Error - other\",
    \"short_description\": \"File Error + [File Name]\",
    \"description\": \"[Error Exception]\",
    \"assignment_group\": \"56b756774fbd368057db0b318110xxxx\",
    \"u_role_type\": \"c319bc4bdb41834074abffa9bf96xxxx\",
    \"impact\": \"2\",
    \"urgency\": \"3\",
    \"service_offering\": \"93d387761be26c1049c38732f54bxxxx\",
    \"caller_id\": \"1475a0491b743414f0dc85e4464bxxxx\"
}" \
--user 'admin':'xxxx'

Comments

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 

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