<?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: To use or not to use &#8211; Remedy core fields</title>
	<atom:link href="http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/feed/" rel="self" type="application/rss+xml" />
	<link>http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/</link>
	<description>Its all about Remedy</description>
	<lastBuildDate>Sat, 05 May 2012 15:45:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Venkat</title>
		<link>http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/comment-page-1/#comment-109</link>
		<dc:creator>Venkat</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:17:24 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=517#comment-109</guid>
		<description>May be there should be some way to disable them on forms that we don&#039;t need.

Anyway fields like Request ID, Created date, submitter, last modified by/date should be there for all the forms.

Regards,
Venkat</description>
		<content:encoded><![CDATA[<p>May be there should be some way to disable them on forms that we don&#8217;t need.</p>
<p>Anyway fields like Request ID, Created date, submitter, last modified by/date should be there for all the forms.</p>
<p>Regards,<br />
Venkat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Venkat</title>
		<link>http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/comment-page-1/#comment-106</link>
		<dc:creator>Venkat</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=517#comment-106</guid>
		<description>Hi Sonia,

I agree the fact that all fields are there for a reason but there are fields like Assigned to which we may reuse but when we try to map the fields with ID from another form and if they are used for different reasons, mapping will break.

In this scenario, we need to leave them alone, which may not be the best thing to do. 

Regards,
Venkat</description>
		<content:encoded><![CDATA[<p>Hi Sonia,</p>
<p>I agree the fact that all fields are there for a reason but there are fields like Assigned to which we may reuse but when we try to map the fields with ID from another form and if they are used for different reasons, mapping will break.</p>
<p>In this scenario, we need to leave them alone, which may not be the best thing to do. </p>
<p>Regards,<br />
Venkat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sonia</title>
		<link>http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/comment-page-1/#comment-102</link>
		<dc:creator>Sonia</dc:creator>
		<pubDate>Wed, 07 Oct 2009 16:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=517#comment-102</guid>
		<description>All the core fields are there for a reason and each field is important for its own reason, so its useless to debate their presence unless you can change the heads at BMC.</description>
		<content:encoded><![CDATA[<p>All the core fields are there for a reason and each field is important for its own reason, so its useless to debate their presence unless you can change the heads at BMC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeniffer</title>
		<link>http://remediesforremedy.com/2009/09/to-use-or-not-to-use-remedy-core-fields/comment-page-1/#comment-86</link>
		<dc:creator>Jeniffer</dc:creator>
		<pubDate>Mon, 05 Oct 2009 16:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=517#comment-86</guid>
		<description>I pesonally don&#039;t feel to use the core fields in the workflow and always wanted to find some way to delete the excess fields because it creates unnecessary problems while users create reports. 

The reason for not using them is I can&#039;t use match all fields by db on workflow and that&#039;s enough for me to neglect these fields.

Any thoughts.....
Jenni</description>
		<content:encoded><![CDATA[<p>I pesonally don&#8217;t feel to use the core fields in the workflow and always wanted to find some way to delete the excess fields because it creates unnecessary problems while users create reports. </p>
<p>The reason for not using them is I can&#8217;t use match all fields by db on workflow and that&#8217;s enough for me to neglect these fields.</p>
<p>Any thoughts&#8230;..<br />
Jenni</p>
]]></content:encoded>
	</item>
</channel>
</rss>

