<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>The Digital DoorMatt : workflows</title><link>http://blogs.technet.com/matt/archive/tags/workflows/default.aspx</link><description>Tags: workflows</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>SharePoint workflows and starting issues</title><link>http://blogs.technet.com/matt/archive/2008/01/17/2754730.aspx</link><pubDate>Thu, 17 Jan 2008 20:24:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2754730</guid><dc:creator>digitaldive</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/matt/comments/2754730.aspx</comments><wfw:commentRss>http://blogs.technet.com/matt/commentrss.aspx?PostID=2754730</wfw:commentRss><description>&lt;P&gt;Using a workflow in SharePoint is a very powerful tool.&amp;nbsp; Workflows allow for a greater degree of control and automation.&amp;nbsp; When a document is added or changed in a library or list, the workflow can be set up using the SharePoint Designer wizard to automatically create list items, send an email, create to-do items, and so forth.&amp;nbsp; You can also set conditions on whether the workflow runs (see screen shots below), for example, if a field contains a certain word or number.&amp;nbsp; Basic workflows can be also be inserted via the canned functionality in SharePoint.&amp;nbsp; Even though the wizard allows for more customization and control, it's a cinch to use.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_4.png" mce_href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_4.png"&gt;&lt;A href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_6.png" mce_href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_6.png"&gt;&lt;IMG style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" height=337 alt=image src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb_2.png" width=429 border=0 mce_src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb_2.png"&gt;&lt;/A&gt;&lt;IMG style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" height=338 alt=image src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb_1.png" width=432 border=0 mce_src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb_1.png"&gt;&lt;/A&gt;&amp;nbsp; &lt;/P&gt;
&lt;P&gt;I've been using workflows in a recent SharePoint creation to automatically send an email when an item is created in a document library.&amp;nbsp; The document was created and submitted via an InfoPath form.&amp;nbsp; However, I noticed a bizarre bug which I eventually found a workaround for.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;&lt;U&gt;The bug&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;On creating a new item, for the first document I added, the workflow ran fine.&amp;nbsp; However, for subsequent documents, the workflow would be shown as "Starting", and would not complete, no matter how long I left it (see screen shot below).&lt;/P&gt;
&lt;P&gt;&lt;A href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_2.png" mce_href="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_2.png"&gt;&lt;IMG style="BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px" height=174 alt=image src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb.png" width=159 border=0 mce_src="http://blogs.technet.com/blogfiles/matt/WindowsLiveWriter/SharePointworkflowsandstartingissues_F4CD/image_thumb.png"&gt;&lt;/A&gt; &lt;/P&gt;
&lt;P&gt;&lt;U&gt;The solution&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;I simply pointed the InfoPath form to a brand new document library, and then pointed it back to the original one.&amp;nbsp; This seemed to solve the issue, and the workflow worked fine from then on.&amp;nbsp; I'm not sure of the root cause of the problem (a SharePoint expert I talked to said it could be either server, the workflow itself or the document library causing problems), so I'm not suggesting this solution would work for everyone.&amp;nbsp; However, if you find that your workflows are not running for no discernable reason, and your conditions are set correctly, give this a go!&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2754730" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/matt/archive/tags/sharepoint/default.aspx">sharepoint</category><category domain="http://blogs.technet.com/matt/archive/tags/InfoPath/default.aspx">InfoPath</category><category domain="http://blogs.technet.com/matt/archive/tags/workflows/default.aspx">workflows</category></item></channel></rss>