Search

An Independent ServiceNow Blog

Category

Administer

Configure and manage your ServiceNow instance.

Email Notifications
Access Control Rules
Update Sets
Reference Qualifiers

STEP 1: PRE-PLANNING: Get to know the tool you've just purchased and the resources available to you and your organization. Research IT! For tips on learning ServiceNOW and/or resources available. Review my post "5 Steps To Learning ServiceNOW, NOW!" Use IT! Most customers who've purchased ServiceNow will have at least a PROD and DEV instance available for there organization. If you'd like to stay away from using your DEV instance for playtime; then my recommendations would be to either navigate to the ServiceNow DEMO site or ServiceNow Developer site. Populate IT! Get your stakeholders on-board and in the tool. STEP 2: PLAN Make Sure Everyone Understands and Agrees on Strategy. Identify, Examine, and Correct Process Gaps (Where You Can) Before you start a "project" to implement ServiceNow take a few..

Advertisements

This article was Originally posted by Tony Fugere and can be found - here ServiceNow Admin 101: Eureka Release and Upgrade Best Practices ServiceNow administrators can work more efficiently simply by following a few tips, and in the Admin 101 Series... Continue Reading →

New! Support: Top 10 Popular Solutions Below are the top 10 solutions this week. For issues with Personalize Choices - KB0529164: When using Personalize Choices, New Choices (sys_choice) are shown as invalid (blue) in list view For issues with operator property... Continue Reading →

Workaround For GlideRecord SetWorkflow (false) Issue

Thanks for sharing Ahmed. Excellent info.
Ahmed wrote: “As part of the GlideRecord API comes the function setWorkflow(false) .

If you’ve never used this before, essentially this function switches off the running of any subsequent business rules or workflows. This is really useful in a number of scenarios, for example when you need to update a lot of records in bulk and do not want emails to be automatically sent out for each one. ”

ServiceNow Gems

As part of the GlideRecord API comes the function setWorkflow(false) .

If you’ve never used this before, essentially this function switches off the running of any subsequent business rules or workflows. This is really useful in a number of scenarios, for example when you need to update a lot of records in bulk and do not want emails to be automatically sent out for each one.

I’ve been recently working on archiving and using the OOB implementation was just too slow for us (OOB was taking approximately 5 minutes to archive one incident and 5 tasks, my custom one now archive 150 incidents, 500 tasks, all audit records, journal records, attachments etc, in less than a minute).

But while doing this, I needed to delete records from one place in ServiceNow and put them somewhere else. I didn’t want it audited that I deleted these records nor did I want…

View original post 711 more words

ServiceNow Advanced Application Checklist: 3 Steps to Success

Trust me. Help yourself and your organization by learning how to reduce risk, achieve faster time to market, and higher user adoption rates #NOW. Watch this Webinar #REPLAY of Cloud Sherpas own Jon Reynolds as he explains essential steps to... Continue Reading →

SERVICENOW ADMIN 101: UPGRADES AND THE RELEASE CYCLE

SERVICENOW TECH TUESDAYS: REFERENCING TEMPLATESExcerpt:"I recently did an internal Lunch-and-Learn for my fellow Professional Services group during which we talked about templates and record producers.You may scratch your head and wonder what the two have in common, but they are... Continue Reading →

SERVICENOW ADMIN 101: SYSTEM CLONES BEST PRACTICES

Need to add Related List within #ServiceNow? Learn more about creating custom-defined relationships

Hey Everyone! Its been a little while since I've posted and to tell the truth its been a crazy few months. However, I wanted to take a break and thought this post from fellow Sherpa Valor Poland was a perfect... Continue Reading →

Enhancing the ServiceNow Nav Filter

Quick video to help with Enhancing the ServiceNow Nav filters. If you have questions, please let me know I am sure myself or one of my Cloud Sherpa professionals can help.

ServiceNow – How to control what comes back in the SOAP response with a View

TY! Good Stuff!

Techie Geek

Recently I have been getting a lot of questions and request about an old Knowledge presentation (concerning how we use views) to control a SOAP response. It may be best to blog it here and share.

First thing is first, lets create a special view on the incident table that only has number and short description and updated date. NOTE here: You want to create a view on the Incident Form if you are going to be getting an individual incident. There is a different list view when getting list. If you are getting list of incidents you would personalize the List Layout instead of the Form Layout in steps below.

Step 1: Open an Incident and Personalize Form Layout
Step 2: In the drop down section of the view select New (and give it a name).
Step 3: With your form view selected – pick the data you want…

View original post 414 more words

Dealing with XML API – Parsing the SOAP response

Techie Geek

Not gonna really try and show off anything here – but the documentation for XML API is a bit foggy and I want to share this. I tried to use a few common XML API calls that are a bit of a challenge to find out about.

Lets pretend you get a SOAP response and you want to manually iterate through that response envelope that has this structure:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body>
      <ns0:Root xmlns:ns0="http://Schemas.SNResponse_RigData">
         <Status>Success</Status>
         <RigData>Whatever</RigData>
      </ns0:Root>
   </s:Body>
</s:Envelope>

Here are a few API calls you will need:

      this.fSoapDoc = new XMLDocument(requestXML);
      var soapBody = this.fSoapDoc.getNode("/Envelope/Body/Root");

      var nodelist = soapBody.getChildNodes();
      for (var i=0; i < nodelist.getLength(); i++) {
          var kidNode = nodelist.item(i);
          if (kidNode.getNodeType() == Packages.org.w3c.dom.Node.ELEMENT_NODE) {
            var fieldName = Packages.com.glide.util.XMLUtil.getNodeNameNS(kidNode);
            var fieldValue = Packages.com.glide.util.XMLUtil.getAllText(kidNode);
            gs.log("FIELD NAME: " + fieldName, "cmaloy");
            gs.log("FIELD VALUE: " + fieldValue, "cmaloy");
          }         
      }

This is going to get the name and value of the Status…

View original post 47 more words

Powered by WordPress.com.

Up ↑

%d bloggers like this: