SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 4

In the previous article SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 3 of this series on the Workflow migration Process we saw the execution of Steps 5 & 6 for the process.

In this article we are going to see the execution of Steps 7 & 8 and for the sake of quick review I am putting up the process diagram again in here.

Process Diagram

1

Step 7: Destination Site – Provision Workflow Export File

Once we are done successfully with the deployment of Content Type in Destination Site “Site002” then next move is to provision the Workflow export file that we have got from “Step 5” earlier

Here we will be using PowerShell Commands to get it deployed. We will be making use of “Add-SPSolution” & “Install-SPSolution” Cmdlets as shown below-

40

And that’s all. We are all done with the export process and now it time to finally test it in Destination Site “Site002”

Step 8: Destination Site – Test Workflow

In order the functioning of the Workflow do as follows-

  • Launch SharePoint Designer 2013
  • Connect to Destination Site “Site002”
  • Click on “Workflow” link in the left navigation

There we can see the “CustomerLogs” workflow under “Reusable Workflow” list

41

Now visit “CustomerCT” using Site Settings > Site Content Types

42

  • Click on the Content Type
  • Click on Workflow Settings

43

Click “Add a workflow” link to choose the workflow to associate with the content type

44

From the list of available workflows choose “CustomerLogs” and give it a logical name of your choice

45

That is how we get the workflow associated with the content type.

46

Now we need to create a list and add this content type to the list as we did it earlier

And finally you can create the item based on this content type

47Add some values and save the item

49

Once the item is created we can start the workflow as shown in the following steps-

Click on “Workflows” link

50

Start the “Log Customers” Workflow on the item

51

52

Once completed see for the status of the Workflow and the message logged by it in the history log

53

54

And we got the Workflow export process working like a charm.

That is all for this demo.

Hope you find it helpful.

 

Advertisements

SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 3

In the previous article SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 2 of this series on the Workflow migration Process we saw the execution of Steps 3 & 4 for the process.

In this article we are going to see the execution of Steps 5 & 6 and for the sake of quick review I am putting up the process diagram again in here.

Process Diagram

1

Step 5: Source Site – Export Workflow

So up till now we have tested the workflow and seem it is working all fine

Now finally it is time to move it out of Source Site “Site001”

  • Launch the SharePoint Designer 2013
  • Click on the Workflow in left navigation
  • Select “CustomerLogs” Workflow
  • Click on “Save as Template” from the Ribbon Control

33

This will export the workflow as .WSP file at the selected drive location

34

With this last action we are all done with the Source Site “Site001”

Please note that we have performed all the above steps just to simulate a proper business case where someone already created a Workflow and now we need to move it to some other SharePoint Site. In case if you already have a workflow created then you can always skip the steps above

Step 6: Destination Site – Provision Content Type

In order to move the Workflow based on the content type we need to first deploy the Content Type Solution to the Destination Site “Site002”

You should deploy it using PowerShell; in here I am making use of Visual Studio to get it deployed as shown below-

35

36

Once the Content Type Solution deployed successfully we should enable the feature to provision the Content Type

37

In order to verify if the Content Type has been provisioned correctly we should go as follows:

  • Go to Site Settings
  • Click on “Site Content Types” link

38

We can filter the list of available Content Types by “Custom Content Types” Group

And there we can see the “CustomerCT” content type provisioned correctly

39

 

That is all for this demo.

We will be looking for Step 7 & 8 in Part 4 of this Series.

SHAREPOINT 2013 : HOW TO MIGRATE SHAREPOINT 2010 STYLE WORKFLOWS – PART 4

So guys just stay tuned 🙂

 

SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 2

In the first article SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 1 of this series on the Workflow migration Process we saw the execution of Steps 1 & 2 for the process.

In this article we are going to see the execution of Steps 3 & 4 and for the sake of quick review I am putting up the process diagram again in here.

Process Diagram

1

Step 3: Source Site – Create Workflow

  • Launch the SharePoint 2013 Designer
  • Connect to the Source Site “Site001”
  • Click on the Workflows section on the left
  • Click on the “Reusable Workflow” Ribbon Control

9

  •  Specify the Workflow Name “CustomerLogs”
  • Select “CustomerCT” content type that we had provisioned in the earlier steps
  • And since this demo is to show how to export SharePoint 2010 Style Workflows so we should choose the Platform Type as “SharePoint 2010 Workflow”
  • Click OK to save the Workflow

10

We can see the new workflow created under “Reusable Workflow” Category

11

Step 4: Source Site – Test Workflow

Now we have to associate “CustomerLogs” workflow with Content Type “CustomerCT”

To add the association go to Site Settings > Site Content Types

12

Filter the content types by group “Custom Content Types”

We can see the “CustomerCT” Content Type available in the Site Content Types List

Click on “CustomerCT” Content Type and edit it

13

Under Settings section click on the “Work Settings”

14

Click on “Add a Workflow” Link

15

Under the Workflow Section you should see the “CustomerLogs” workflow list in Workflow Template list and specify a suitable name as “Customer Logging” in this case

Save the Workflow Settings

16

Now we can see new instance of “CustomerLogs” workflow associated with “CustomerCT” content type

17Now lets’ create a Test SharePoint List to verify the Workflow is working fine in association with Content Type

  • Go to Site Contents
  • Select “Custom List” list template to create a list

18

Let us call this list as “Customers” and click “Create”

19

We can see the “Customers” List created a successfully

20

Now we need to add “CustomerCT” content type to the “Customers” list

  • Go to List Settings
  • Click on the “Advanced Settings” link

21

  • Select “Yes” under “Content Types” Section
  • Save the settings

22

Click on the “Add from existing content types” link and select the “CustomerCT” content type

23

24

Now create a new item based on “CustomerCT” content type

25

  • Add suitable values to the fields

26Since we did not configured the “CustomerLogs” Workflow to start automatically on “Item Added” or “Item Updated” so we need to manually start it

27

Now lets’ review the workflow status

Click Ellipsis and select “Workflows” to get the Workflow Start Page

28

Click on the “Customer Logging” workflow to start

29

  • Click on “Start” button

30

And we got the workflow started & completed

31

We can verify the Workflow Status and also the message logged by it to the history log

32

That is all for this demo.

We will be looking for Step 5 & 6 in Part 3 of this Series.

SHAREPOINT 2013 : HOW TO MIGRATE SHAREPOINT 2010 STYLE WORKFLOWS – PART 3

So guys just stay tuned 🙂

SharePoint 2013 : How to migrate SharePoint 2010 Style Workflows – Part 1

In this article we are going to learn the steps that are involved in moving SharePoint 2010 style reusable workflows from one site to another and I must say this a bit of tricky process all around.

The whole process of exporting SharePoint 2010 Style Workflow involves 8 steps as showing below in Process flow diagram which I will be going to deliver as a series of four articles-

Process Diagram

1

So we can see that we got to go a long way in order to accomplish the task of moving workflow from one location to another so let’s hit the floor

Step 1: Create Site Collections

In order to setup this demo we need to first create two Sites lets’ call them “Site001” (Source) & “Site002” (Destination)

So the task is to move a reusable SharePoint 2010 Workflow from Source Site to Destination Site.

So we created both Source & Destination Sites as per usual process as shown below:

2

3Step 2: Source Site – Provision Content Type

In order to develop a reusable workflow in the Source site we would be needing a Content Type to be provisioned first based on that we can be able to create the require reusable workflow

In order to provision the Content Type lets create a solution and add a content type based on our business requirements.

Here for the sake of this demo I have added a Content Type called Customers with just two fields “Work Address” & “Company Name”

4

Lets’ name the feature associated with this content type as “Enable Customer Logging”

5

In order to provision the Content Type we need to deploy the solution and activate the “Enable Customer Logging” feature

6

In order to verify if the Content Type is provisioned we can go to Site Settings > Site Content Types

7

Filter the content types by group “Custom Content Types”

We can see the “CustomerCT” Content Type available in the Site Content Types List

8

That is all for this demo.

We will be looking for Step 3 & 4 in Part 2 of this Series.

SHAREPOINT 2013 : HOW TO MIGRATE SHAREPOINT 2010 STYLE WORKFLOWS – PART 2

So guys just stay tuned 🙂

 

SharePoint 2016 Administration : How to configure SharePoint Designer Settings using PowerShell

SharePoint Designer being a very powerful tool can be used to perform many operations inside SharePoint Environment, creating Workflows, External Content Types, Master Pages & Page Layouts Branding are to name a few of them.

Since Microsoft already announced that there will be no new version of SharePoint Designer to be released for SharePoint 2016 and the existing SharePoint Designer would be fully functional with it so it even becomes more important to understand the governance around this excellent tool.

Being a tool with reputation to perform so many actions it is utmost important to work around proper governance plan per Web Application basis to control this little beast.

In this article we will be going to walk through the steps and PowerShell Scripts involved in configuring the SharePoint Designer settings.

Before we start configuring the settings for SPD lets’ see what will happen if these settings are not enabled on Web Application Level

Search for SharePoint Designer and Launch it

1

Now try opening any Site using SharePoint Designer and boom

Got an error: Access Denied!

2

This is due to the fact that SPD usage permission has been revoked already we would be looking an obvious SharePoint Error saying access denied even if the user has full access the Site itself. This is because of the fact that SharePoint manages permissions for SPD and Sites separately.

Now in order to enable permissions for SPD we can go along with the following steps-

  • Launch Central Administration Site
  • Click on “General Application Settings”

3

  • Click on “Configure SharePoint Designer Settings” Link under SharePoint Designer Section

4

Select Web Application for which you want enable SharePoint Designer Settings

And in the screenshot below we can see there are four properties that need to be configured to get SPD up and running.

5Since we are looking for automating SharePoint Configurations using PowerShell so we will configure it by PowerShell way only.

Since this article is about implementing automation for SharePoint configurations using PowerShell, so we will go along with PowerShell only.

PowerShell Commands

  • Get Web Application Object that you want to enabled with SPD usage

$webAppObj = Get-SPWebApplication -Identity http://sp-2016-dev

  • Set AllowDesigner, AllowRevertFromTemplate, AllowMasterPageEditing, ShowURLStructure properties to “true” if you want all SPD features enabled for the Web Application

6

$webAppObj.AllowDesigner = $true

$webAppObj.AllowRevertFromTemplate = $true

$webAppObj.AllowMasterPageEditing = $true

$webAppObj.ShowURLStructure = $true

  • After setting the required properties don’t forget to call Web Application Update Method to save the changes back to database.

 $webAppObj.Update()

Execution

  • Launch SharePoint 2016 Management Shell
  • Run the above commands

7

Once the commands get executed we can go back to “SharePoint Designer Settings” Page to verify the changes to the properties persist.

8Now try connecting to the Site again

9

And since the permissions has been enabled to the Web Application for SPD Access you can be able to connect to the site with the Web Application as shown in the screen shots below-

10

11

That is all for this demo.

Hope you find it helpful.

SharePoint 2010 References

SharePoint 2010 Installation

  1. Managing and Implementing Microsoft SharePoint 2010 Projects
  2. Practical SharePoint 2010 Information Architecture

SharePoint 2010 Architecture & Governance

  1. Pro SharePoint 2010 Disaster Recovery and High Availability
  2. Pro SharePoint 2010 Governance

SharePoint 2010 Project Management

  1. SharePoint 2010 for Project Management, 2nd Edition
  2. Pro Project Management with SharePoint 2010

SharePoint 2010 Development

  1. Using Microsoft InfoPath 2010 with Microsoft SharePoint 2010 Step by Step
  2. Professional SharePoint 2010 Development
  3. SharePoint 2010 Development with Silverlight
  4. SharePoint 2010 Web Parts in Action
  5. Beginning SharePoint 2010
  6. Microsoft SharePoint 2010 Enterprise Applications on Windows Phone 7
  7. Inside Microsoft SharePoint 2010
  8. Microsoft SharePoint Foundation 2010 Inside Out

SharePoint 2010 Designer

  1. Pro SharePoint Designer 2010
  2. Beginning SharePoint Designer 2010
  3. Microsoft SharePoint Designer 2010 Step by Step

SharePoint 2010 Cloud Based Solution

  1. Developing Microsoft SharePoint Applications Using Windows Azure
  2. Professional SharePoint 2010 Cloud-Based Solutions
  3. Pro SharePoint 2010 Development for Office 365

SharePoint 2010 Search

  1. Pro SharePoint 2010 Search
  2. Working with Microsoft FAST Search Server 2010 for SharePoint

SharePoint 2010 PowerShell

  1. Microsoft SharePoint 2010 and Windows PowerShell 2.0

SharePoint Best Practices

  1. Expert SharePoint 2010 Practices

SharePoint 2010 Business Intelligence

  1. Professional Business Connectivity Services in SharePoint 2010
  2. Microsoft SharePoint 2010 Business Application Blueprints
  3. Microsoft SharePoint 2010 Business Intelligence Unleashed
  4. Microsoft SharePoint 2010 PerformancePoint Services Unleashed

SharePoint 2010 Branding

  1. Professional SharePoint 2010 Branding and User Interface Design
  2. Microsoft SharePoint 2010 Administration Cookbook

SharePoint 2010 Administration

  1. Pro SharePoint 2010 Administration
  2. SharePoint Server 2010 Administration 24 Hour Trainer

SharePoint 2010 Enterprise Content Management

  1. SharePoint Server 2010 Enterprise Content Management

SharePoint 2013 User Guides

  1. SharePoint 2010 at Work
  2. SharePoint 2010 Field Guide
  3. SharePoint 2010 Six-in-One
  4. SharePoint 2010 How-To
  5. Microsoft SharePoint Foundation 2010 Step by Step
  6. SharePoint 2010 All-in-One For Dummies
  7. Microsoft SharePoint Server 2010 Bible

SharePoint 2013: How to call OData Web Service End Point Using SharePoint Designer 2013 Workflows

In this article we are going to explore “Call HTTP Web Service” Workflow Action which is newly introduced in SharePoint 2013. In order to test this action will make use of OData Web Service End Point and target the following scenario where Customer Data needs to be auto populated based on the Customer ID using SharePoint Designer Workflow and OData Web Services.

Prerequisites:

  1. As this is going to be a List Workflow, make sure you must have a Custom List containing three columns “Customer ID”, “Full Name” and “Employer” already created on the site which you are going to select in Step 2 down the line. For the sake of this demo I have created a List with the name “Fill Customer Using Web Service” containing all the required columns.
  2. OData Web Service End Point http://services.odata.org/V2/Northwind/Northwind.svc should be accessible from the system which is running SharePoint Designer.
  3. Fiddler Web Proxy should be installed. You can get Fiddler from http://www.telerik.com/download/fiddler

Following are the steps involved in the development of Workflow Calling OData Web Service End Point:

Step-1 : Start SharePoint Designer 2013

Step-2 : Select the site in which you want to create the workflow

1

Step-3 : Go to left navigation pane and select Workflows

2

Step-4 : Select List Workflow [From Ribbon] > Select List [In our case it would be “Fill Customer Using Web Service”]

3

Step-5 : On the Workflow Designer select “Call HTTP Web Service” Action from the Action Ribbon Menu

4

Step-6 : Create the Workflow variables as shown below

5

Step-7 : Specify the Web Service End Point, and HTTP Method as shown below

6

Step-8 : Specify the variable of type Dictionary as placeholder for the incoming response data from the Web Service End Point

7

Step-9 : Now before proceeding any further lets’ analyze the response from the Web Service End Point. Please note that this step is of high importance and must not be neglected. Fiddler Web Proxy is your best friend when it comes to deal with Web Services. Analysis using Fiddler will provide us with the following Vital Information out of the response

  1. Structure of Data returned as a part of the response
  2. Properties Exposed by the Web Service End Point
  3. Data Types of the Properties
  4. Additional information on Error & Exceptions (If any)

8

Step-10 : After analyzing the data we come across the fact that we have got the required data in form of Key Value Pairs and the result set can be accessed by using the path “d/PropertyName”. So based on this knowledge we can now set the values for variable “CustomerName” & “CompanyName” using “Get an Item from a Dictionary” Action as shown below.

9

Step-11 :  As we have got the data from the Web Service End Point and stored in a set of variables, now it is time to update our list using “Set Field in Current Item” Action. We should use two instances of the same Action in order to set the value for both the fields using the variables as shown below

10

Step-12 : With this we are good to go. Now lets’ Save the Workflow Definition, Check for the Errors and if everything is fine Publish the Workflow.

13

14

15

16

17

Step-13 : In order to test the Workflow lets visit our List “Fill Customer Using Web Service” and quickly add a new item. We need to add the Customer ID only and rest of field will be populated by the Workflow

18

Step-14 : Specify the Customer ID and Save the item.

19

Step-15 : Start the Workflow on the newly added item.

20

21

Step-16 : And sure enough you will get the desired output with “FullName” and “Employer” Columns populated by our workflow using OData Web Service Call.

22

Though the scenario I mentioned here is quite simple, but this new add-on to SharePoint Designer 2013 is very powerful and could be utilized to cater complex business requirements without using any need of writing modules.

Hope this will help someone in need…