Posts Tagged ‘CMDB’
Posted by Mark Stanger in Client scripts Monday, 3 May 2010 07:26 1 Comment
A while ago I wrote about some of the different ways to customize the autocomplete search behavior for a reference field. I saw a forum post the other day where the poster asked if it was possible to create aliases for records so that they could be searched on. For example, what if you had a CI called ‘ABC’ but everybody knew it by the name of ‘XYZ’? While support for this type of searching isn’t really built into Service-now, it is possible to add this kind of behavior to a reference field. If the CI just had a single alias, you could probably just customize the display value and do a ‘contains’ autocomplete search as described in the article previously. For this specific scenario I think that there might be a better way to accomplish the same thing.
T
he Subscription-based Notification plugin allows Service-now users to manage their subscriptions for any notification in the system. It also allows users to subscribe to particular Configuration Items in your CMDB that they may be interested in.
As an administrator or process owner, it may be necessary for you to be able to view or report on which users have subscribed to updates for a particular configuration item. You may also want to see what configuration items a particular user has subscribed to without opening up their subscriptions page.
Posted by Mark Stanger in Scripting Tuesday, 19 January 2010 06:13 2 Comments
This customization DOES NOT come across in update sets! If you make this change you need to make it across all of your instances manually as soon as you verify the result in a dev or test instance.
S
ervice-now allows you to use and create extended tables to help organize your database structure. Out-of-box, there are 2 really important places that you’ll need to understand this setup. The first is the ‘task’ table (which includes incident, problem, change_request, etc.) and the second is the ‘cmdb_ci’ table (which contains every table in the Service-now CMDB).
One of the nice things about this type of arrangement is that it allows you to set up fields or columns on these tables that can be unique to a single table (‘caller_id’ on the Incident table) or available to all extensions of a parent table (‘short_description’ on the Task table). You can see if a table extends or is extended by another table by using the table schema map.
If you’re not careful when working with tables that are set up this way, you can get yourself into a little bit of trouble. Fortunately it’s not that difficult to work your way out of it most of the time. The biggest thing to be aware of when you’re creating fields on an extended table is to know what table you’re working on and what table(s) your new field should be available to.
If you do make a mistake, the easiest thing to do is just to catch it early and re-create the field. If that’s not possible then there is a command you can run that promotes a field from an extended table to a parent table. The function should be run from ‘System Definition -> Scripts – Background’ and works like this…
Posted by Mark Stanger in CMDB, Script includes Wednesday, 6 January 2010 13:08 1 Comment
O
ne of the great features of Service-now.com is its CMDB and relational mapping. You can easily set up relationships between any CIs in the system. Once the relationships are defined, it becomes very simple to pull up a visual representation of a CI and its dependencies by using Service-now BSM maps. Using this feature allows an end user to look at that CI and identify what else in the environment is impacted by an outage or a change to that CI.
Recent Comments