<?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; Business rules Archives </title>
	<atom:link href="http://www.servicenowguru.com/tag/business-rules/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>Schedule-based Date/Time Addition</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/schedule-time-addition/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/schedule-time-addition/#comments</comments>
		<pubDate>Wed, 26 Oct 2011 15:53:50 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Dates]]></category>
		<category><![CDATA[Schedules]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=4076</guid>
		<description><![CDATA[I was recently asked to help a colleague figure out some date calculations based on a schedule. The requirement was to calculate a future date based on the existing value of a date/time field. I decided to document this solution (and come up with a solution for a similar problem&#8230;date addition from the current date/time [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/schedule-time-addition/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>What Everybody Should Know About ServiceNow Security</title>
		<link>http://www.servicenowguru.com/showcase/servicenow-security-tips/</link>
		<comments>http://www.servicenowguru.com/showcase/servicenow-security-tips/#comments</comments>
		<pubDate>Thu, 30 Jun 2011 16:56:51 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Showcase]]></category>
		<category><![CDATA[System Definition]]></category>
		<category><![CDATA[ACLs]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[System Security]]></category>
		<category><![CDATA[UI policy]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3638</guid>
		<description><![CDATA[Follow these guidelines to make sure you&#8217;re using the right security technique for every situation! S ecurity in ServiceNow is a very important, but often very confusing subject to get the hang of. ACLs, business rules, client scripts, and UI policies can all affect the security in your system to varying levels. Improper use of [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/showcase/servicenow-security-tips/feed/</wfw:commentRss>
		<slash:comments>5</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>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>Checking for Modified or Changed Fields in Script</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/checking-modified-fields-script/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/checking-modified-fields-script/#comments</comments>
		<pubDate>Thu, 20 Jan 2011 13:35:43 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Email notifications]]></category>
		<category><![CDATA[GlideRecord]]></category>
		<category><![CDATA[GlideRecordUtil]]></category>
		<category><![CDATA[mail_script]]></category>
		<category><![CDATA[modified]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3175</guid>
		<description><![CDATA[W orking in Service-now, you&#8217;ll find that a lot of scripting tasks come down to identifying which fields changed on a form (client-side) or record (server-side). In this post, I&#8217;ll show you some different techniques to identify changed fields in both client-side, and server-side scripts. I&#8217;ll also show you a way that you can capture [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/checking-modified-fields-script/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Fixing the Fatal Flaw of Before Query Business Rules</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/fixing-before-query-business-rules-flaw/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/fixing-before-query-business-rules-flaw/#comments</comments>
		<pubDate>Wed, 05 Jan 2011 16:30:07 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Reference field]]></category>
		<category><![CDATA[Reference qualifiers]]></category>
		<category><![CDATA[System Security]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3137</guid>
		<description><![CDATA[I &#8216;ve written before on SNCGuru about how &#8216;before query&#8217; business rules can (and should) be used to secure row-level read access to records in Service-now. While this usually works perfectly, there is one issue that I&#8217;ve seen come up continually that there hasn&#8217;t been a good fix for. Over the past few weeks, I&#8217;ve [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/fixing-before-query-business-rules-flaw/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Are YOU a ServiceNow Jedi?</title>
		<link>http://www.servicenowguru.com/showcase/service-now-jedi/</link>
		<comments>http://www.servicenowguru.com/showcase/service-now-jedi/#comments</comments>
		<pubDate>Sat, 27 Nov 2010 19:30:52 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[General knowledge]]></category>
		<category><![CDATA[Showcase]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Catalog client scripts]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Email notifications]]></category>
		<category><![CDATA[GlideRecord]]></category>
		<category><![CDATA[Graphical workflow]]></category>
		<category><![CDATA[Import Sets]]></category>
		<category><![CDATA[Service catalog]]></category>
		<category><![CDATA[UI policy]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1808</guid>
		<description><![CDATA[Whether you&#8217;re a new administrator or an experienced consultant, you need to know these things to become a master of the ServiceNow force. Since I started SNCGuru, I&#8217;ve had several people who were just starting their ServiceNow.com experience ask me what I would recommend they focus on to really start learning ServiceNow. I&#8217;ve wanted to [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/showcase/service-now-jedi/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Client &amp; Server Code in One UI Action</title>
		<link>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/client-server-code-ui-action/</link>
		<comments>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/client-server-code-ui-action/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 11:45:36 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[UI actions]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1962</guid>
		<description><![CDATA[M ost Service-now administrators and consultants know how to configure and use UI Actions. UI Actions are UI elements that can show up on a form or a list as a button, link, or context menu. When these UI elements are clicked they execute some JavaScript. Most of the time UI Actions are used to [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/system-ui/ui-actions-system-ui/client-server-code-ui-action/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Testing for a Valid Record</title>
		<link>http://www.servicenowguru.com/scripting/client-scripts-scripting/testing-valid-record/</link>
		<comments>http://www.servicenowguru.com/scripting/client-scripts-scripting/testing-valid-record/#comments</comments>
		<pubDate>Thu, 17 Jun 2010 19:38:00 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[UI policy]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1738</guid>
		<description><![CDATA[T oday I came across a scripting issue that I actually see quite often. I can&#8217;t ever remember it when I need it so I&#8217;m going to document it here. The issue is this: when working in a client script or business rule, I need to only have the script run if the record is [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/client-scripts-scripting/testing-valid-record/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identifying the sys_id Value of a Record</title>
		<link>http://www.servicenowguru.com/scripting/identifying-sysid-value/</link>
		<comments>http://www.servicenowguru.com/scripting/identifying-sysid-value/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 13:26:50 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[sys_id]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=939</guid>
		<description><![CDATA[S ys_id values uniquely identify each record in your Service-now instance database. While you should never try to modify these values, it is sometimes useful to know what the sys_id value is for a particular record. This article describes the different ways of identifying the sys_id value for a particular record. View the sys_id in [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/identifying-sysid-value/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GlideRecord Query Cheat Sheet</title>
		<link>http://www.servicenowguru.com/scripting/gliderecord-query-cheat-sheet/</link>
		<comments>http://www.servicenowguru.com/scripting/gliderecord-query-cheat-sheet/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 13:37:55 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Cheat Sheet]]></category>
		<category><![CDATA[GlideRecord]]></category>
		<category><![CDATA[UI actions]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1016</guid>
		<description><![CDATA[I doubt if there&#8217;s a single concept in Service-now that is more valuable to understand than how to use GlideRecord methods to query, insert, update, and delete records in your system. These methods have a wide variety of uses and are found at the heart of many of the business rules, UI actions, and scheduled [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/gliderecord-query-cheat-sheet/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Stopping Record Submission</title>
		<link>http://www.servicenowguru.com/scripting/stopping-record-submission-servicenow/</link>
		<comments>http://www.servicenowguru.com/scripting/stopping-record-submission-servicenow/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 23:10:14 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=933</guid>
		<description><![CDATA[A n important part of managing the flow of any record submission is to be able to validate the information from the form or record and provide feedback to the end-user if there is something that they need to change. While there are many ways to validate different kinds of data, preventing the submission of [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/stopping-record-submission-servicenow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding the Name or URL of your Instance via Script</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/finding-instance-name-via-script/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/finding-instance-name-via-script/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 13:53:40 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=714</guid>
		<description><![CDATA[H ere&#8217;s a quick tip that shows you how to retrieve the name or URL of your Service-now instance. This can come in handy if you need to construct a URL in a business rule or mail script or if you have some automated post-clone configuration when dealing with multiple Service-now instances in your environment. [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/finding-instance-name-via-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Parsing the Date and Time Sections from a Date/Time field</title>
		<link>http://www.servicenowguru.com/scripting/parsing-date-time-sections-from-datetime-field/</link>
		<comments>http://www.servicenowguru.com/scripting/parsing-date-time-sections-from-datetime-field/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 14:49:51 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Graphical workflow]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=634</guid>
		<description><![CDATA[H ere are some examples of how you could use a simple Javascript &#8216;split&#8217; method to parse out the date and/or time value from a date/time field.  Both examples split out the date and time, populate them into variables, and then populate the date section into a regular date field on the same record. Business [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/parsing-date-time-sections-from-datetime-field/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>JavaScript is not Java</title>
		<link>http://www.servicenowguru.com/scripting/javascript-java/</link>
		<comments>http://www.servicenowguru.com/scripting/javascript-java/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 19:46:20 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=619</guid>
		<description><![CDATA[A t some point somebody a lot smarter than me (probably the first person who reads this) will see the title of this article and say &#8220;No duh! JavaScript and Java are completely different. What a waste of an article!&#8221;. You can actually find quite a bit of information on this topic out on the [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/javascript-java/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Eliminating Duplicates from an Array with JavaScript</title>
		<link>http://www.servicenowguru.com/scripting/eliminating-duplicates-array-javascript/</link>
		<comments>http://www.servicenowguru.com/scripting/eliminating-duplicates-array-javascript/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 20:21:17 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=532</guid>
		<description><![CDATA[This is a great function that you can use to eliminate duplicates from an array in Service-now. It&#8217;s just standard JavaScript so it will work in Client Scripts, Business Rules, or pretty much anywhere else you want to put it. The function takes an array as the input parameter and returns an array&#8230;minus the duplicate [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/eliminating-duplicates-array-javascript/feed/</wfw:commentRss>
		<slash:comments>0</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>Controlling record access using &#8216;Before Query&#8217; business rules</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/controlling-record-access-before-query-business-rules/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/controlling-record-access-before-query-business-rules/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 17:44:48 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[System Security]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=514</guid>
		<description><![CDATA[System security is probably one of the more challenging things to implement in Service-now.com.  While an out-of-box Service-now instance comes with the core security built-in, any implementation will inevitably have customizations in this area.  At some point, I plan on writing a basic security guide to help administrators and consultants make informed decisions about how [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/controlling-record-access-before-query-business-rules/feed/</wfw:commentRss>
		<slash:comments>13</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>
	</channel>
</rss>

