servicenow

Coloring the Relationship in Dependency View We all have seen the Mono-Chrome look of the dependency view previously called BSM map.  Do you know, you can color code the relationship in the dependency view? Servicenow do gives this capability where you can color code different types of relationship in different color. Below is the way to do it. 1. Go to table Edge Colors [bsm_edge_color] and create a new record 2. Select the type of relationship that you want to color and select the desired color and save the form And that is all you needed to do. Now you can open any CI's dependency view and in whichever CI that relationship is there, it will be color coded. From the above example, in whichever CI's dependency view  Depends on::Used by relationship is there, it will be color coded in green

Inbound action is all about how servicenow responds when an email is received by the system. Based on the logic inbuilt in the system, email received is categorized as new/forward/reply, and then continues the processing.   What triggers inbound and what’s the frequency In every two minutes servicenow runs a schedule job named Email Reader. It connects to the mail server using the account specified in Email Properties. The Email Reader downloads any incoming message that is waiting on the mail server and creates email.read events . After the instance processes the events, the inbound actions run. Based on the logic inbuilt, it identifies whether email received is new/forward/reply.                Identification of the Sender of the email Servicenow identifies the user who sent the email based on the email id of the sender. As soon as servicenow receives the email, it matches the sender’s email id with all the user’s email id in the user table. if there is any match found t

  Hello all Readers,   I have seen many developers struggling and killing lots of their productive time in finding error/bugs in the code. Often they have no clue why the hell their code is not working the way it should. Now there could be 'N' number of reasons why your code migh not work, but how to know  ?    The most approached way I have seen that developers follow is using  alert()  method or  console.log()  method. This approach is no doubt helpful but, what if you are not sure at which line of code you are having data processing issue? You may end up with multiple alert messages and unknowingly you may end up irritating other people who are working on the form, as those alerts will popup on their screen as well    So, is there a way I can debug my client side code silently without using alert(s) and without bothering anyone else ?? Ofcourse,  YES !!!!   Before we go on to the soultion. Lets go to the basics of execution platform of client and server code.    Server side