Knock, knock who is there?

General No Comments »
by:


In ServiceNow out of the box it is possible to restrict access to the instance based on IP address. When access is revoked the following page is visible below.
Continue reading…»

Discovery and creating new CIs

General 1 Comment »
by:

If discovery tools are used within ServiceNow it can happen that based on the information provided it is not possible to determine the specific CI Class in ServiceNow. Therefore it could be useful to change the class after creation. This is possible as described in the following article by a colleague of mine: Change the Class of a CI. This article enables the option for the end user (without admin access) to change the ServiceNow CI class.
Continue reading…»

Archiving with unique fields

General No Comments »
by:

In the instances which have the Berlin or a later release installed, the archiving functionality is enabled. The application “System Archiving” is available. Archiving rules are used to determine which tables are archived and for which tables a corresponding archiving table should be created. All the archiving tables are named ar for example the incident table will have an arincident table if an active archiving rule is defined.
What happens if the “number” field on the task table is set as a unique field in the dictionary table?
kelvin1
Continue reading…»

Like Calculated Fields, but easier and allowing more flexibility…

General 2 Comments »
by:

Would it not be handy to have a way to fill in a field based on some rules in combination with existing field values? Kind of the functionality you can achieve with Calculated Fields?
For example a naming convention to determine the name of a CI, and also in a flexible way?

In this blog article a solution will be demonstrated with the corresponding update set at the end to deploy it on your own instance.
It introduces more flexibility than out-of-the-box Calculated Fields in ServiceNow and can be used on multiple tables/fields without the need for specific scripting – as would be required when using Calculated Fields. It’s all managed from just 2 tables.

The solution consists of the following functionality

Functionality Name
Table Name Convention (u_name_conv)

  • u_table (string – table_name)
  • u_field (string)
Table Name Convention values (u_name_conv_val)

  • u_name_conv (reference)
  • u_type (choice)
  • u_value (string)
  • u_order (string)
Script Include ExtNumbMaint
Business Rule useNumbMaint
UI Action Tidy up order

In the table “Name Convention” and “Name Convention Values” all the logic for the naming is determined and registered. The “Name Convention” stores the table and the field on which you want to perform the name convention. The “Name Convention Values” table defines the values you want to use and in which order you want to use them. There are two ways to determine a value:
Continue reading…»

Capturing end user feedback at Incident Resolving

General No Comments »
by:

Let me capture that...

In the ServiceNow out of the box setting there is a button which allows the user to resolve the incident. This button sets the incident to state Resolved.
This functionality is provided by a UI Action and a Business Rule. However, all incidents that are resolved this way are provided with a standard ServiceNow text.

Below I’ve included the ServiceNow out-of-the-box UI Action and Business Rule that facilitate the default functionality.

Functionality 

UI Action 

Name 

Resolve Incident 

Condition 

(current.incident_state != 7 && current.incident_state != 6) && (gs.hasRole(“itil”) || gs.hasRole(“itil_admin”) || current.caller_id == gs.getUserID())

Script 

current.incident_state = 6;

current.update(); 

 

Continue reading…»

Export different record(s) from different tables into one XML

General 2 Comments »
by:

In Service-now (SNC) it is possible to export records into one XML file. This action can be performed in the list view or on a single record.


Unfortunately this only exports the records on one single table, in this example the incident table. For other purposes, for example use the XML file to convert it to another format (Word) or use this file for an initial load to an external system this is not usable. For this solution a complete export from different tables is needed. For example a change request with all the affected CI’s and approvals related to the change and all the individual change tasks.

In the out of the box SNC implementation it is possible to export a complete update set into one XML file, question is, is this usable?
Yes it is!
J
In this article I will explain how to configure this and which components are needed.
Continue reading…»