<?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; Problem management Archives </title>
	<atom:link href="http://www.servicenowguru.com/tag/problem-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>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>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>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>
	</channel>
</rss>

