servicenow

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 t...

Discovery Probes and Sensors Introduction Discovery is a module that servicenow provides in order to maintain CI's data that are present in the network of an organization. It is an automated process which means you just need to configure this and it will work on it's own i.e mannual intervention is not required ( given nothing is going wrong and you have configured it as expected) . The basic functionality of discovery is to knock the door of each and every device that are present in your network. Then classify which kind of device it is ex. computer, server etc. Then gathers the detailed information of the device like Serial number, Version and so on and populates all these data into the cmdb_ci table.  Now the one who is responsible for knocking the doors and gathering data is what is called Probe and the one who is responsible for analyzing these data and populating cmdb_ci table is what is called Sensor.  The one who does the coordination between the servicenow an...

Creating custom probe and sensor. Before starting this I assume you already know what is probe and sensor and what does it do.If you are not aware of probe and sensor then please go through this link first  Probes and Sensor. Here we will try implementing a very small and basic requirement. Once you understand how it works you can implement any complex requirement also. So here we will try to fetch the BIOS information of a windows system and will populate this result into the BIOS detail field ( which is a custom field that I have created ) of CI table . Let's start with probe first :- To create a probe follow the below steps :- 1. Under Discovery definition click on probes module. 2. Give a meaningful name to the probe. Ex. Windows-BIOS version . 3. The value in the ECC queue topic field appears in the ECC queue output record's "topic" field when this probe is launched.Since its a DOS command write Command in the field. Please ...