Add “Wait for Project Event” Action – Wait for Event: When project is “submitted”ī. Add “Include this stage” Condition – If Project Web App starts the workflow normally or restarts the workflow and includes this stageĪ.

Add “Log to History List” Action – Log “Project entered to the workflow history listħ.

Add “Set Workflow Variable” Action – Set Variable “CurrentStage” to “1.0 Idea”Ħ. Add “Set Workflow Variable” Action – Set Variable “ProjectCenterURL” to “”ĥ. Add “1.0 Idea” Stage (stage pre-defined in PWA > Server Settings > Manage Stages)Ĥ. Click on the “Site Workflow” button to create a new site-based workflow – being sure to select the “SharePoint Workflow 2013 – Project Server” platformģ. Start by opening Microsoft SharePoint Designer 2013 and then opening your Project Web App site, navigating to the “Workflows” section of the user-interfaceĢ. The Department categorisation creates a logic branch – determining the SharePoint “Approval” Group to send emails and/or create SharePoint workflow tasks – for this reason it is highly recommend to set this field as mandatory for all projects.ġ.

In the simple example below, Project Server 2013 Stages (via Server Settings > Manage Stages) have already been created, and projects have been categorised by Department (built-in lookup table / filter) being either a “Business” or “IT” Departmental project. It covers the maintenance of Steps, Actions and Conditions in the preparation of a multi-stage approval workflow, including workflow status and history list updates and branching logic.ĭocumenting workflow design using this approach assists stakeholders in comprehending business rules and general conditional logic followed during the implementation of a Project Server 2013 based PPM solution. This applies also to Microsoft Project Online.

Posted by: EPM Partners on August 20, 2014īelow is a reusable pattern for the design of Project Server 2013 / SharePoint Designer 2013 based approval workflows.

Ms project server 2013