<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx</link><description>During the past several months, we've seen a lot of questions about developing custom SharePoint workflows in the comments of various posts on this blog as well as in the SharePoint Workflow community forum . Many of the answers can be found in a recently</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Dew Drop - June 1, 2008 | Alvin Ashcraft's Morning Dew</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8567648</link><pubDate>Sun, 01 Jun 2008 16:59:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8567648</guid><dc:creator>Dew Drop - June 1, 2008 | Alvin Ashcraft's Morning Dew</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.alvinashcraft.com/2008/06/01/dew-drop-june-1-2008/"&gt;http://www.alvinashcraft.com/2008/06/01/dew-drop-june-1-2008/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8572156</link><pubDate>Wed, 04 Jun 2008 00:12:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8572156</guid><dc:creator>me</dc:creator><description>&lt;p&gt;When is Microsoft going to stop pushing the coding angle on all things, why can't there be a GUI interface that allows drag and drop of even custom workflow.&lt;/p&gt;
&lt;p&gt;gone are the days of coding come on get with the 21st century and lets all move on from this coding backwater&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8574020</link><pubDate>Thu, 05 Jun 2008 00:02:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8574020</guid><dc:creator>Zlatan</dc:creator><description>&lt;p&gt;Hi Me,&lt;/p&gt;
&lt;p&gt;Limitations of such Workflow engine solutions with the GUIs you mentioned is the main problem. &lt;/p&gt;
&lt;p&gt;Speaking from experience of dealing with various other ECM products in the past that in fact contained Workflow engines that featured dragging and dropping of configurable and even allowed for custom steps, there was hardly ever the case where a customer did not require something from me that the Workflow could not handle without a significant level of customisation. Problem with that is that such customisations are commonly far more complex then they should be and can de-stabilise the solution besides adding far more points of failure than it should.&lt;/p&gt;
&lt;p&gt;WWF for SharePoint provides the best way to ensure that proper Workflow solutions are created as part of the complete solution. Buidling such solutions in Visual Studio 2008 is far easier than the fatured MSDN article in this post would like you to think and it featuras a very good blend of drag and drop type of solution and code solution. I do however agree that it's not perfect and it can get much better, but as such it's still far better for creating proper ECM Workflow solutions than today's drag and drop Workflow engines. Also, available third party solutions that can complement SharePoint 2007 instead of WWF are not really that great.&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8586182</link><pubDate>Mon, 09 Jun 2008 18:38:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8586182</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;Is that not what &amp;quot;SharePoint Designer&amp;quot;(SPD)is for??&lt;/p&gt;
&lt;p&gt;I have designed several work flows using designer and never had to directly touch the code.&lt;/p&gt;
&lt;p&gt;Granted, there are some limitations, but it is far better than the Out Of The Box functionality.&lt;/p&gt;
&lt;p&gt;If the work flow is so complex that you can not accomplish it in SPD, then code would be the answer...&lt;/p&gt;
&lt;p&gt;If you don't like to code, I would ask why you are a developer then... (not to be rude, just a question)&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8591999</link><pubDate>Wed, 11 Jun 2008 22:33:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8591999</guid><dc:creator>lucas</dc:creator><description>&lt;p&gt;not a rude question, Joshua, an excellent one&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8592332</link><pubDate>Thu, 12 Jun 2008 02:12:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8592332</guid><dc:creator>Levi</dc:creator><description>&lt;p&gt;We'll never be done with code, because by the time all the GUI interfaces enable us to do what we're doing in code right now, they'll be a whole new generation of technology that we'll be coding, that GUIs have not be made for yet. We are developers. We code. It's what we do!&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8767731</link><pubDate>Thu, 24 Jul 2008 00:21:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8767731</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;Does someone has used a workflow for SharePoint is called kaldeera?&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8906401</link><pubDate>Fri, 29 Aug 2008 22:17:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8906401</guid><dc:creator>Rebecca McWilliams</dc:creator><description>&lt;p&gt;My users have created approval workflows for document publication. The want the approver to be able to open the document and make changes. Why are documents in read only format when working with workflows? Does anyone know a simple work around?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Rebecca&lt;/p&gt;
&lt;p&gt;rebeccamcwilliams@wellsfargo.com&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8926291</link><pubDate>Fri, 05 Sep 2008 16:19:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8926291</guid><dc:creator>Frank</dc:creator><description>&lt;p&gt;Has anyone created an &amp;quot;end of task&amp;quot; workflow yet? I would like to be notified when a task's completion percentage reaches 100%.&lt;/p&gt;
&lt;p&gt;Thanks in advance&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#8965106</link><pubDate>Thu, 25 Sep 2008 17:56:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8965106</guid><dc:creator>Wendy Suydam</dc:creator><description>&lt;p&gt;I'm learning about workflow set-ups and would like to have a workflow associated with a particular library in SharePoint and not a single document, is this possible? &amp;nbsp;How would I set it up. &amp;nbsp;I have been exploring and do not see that the system has that capability. &amp;nbsp;Is there a work around? &amp;nbsp;Can I attach several documents to a workflow instead of just one document? &amp;nbsp;Can I set up individual workflows and then link workflows so that one starts upon the completion of another workflow (so that I can attach different documents in a library)?&lt;/p&gt;</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#9359136</link><pubDate>Thu, 22 Jan 2009 00:35:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9359136</guid><dc:creator>tomsrig</dc:creator><description>&lt;p&gt;I have read all the tutorials for Sharepoint Designer workflow develoment. &amp;nbsp;I am looking for a list of what actions are available, and what type of calculations a workflow can accept. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am trying to find a way to make a workflow calculate a new date and time by adding minutes to it. &amp;nbsp;Example 30minutes is added to 1/20/09 1:00Pm. &amp;nbsp;Answer should be 1/20/09 1:30Pm.&lt;/p&gt;
&lt;p&gt;Can this be done using a workflow?&lt;/p&gt;
</description></item><item><title>re: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation</title><link>http://blogs.msdn.com/sharepoint/archive/2008/05/31/developing-workflow-solutions-with-sharepoint-server-2007-and-windows-workflow-foundation.aspx#9392386</link><pubDate>Tue, 03 Feb 2009 05:15:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9392386</guid><dc:creator>wickid1ne</dc:creator><description>&lt;p&gt;I am trying to expand on the Sales Lead Pipeline Solution Template. The template was set up to convert a lead to an opportunity. our company has asked me to modify the site and create a second Workflow on the opportunities list to convert to a Project. I have created the new workflow with SD and created a &amp;quot;Convert an Opportunity&amp;quot; Link just under the Convert a Lead Link on the QL Bar and modified my Data view to include an input button titled &amp;quot;Project&amp;quot; that navigates to the Workflow Form to start the workflow. But i am getting a error when i try to use the workflow through this method. I can start the workflow from an individual items edit menu but not from the quick access Input button and Convert Page. It is as if my input button works to navigate to the new page but does not transfer teh info for the item that i am trying to convert What am i missing???? I have looked all over the provided workflow and i am stuck &lt;/p&gt;
&lt;p&gt;HELP&lt;/p&gt;
</description></item></channel></rss>