<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Best practices in Workflow Design - Part 2</title><link>http://msmvps.com/blogs/manoj/archive/2008/07/15/best-practices-in-workflow-design-part-2.aspx</link><description>Naming convention in Workflows Workflow activities should be named appropriately. As much as possible, they should reflect names form the business domain. For example, it wouldn&amp;rsquo;t appear good to have names like ifelseActivity1 or callExternalMethodActivity1</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator></channel></rss>