As Heather OCull wrote on September 18, 2012 on the Microsoft Project Blog (which is published on the Office Blogs web site), ” . . . You can now create Project workflows [for Microsoft Project Server 2013] in SharePoint Designer  in addition to Visual Studio. . . . these improvements make the whole process significantly easier: with very limited coding knowledge, you can create complex Project workflows to manage the lifecycle of a wide range of proposals.”
Certainly, from our perspective at Rehmani Consulting, Inc., this expansion of the range of development options for Microsoft Project 2013 workflows to include no-code methods built with SharePoint Designer 2013, is very good news. Organizations committed to empowering line of business (LOB) users to “self maintain” through IT project life cycles can now provision SharePoint 2013, SharePoint Designer 2013 and Microsoft Project Server 2013 to LOBs, train them on best practices to exploit the capabilities of each of these tools, and, realistically, successfully achieve their objectives — at least on paper.
Of course, including SharePoint Designer as a legitimate, supported method of building workflows for Microsoft Project Server 2013 increases the usefulness, and, value, of SharePoint Designer 2013 as a tool that can serve well, whether the objective is building processes for SharePoint Server 2013 or for Project Server. It is also of interest to us that Ms. OCull’s blog post also presents a role in this process for Visio 2013, which, as we wrote earlier in our current series of posts, has taken on a larger role for workflow production in SharePoint Server 2013.
We think that the new uniformity of workflow development options that has been created for a range of Microsoft 2013 platforms will likely increase interest on the part of enterprise business users. Further, as this new uniformity is built, solidly, around no-code options (from Visio 2013 and SharePoint Designer 2013) enterprise IT organizations will likely look to capture two key benefits:
- a lower cost of development as reliance on Visual Studio is, to some extent, reduced through the presentation of no-code development options
- and, in all likelihood, wider user adoption of these platforms as the result of several factors, not the least of which being the likelihood that LOBs will be more successful at self managing their own development requirements when they can avail of no-code tools
In sum, now that SharePoint Designer 2013 has been established as a legitimate workflow development resource for Microsoft Project Server 2013, it should be clear to enterprise IT organizations that training users to successfully exploit the capabilities of each of these tools makes sense. We welcome opportunities to speak with prospects interested in hearing further as to the training options that are available. Please do visit our web site, SharePoint-Videos.com to learn more about our training content and consulting offers. You can contact us to learn more about what we may be able to do to help your organization achieve your objectives.
© IMB Enterprises, Inc. & Ira Michael Blonder, 2012 All Rights Reserved
on behalf of Rehmani Consulting, Inc.