<?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; Service-now.com Business rules scripting helps &#8211; tips, tricks, and more</title>
	<atom:link href="http://www.servicenowguru.com/topics/scripting/business-rules-scripting/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>Hide Empty Variables on a Standard Form</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/hide-empty-variables-standard-form/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/hide-empty-variables-standard-form/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 16:31:17 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Service catalog]]></category>
		<category><![CDATA[Variable Set]]></category>
		<category><![CDATA[Variables]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3826</guid>
		<description><![CDATA[S ervice catalog variables can be a challenge to deal with on standard forms when they are displayed in a variable editor. I&#8217;ve written before about different ways that you can solve one of these challenges&#8230;making the variables read only, so that they can&#8217;t be modified after the initial submission through the service catalog interface. [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/hide-empty-variables-standard-form/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Prevent Circular Relationships in Service-now</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/prevent-circular-relationships-servicenow/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/prevent-circular-relationships-servicenow/#comments</comments>
		<pubDate>Wed, 16 Mar 2011 12:52:59 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Script includes]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=3457</guid>
		<description><![CDATA[A lmost any database will have situations where a record in a table can relate back to other records in that same table. This happens in Service-now in several places and it&#8217;s common enough that you may find yourself building additional functionality that works this way. The classic case is the &#8216;Parent&#8217; field. A good [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/prevent-circular-relationships-servicenow/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>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>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>Readonly Variables on a Standard Form</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/variables-form-readonly/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/variables-form-readonly/#comments</comments>
		<pubDate>Sat, 22 May 2010 22:18:38 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[Client scripts]]></category>
		<category><![CDATA[Service catalog]]></category>
		<category><![CDATA[Variable Set]]></category>
		<category><![CDATA[Variables]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1706</guid>
		<description><![CDATA[A while ago I helped to answer a forum posting for someone who was looking for a way to present catalog variables to an end-user on a Request Item form but restrict the editing of those variables. At the time, I came up with a solution that worked, but that I really wasn&#8217;t happy with. [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/variables-form-readonly/feed/</wfw:commentRss>
		<slash:comments>43</slash:comments>
		</item>
		<item>
		<title>Advanced &#8216;getMyGroups&#8217; Function</title>
		<link>http://www.servicenowguru.com/scripting/business-rules-scripting/advanced-getmygroups-function/</link>
		<comments>http://www.servicenowguru.com/scripting/business-rules-scripting/advanced-getmygroups-function/#comments</comments>
		<pubDate>Tue, 04 May 2010 15:40:06 +0000</pubDate>
		<dc:creator>Mark Stanger</dc:creator>
				<category><![CDATA[Business rules]]></category>
		<category><![CDATA[System Definition]]></category>
		<category><![CDATA[getMyGroups]]></category>

		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1672</guid>
		<description><![CDATA[I f you’ve taken a look at the ‘My Groups Work’ module (or maybe a particular security rule or report) you may have noticed that the condition or filter for that record makes a function call to return a list of values to compare against the value in the given field. In the case of [...]]]></description>
		<wfw:commentRss>http://www.servicenowguru.com/scripting/business-rules-scripting/advanced-getmygroups-function/feed/</wfw:commentRss>
		<slash:comments>8</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>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>

