<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Re-using Choice List Options in Fields and Variables</title>
	<atom:link href="http://www.servicenowguru.com/system-definition/reusing-choice-list-options/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.servicenowguru.com/system-definition/reusing-choice-list-options/</link>
	<description>ServiceNow Consulting Scripting Administration Development</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:04:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Stanger</title>
		<link>http://www.servicenowguru.com/system-definition/reusing-choice-list-options/comment-page-1/#comment-6371</link>
		<dc:creator>Mark Stanger</dc:creator>
		<pubDate>Mon, 07 Nov 2011 19:57:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1792#comment-6371</guid>
		<description>Unfortunately, there isn&#039;t a way to filter the results currently.  This actually seems like a bug to me though.  Inactive choices should never show up, regardless of where you&#039;re pulling them in from.  One way you might address this would be to set up a &#039;before query&#039; business rule.  You could easily filter out invalid choices for non-admins.  The other method would be to set up a regular choice list and dynamically populate the choices...or just set up the choices and maintain them in 2 places.</description>
		<content:encoded><![CDATA[<p>Unfortunately, there isn&#8217;t a way to filter the results currently.  This actually seems like a bug to me though.  Inactive choices should never show up, regardless of where you&#8217;re pulling them in from.  One way you might address this would be to set up a &#8216;before query&#8217; business rule.  You could easily filter out invalid choices for non-admins.  The other method would be to set up a regular choice list and dynamically populate the choices&#8230;or just set up the choices and maintain them in 2 places.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cary Trusty</title>
		<link>http://www.servicenowguru.com/system-definition/reusing-choice-list-options/comment-page-1/#comment-6370</link>
		<dc:creator>Cary Trusty</dc:creator>
		<pubDate>Mon, 07 Nov 2011 17:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.servicenowguru.com/?p=1792#comment-6370</guid>
		<description>I have used this a few times but this is the first time I&#039;ve noticed (or ran into this issue). I&#039;m using this select box on a wizard that is collecting information for a record producer at the end of the wizard.

On the actual Incident record, there are fewer choices than there are on the wizard. The reason for this is that the Choice field/list pulls in all variables (no conditions). On the Incident form, some choices are set to inactive=true. The wizard doesn&#039;t allow for a reference qual on the Selectbox option. Is there a way to use the attributes fields to filter where inactive=false?</description>
		<content:encoded><![CDATA[<p>I have used this a few times but this is the first time I&#8217;ve noticed (or ran into this issue). I&#8217;m using this select box on a wizard that is collecting information for a record producer at the end of the wizard.</p>
<p>On the actual Incident record, there are fewer choices than there are on the wizard. The reason for this is that the Choice field/list pulls in all variables (no conditions). On the Incident form, some choices are set to inactive=true. The wizard doesn&#8217;t allow for a reference qual on the Selectbox option. Is there a way to use the attributes fields to filter where inactive=false?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

