Rehmani Consulting, Inc makes substantial efforts to keep SharePoint stakeholders, whether these individuals play a role as a line of business (LOB) decision-maker, or a role within an implementation and/or support team as an administrator, developer, architect, or SharePoint advocate, up to date with best practices with regards to using workflows to develop no-code processes for enterprise implementation on SharePoint. We see workflows as a very valuable feature of SharePoint, which, if successfully implemented, may provide the basis for a meaningful reduction in the cost of daily computing. One can review the type of effort that we make in this area by taking a look at the syllabus of our SharePoint Designer 2010: Create No-Code Solutions.
Therefore, we have spent the last few posts to this blog reviewing changes in SharePoint Designer 2013. In this post, we wish to provide further detail on Microsoft’s new Workflows in SharePoint 2013, a set of processes built on Workflow Manager Client 1.0, which is new for SharePoint 2013. In turn, we should note that Workflow Manager Client 1.0, which is an optional component of SharePoint 2013 (in fact, it must be installed and started independently of SharePoint Server 2013) is, itself, built on a new ” . . . Windows Workflow Foundation 4 (WF), which was substantially redesigned from previous versions” (quoted from the MSDN article, to which we have provided a link in this paragraph).
Microsoft has provided a granular summary of how to install and work with Workflow Manager Client 1.0 on Technet: Installing and configuring workflow for SharePoint Server 2013. As presented in this document, with SharePoint Designer 2013 there are now three different platform options for workflows:
- SharePoint 2010 Workflow
- SharePoint 2013 Workflow
- SharePoint 2013 Workflow – Project Server
Therefore, not only does SharePoint 2013 offer near complete support for workflows built with SharePoint Designer 2010 (which, in turn, was built on Windows Workflow Foundation 3); complete support for workflows built with Workflow Manager Client 1.0 (requires separate download, installation and pairing procedure for SharePoint 2013); but, finally, support for something called “SharePoint 2013 Project Server”.
It does not take much web searching to learn that “SharePoint 2013 Workflow – Project Server” is, in fact, a feature of Microsoft Project Server 2013. In a separate entry to MSDN, Getting started developing Project Server 2013 workflows, Microsoft presents some introductory details on using SharePoint Designer 2013 within Microsoft Project Server 2013.
As we demonstrated in our training set, SharePoint 2010: Project Management, SharePoint Designer 2010 can be used successfully, to configure workflows for project management. In the spirit of continuing our exploration of how SharePoint Designer 2013 differs from its predecessors, in the next post to this blog we will look further at how workflows can now be developed with SharePoint Designer 2013 for Microsoft Project Server 2013.
© IMB Enterprises, Inc. & Ira Michael Blonder, 2012 All Rights Reserved
on behalf of Rehmani Consulting, Inc.