<?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"
	>
<channel>
	<title>Comments on: Common Sense in Short Supply</title>
	<atom:link href="http://www.bpm-research.com/2007/10/08/common-sense-in-short-supply/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bpm-research.com/2007/10/08/common-sense-in-short-supply/</link>
	<description>Standards, Research &#38; Innovation around Business Process Management and Workflow</description>
	<pubDate>Fri, 21 Nov 2008 02:48:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: daniel</title>
		<link>http://www.bpm-research.com/2007/10/08/common-sense-in-short-supply/#comment-445</link>
		<dc:creator>daniel</dc:creator>
		<pubDate>Thu, 17 Jul 2008 08:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bpm-research.com/2007/10/08/common-sense-in-short-supply/#comment-445</guid>
		<description>Thank you for the article. I am new in the BPM area, but I think it is the first approach I've seen, which suggests a 'better' process workflow in which failed client request should contain ALL failure reasons. All others stated something like: if client form misses an ID, inform him immediately about the missing ID and exit. And this is so simple and natural.

As for Absurdistan, I live in Romania - maybe you can visit us sometime...</description>
		<content:encoded><![CDATA[<p>Thank you for the article. I am new in the BPM area, but I think it is the first approach I&#8217;ve seen, which suggests a &#8216;better&#8217; process workflow in which failed client request should contain ALL failure reasons. All others stated something like: if client form misses an ID, inform him immediately about the missing ID and exit. And this is so simple and natural.</p>
<p>As for Absurdistan, I live in Romania - maybe you can visit us sometime&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
