ProjectLevel of Complexity

Journey from SharePoint to Project and Portfolio Management

Project

Demand Management

2013 Workflow InfrastructureSharePoint 2013 workflows are powered by Windows Workflow Foundation 4 (WF), which was

substantially redesigned from previous versions. Windows Workflow Foundation, in turn, is built on

the messaging functionality that is provided by Windows Communication Foundation (WCF).

Perhaps the most prominent feature of the new workflow infrastructure is the introduction of

Windows Azure as the new workflow execution host. The workflow execution engine now lives

outside of SharePoint, in Windows Azure.

• By using Visio 2013, you can visually create a Project workflow,

export the workflow to SharePoint Designer 2013, and then publish

that workflow to a Project Web App site.

• Project Server 2013 workflows are built on the SharePoint 2013

workflow platform, which use version 4 of Windows Workflow

Foundation (WF4).

• Workflows in Project Server 2013 can be created by using

SharePoint Designer 2013 and are accessible for both on-premises

and online use.

• Project Server 2013 workflows are implemented in the new

SharePoint 2013 architecture.

• No More Code!!! - It is no longer necessary to use Visual Studio

and a .NET Framework language. However, workflows that require

programmatic access to Project Server that SharePoint Designer

does not provide, you must use Visual Studio 2012 with the client-

side object model (CSOM).

SharePoint 2013 Workflow Key enhancements to workflows in SharePoint 2013

• Enhanced connectivity to enable cloud-based execution of workflows. In

fact, there is 100 percent parity in SharePoint 2013 between on-premises

and Office 365 -based workflows.

• There is full interoperability in SharePoint 2013 with SharePoint 2010

workflows, which is enabled by using the SharePoint workflow interop .

• Enhanced authoring expressiveness by using SharePoint events and action,

web services, and classic programming structures, all in a declarative, no-

code environment.

• Scalability and robustness that is consistent with requirements for Office 365

and the Cloud App Model.

• Enhanced connectivity to promote highly functional integrated systems. You

can call and control your workflows from any external system. Additionally,

your workflow can make web service calls to any stream or data source

using common protocols like HTTP, SOAP, the Open Data protocol (OData),

and Representational State Transfer (REST).

• Enhanced authoring capabilities for the non-developer in SharePoint

Designer 2013, and the ability to compose workflow logic in Visio.

• Enhanced, and yet simplified, workflow development in Visual Studio,

including support for custom workflow actions, rapid development in a

declarative environment, single-step deployment, and support for

developing apps for SharePoint.

• Full support for workflow-powered apps for SharePoint, where workflows

function as the middle tier for business process management.

SharePoint Designer 2013

http://www.microsoft.com/en-us/download/details.aspx?id=35491

Visual Studio 2012

Creating and Importing a Workflow from Visio

Importing Workflow from Visio

Business analysts and process analysts who are already familiar with flowcharting

in Visio can use Visio to design a SharePoint workflow. The workflow in Visio

represents the business logic. After the business logic is complete, the workflow

can be exported to SharePoint Designer. Once the workflow is in SharePoint

Designer, an IT professional can wire it up to the SharePoint site.

SharePoint Designer 2013

SharePoint Designer Text Based Designer

In SharePoint Designer 2013, construct the workflow by using

declarative statements in the Text-Based Designer.

SharePoint Designer 2013 Visual Designer

You can edit items in the workflow by using the Visual Designer.

Working with Workflow in Visio

New Workflow ActionsAction Description

Assign a Task Assigns a single workflow task to a user or group.

Start a Task Process Initiates execution of a task process.

Go to This Stage Specifies the next stage in a workflow to which flow control

should be handed.

Call HTTP Web Service Functions as a method call to a Representational State Transfer

(REST) endpoint.

Start a List Workflow Starts a list-scoped workflow.

Start a Site Workflow Starts a site-scoped workflow.

Build DynamicValue Creates a new variable of type DynamicValue.

Get Property from DynamicValue Retrieves a property value from a specified variable of

type DynamicValue.

Count Items in DynamicValue Returns the number of rows in a variable of type DynamicValue.

Trim String Removes all leading and trailing white-space characters from the

current string.

New Workflow Actions

Action Description

Replace Substring in String Returns a new string in which all occurrences of a specified character or

string are replaced with another specified character or string.

Translate Document Functions as a wrapper around the HTTP activity that calls the synchronous

translation API. You must configure a Machine Translation Service

Application for the SharePoint site on which you run the workflow.

Set Workflow Status Updates workflow status as specified in message string.

Create a Project from Current Item [Microsoft

Project]

Creates a Project Server project based on the current item.

Set the current project stage status to this value

[Microsoft Project]

Sets the two status fields within the current stage of the project.

Set the status field in the idea list item to this

value [Microsoft Project]

Updates the status field of the original SharePoint list item.

Wait for Project Event [Microsoft Project] Pauses the current instance of the workflow to await a specified Project

event: Project checked in, Project committed, Project submitted.

Set this field in the project to this value

[Microsoft Project]

Sets the value for the enterprise custom field for a specified project.