<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ServiceNow Guru &#187; Incident management Archives </title>
	<atom:link href="http://www.servicenowguru.com/tag/incident-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.servicenowguru.com</link>
	<description>ServiceNow Consulting Scripting Administration Development</description>
	<lastBuildDate>Mon, 30 Jan 2012 23:21:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Building a CI Change Calendar Macro &#8211; On The Fly</title>
		<link>http://www.servicenowguru.com/scripting/client-scripts-scripting/ci-change-calendar-macro/</link>
		<comments>http://www.servicenowguru.com/scripting/client-scripts-scripting/ci-change-calendar-macro/#comments</comments>
		<pubDate>Wed, 20 Jul 2011 12:39:19 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[UI macros]]></category>
		<category><![CDATA[Catalog client scripts]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Incident management]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3920</guid>
		<description><![CDATA[A co-worker asked me for some help yesterday fulfilling an interesting requirement. He needed to set up a configuration item reference field or catalog variable that would display a calendar macro that, when clicked, would open a popup window containing a change calendar report for that configuration item. I figured this idea might be of [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/client-scripts-scripting/ci-change-calendar-macro/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Track Affected CIs in One Place</title>
		<link>http://www.servicenowguru.com/cmdb/track-affected-cis-one-place/</link>
		<comments>http://www.servicenowguru.com/cmdb/track-affected-cis-one-place/#comments</comments>
		<pubDate>Fri, 27 May 2011 12:47:53 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[CMDB]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Problem management]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3740</guid>
		<description><![CDATA[I t should come as no surprise to you that, if used properly, your CMDB can be an extremely valuable input to your incident/problem/change processes. This is true not only of the actual CIs, but also the &#8216;Affected CI&#8217; records that you create. ServiceNow gives you a couple of different places to track this information. [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/cmdb/track-affected-cis-one-place/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Advanced Incident Management</title>
		<link>http://www.servicenowguru.com/service-now-general-knowledge/advanced-incident-management/</link>
		<comments>http://www.servicenowguru.com/service-now-general-knowledge/advanced-incident-management/#comments</comments>
		<pubDate>Thu, 26 May 2011 12:35:51 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[General knowledge]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[knowledge11]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3719</guid>
		<description><![CDATA[I had a great time presenting on Advanced Incident Management last week at Knowledge11. During that session I demonstrated a lot of very useful functionality that I&#8217;ve used and created to improve the standard incident management setup for technicians working in ServiceNow. Since most of my presentation was a demo, I promised the attendees that [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/service-now-general-knowledge/advanced-incident-management/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Incident Priority Lookup</title>
		<link>http://www.servicenowguru.com/system-definition/incident-priority-lookup/</link>
		<comments>http://www.servicenowguru.com/system-definition/incident-priority-lookup/#comments</comments>
		<pubDate>Mon, 23 May 2011 14:21:32 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[System Definition]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[knowledge11]]></category>
		<category><![CDATA[Priority]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3698</guid>
		<description><![CDATA[One of the basic pieces of any ITIL-based incident management setup is a priority matrix. Impact and Urgency drive a Priority calculation that can then be used to prioritize work and drive SLAs (among other things). ServiceNow comes with these prioritization fields and also includes a default calculation for you. While this setup works fine, [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-definition/incident-priority-lookup/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>On-call Calendar Popup UI Macro</title>
		<link>http://www.servicenowguru.com/system-ui/ui-macros/on-call-calendar-popup-ui-macro/</link>
		<comments>http://www.servicenowguru.com/system-ui/ui-macros/on-call-calendar-popup-ui-macro/#comments</comments>
		<pubDate>Mon, 09 May 2011 16:24:29 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[UI macros]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[On-call rotations]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3623</guid>
		<description><![CDATA[H ere&#8217;s a UI macro that I&#8217;ve used for a couple of clients that allows you to pop open an on-call rotation calendar for the group selected in any &#8216;Group&#8217; reference field in the system. This will probably be most useful for the &#8216;Assignment group&#8217; table that you use on the task table. As with [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-ui/ui-macros/on-call-calendar-popup-ui-macro/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Pause or Toggle a Time Worked Field Timer</title>
		<link>http://www.servicenowguru.com/scripting/client-scripts-scripting/pausetoggle-time-worked-field/</link>
		<comments>http://www.servicenowguru.com/scripting/client-scripts-scripting/pausetoggle-time-worked-field/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 14:57:29 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[System UI]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Time worked]]></category>
		<category><![CDATA[Timer]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3384</guid>
		<description><![CDATA[T here are several ways to do time tracking in Service-now. One of the ways used frequently (especially in Incident Management) is the &#8216;Time Worked&#8217; field. The Service-now wiki describes this functionality. I often see the requirement to have some control over the stop/start of this Time Worked field for customers using this functionality. This [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/client-scripts-scripting/pausetoggle-time-worked-field/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Calendar or Schedule-based Incident Autoclose</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/calendar-based-incident-autoclose/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/calendar-based-incident-autoclose/#comments</comments>
		<pubDate>Mon, 24 Jan 2011 16:43:03 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[autoclose]]></category>
		<category><![CDATA[calDateDiff]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Schedules]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=2097</guid>
		<description><![CDATA[S ervice-now provides the ability to automatically move incidents marked as &#8216;Resolved&#8217; into a &#8216;Closed&#8217; state after a certain number of days. In my experience I&#8217;ve found that this type of resolution/closure workflow is really the best way to configure your incident management setup because it allows end-users the ability to reopen incidents within a [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/calendar-based-incident-autoclose/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>New Call Call-taking Application</title>
		<link>http://www.servicenowguru.com/system-definition/new-call-application/</link>
		<comments>http://www.servicenowguru.com/system-definition/new-call-application/#comments</comments>
		<pubDate>Tue, 23 Nov 2010 11:58:04 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[System Definition]]></category>
		<category><![CDATA[Catalog client scripts]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[new call]]></category>
		<category><![CDATA[Service catalog]]></category>
		<category><![CDATA[UI actions]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=2809</guid>
		<description><![CDATA[While most IT departments do their best to educate their end users and help them to solve their own problems as they come up, the need for users to contact the Service Desk is something that will always be there. Ideally, this contact takes place through a support tool like Service-now but chances are you&#8217;ve [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-definition/new-call-application/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Assignment Rule Lookup</title>
		<link>http://www.servicenowguru.com/system-definition/assignment-rule-lookup/</link>
		<comments>http://www.servicenowguru.com/system-definition/assignment-rule-lookup/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 19:40:17 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[System Definition]]></category>
		<category><![CDATA[Assignment rules]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Problem management]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1553</guid>
		<description><![CDATA[Assignment rules allow you to specify conditions for which a particular assignment group and/or assigned to person should be assigned to work on a particular task. Assignment rules work fine, but as I&#8217;ve worked with clients I&#8217;ve come across some common scenarios that can&#8217;t be solved with the out-of-box setup. The primary issue with assignment [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-definition/assignment-rule-lookup/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Creating a Many-to-Many relationship in Service-now.com</title>
		<link>http://www.servicenowguru.com/system-definition/relationships/creating-manytomany-relationship-servicenowcom/</link>
		<comments>http://www.servicenowguru.com/system-definition/relationships/creating-manytomany-relationship-servicenowcom/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 20:09:05 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Relationships]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Many-to-Many]]></category>
		<category><![CDATA[One-to-Many]]></category>
		<category><![CDATA[Related lists]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=682</guid>
		<description><![CDATA[S ervice-now allows you to easily create relationships between tables without having to know a whole lot about the underlying table structure. If you&#8217;ve ever worked with a reference field then you&#8217;ve worked with one of these relationships. A reference field is simply a one-to-many relationship between 2 tables in Service-now. The &#8216;one&#8217; end of [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-definition/relationships/creating-manytomany-relationship-servicenowcom/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>One Field Shared Between Many Tables</title>
		<link>http://www.servicenowguru.com/scripting/one-field-shared-between-many-tables/</link>
		<comments>http://www.servicenowguru.com/scripting/one-field-shared-between-many-tables/#comments</comments>
		<pubDate>Fri, 01 Jan 2010 00:06:58 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[ACLs]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Dictionary]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Problem management]]></category>
		<category><![CDATA[Reference qualifiers]]></category>
		<category><![CDATA[System Security]]></category>
		<category><![CDATA[UI policy]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=594</guid>
		<description><![CDATA[One common problem I encounter with Service-now deployments has to do with the sharing of a field between many tables extended off of the same parent table.  Because the Task table and the Configuration Item table make heavy use of extended tables this is where I see the problem most often.  What is the best way to make changes to a shared field for the table that I'm working on, but not impact other tables that may be using the same field?]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/one-field-shared-between-many-tables/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>6 Plugins to install the first time you log in to your Service-now.com instance</title>
		<link>http://www.servicenowguru.com/scripting/6-essential-servicenow-plugins/</link>
		<comments>http://www.servicenowguru.com/scripting/6-essential-servicenow-plugins/#comments</comments>
		<pubDate>Thu, 31 Dec 2009 15:26:41 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[General knowledge]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Incident management]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Service Level management]]></category>
		<category><![CDATA[Surveys]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=432</guid>
		<description><![CDATA[If you're new to Service-now you're probably realizing that there are a lot of cool things that you can do with the product.  In most cases, the functionality you need is already set up and ready to go.  Other things can be accomplished by installing a plugin that fits your particular need.  In my experience, there are a few plugins that end up being used (or should be used) on almost every Service-now.com installation.]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/6-essential-servicenow-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

