<?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; Change management Archives </title>
	<atom:link href="http://www.servicenowguru.com/tag/change-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>Sending iCalendar Invites from any Task table</title>
		<link>http://www.servicenowguru.com/system-definition/email-notifications-system-definition/sending-calendar-invites-task-table/</link>
		<comments>http://www.servicenowguru.com/system-definition/email-notifications-system-definition/sending-calendar-invites-task-table/#comments</comments>
		<pubDate>Thu, 09 Dec 2010 13:08:36 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Email Notifications]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Email notifications]]></category>
		<category><![CDATA[iCalendar]]></category>
		<category><![CDATA[Outlook]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1707</guid>
		<description><![CDATA[If you&#8217;re interested in this solution, you should also check out the ICS Request Processor, which allows you to subscribe to and pull iCal invites from tasks! S ervice-now has a pretty simple one-way Outlook calendar integration that you can use to send out iCal meeting requests and updates to assignees involved with a Change [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-definition/email-notifications-system-definition/sending-calendar-invites-task-table/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Change Management Workflow Approval Scripts in Service-now.com</title>
		<link>http://www.servicenowguru.com/scripting/change-management-workflow-approval-scripts-servicenowcom/</link>
		<comments>http://www.servicenowguru.com/scripting/change-management-workflow-approval-scripts-servicenowcom/#comments</comments>
		<pubDate>Wed, 20 Oct 2010 16:25:52 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Approvals]]></category>
		<category><![CDATA[Change management]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=2193</guid>
		<description><![CDATA[S ervice-now.com provides a really cool Graphical Workflow engine to help manage workflows for different tasks. This graphical workflow engine is particularly useful when working with approvals for Change Requests. As a Service-now.com consultant I&#8217;ve found that change approvals usually fall into just a few different types but new administrators and consultants sometimes don&#8217;t know [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/change-management-workflow-approval-scripts-servicenowcom/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Wait for Closure of all Tasks in Graphical Workflow</title>
		<link>http://www.servicenowguru.com/graphical-workflow/wait-closure-tasks-graphical-workflow/</link>
		<comments>http://www.servicenowguru.com/graphical-workflow/wait-closure-tasks-graphical-workflow/#comments</comments>
		<pubDate>Mon, 16 Aug 2010 14:57:14 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Service catalog]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1909</guid>
		<description><![CDATA[A common Graphical Workflow requirement in Service-now is to tell the workflow to wait for some trigger before continuing. The &#8216;Wait For condition&#8217; activity is available out-of-box and is very simple to configure. Usually when working with Service Requests or Change Requests I am asked how you can set up the workflow to wait for [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/graphical-workflow/wait-closure-tasks-graphical-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8216;Copy&#8217; UI action for Change requests (Part 2!)</title>
		<link>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests-part-2/</link>
		<comments>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests-part-2/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 16:42:41 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[UI actions]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1838</guid>
		<description><![CDATA[A few months ago I wrote about copying change requests using a UI action. While that method works great, it does require you to specify each and every field and value that you want to populate into the new change request. If you&#8217;ve got a lot of fields to copy over then you might end [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests-part-2/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Calculating Change Dates From Change Tasks</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/calculating-change-dates-change-tasks/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/calculating-change-dates-change-tasks/#comments</comments>
		<pubDate>Mon, 21 Jun 2010 17:47:01 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Dates]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1755</guid>
		<description><![CDATA[C hange management in Service-now includes the use of a parent &#8216;Change request&#8217; ticket and (usually) the use of multiple &#8216;Change task&#8217; tickets that can be assigned to separate groups or individuals to perform specific pieces of work. Because these change task tickets should factor into the overall plan for the parent change request, it [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/calculating-change-dates-change-tasks/feed/</wfw:commentRss>
		<slash:comments>0</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>Managing Ad-hoc Tasks in Service-now Workflow</title>
		<link>http://www.servicenowguru.com/graphical-workflow/managing-adhoc-tasks-servicenow-workflow/</link>
		<comments>http://www.servicenowguru.com/graphical-workflow/managing-adhoc-tasks-servicenow-workflow/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 22:19:25 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Service catalog]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=656</guid>
		<description><![CDATA[This post is written in response to a question I received from a reader about how to handle ad-hoc tasks when you&#8217;re using graphical workflow. I’m always open to suggestions on how to improve the site and its content. If you have any ideas, questions, or suggestions for the site just use the ‘Contact‘ link [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/graphical-workflow/managing-adhoc-tasks-servicenow-workflow/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Walking the Service-now.com CMDB Relationship Tree</title>
		<link>http://www.servicenowguru.com/scripting/script-includes-scripting/walking-servicenowcom-cmdb-relationship-tree/</link>
		<comments>http://www.servicenowguru.com/scripting/script-includes-scripting/walking-servicenowcom-cmdb-relationship-tree/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 20:08:52 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[CMDB]]></category>
		<category><![CDATA[Script includes]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Configuration management]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[UI actions]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=521</guid>
		<description><![CDATA[One 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.]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/script-includes-scripting/walking-servicenowcom-cmdb-relationship-tree/feed/</wfw:commentRss>
		<slash:comments>10</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>Canceling executing workflows on task closure</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/canceling-executing-workflows-task-closure/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/canceling-executing-workflows-task-closure/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 12:55:14 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Script includes]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=407</guid>
		<description><![CDATA[It is very common to use graphical workflow to help facilitate some change management process within your organization.  One common requirement in change management is to be able to cancel or close the change request at any time during the process.  "Simple", you say.  "Just allow the user to change the value of the 'State' field to 'Closed'." 
You would not be incorrect in saying something like that, but you would be forgetting about part of the problem with closing or canceling a change request or other task ticket.]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/canceling-executing-workflows-task-closure/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Reset change request workflow, approvals, and tasks</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/reset-change-request-workflow-approvals-tasks/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/reset-change-request-workflow-approvals-tasks/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 14:41:15 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[UI actions]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Client scripts]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=381</guid>
		<description><![CDATA[When implementing the Change management process in Service-now you'll probably encounter a scenario where your entire change workflow (including all tasks and approvals) needs to be reset.  The first option to consider (assuming you're using the graphical workflow engine to manage the tasks and approvals) is the Rollback workflow activity.  The rollback activity works great for a lot of scenarios, but what if you don't have a defined point in the workflow where everything should be rolled back?  What if the rollback (or reset) can happen at any point in time?  There's not really an easy way to handle this within the workflow itself since you would need to check for a rollback condition at an infinite number of places.]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/reset-change-request-workflow-approvals-tasks/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>&#8216;Copy&#8217; UI action for Change requests</title>
		<link>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests/</link>
		<comments>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 02:24:08 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[UI actions]]></category>
		<category><![CDATA[Change management]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=342</guid>
		<description><![CDATA[There are a variety of ways to implement copying functionality...]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/copy-ui-action-change-requests/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>

