K2 Blackpearl: October 2011

Friday, October 21, 2011

Difference between SharePoint Workflow and K2 Workflow

From Development and Business Prospective:

	SharePoint Custom Workflow	K2 Blackperal Workflow
1	There are no in-build components by which it will be easy to integrate with SharePoint, Office 2007, and other backend systems.	K2 is built on top of WWF and they have a lot of nice components that make it easy to integrate with SharePoint, Office 2007, and other backend systems.
2	No Real time monitoring for each task.	You can find ‘Flow Diagram’ for the current status in graphical mode. You can also do real time monitoring of each task.
3	We need to write custom code for Error handling.	K2 introduces a ‘BlackPearl Workspace’ site which manages all for Error handing of each instance, managing workflow permission and tracking workflow process etc.
4	No web parts available for managing Tasks.	K2 Work list web part is available for managing Tasks.
5	No Context Browser available while development.	Here you will get content browser for all. E.g. SharePoint Environment browser, Mail Server Browser, Workflow Server Browser, Workflow process browser and Function browser etc.
6	No SharePoint Event available while development.	All SharePoint Events available. E.g. : · Manage Site and Workspace · Manage List/Library · Manager Site/List/List Item permission · SharePoint Search · SharePoint Record Management etc.
7	You can find only ‘Activity’ and you have to write code for each case.	Here you will find Activity with lots of event templates. Just drag them and use them.
8	Settings properties for each activity is not user friendly.	Here everything through wizard process (step-by-step) with nice GUI.
9	InfoPath integration with Workflow will require so many steps.	Here it’s cool to use and easy to interact with InfoPath data fields.
10	Custom Web Forms integrate with WF is very difficult.	Here it’s cool to use through wizard interface.
11	Development is difficult(Less feature, More code).	Development is easy and user friendly(More feature, less code).
12	Deployment is not user friendly	Deployment is easy.

Introduction to K2 Blackpearl

Introduction:

K2 blackpearl helps people create or amend process-driven applications through wizards and other graphical tools; and in most cases, no code is required. This simplicity and familiarity allows non-technical users to actually design, build and change these applications, rather than just trying to convey their needs to IT.

K2 Architecture:

The overall K2 architecture includes Microsoft components and K2 blackpearl-hosted server components. Depending on the role a server plays in the deployment, all or some of these components will be installed. At a high level, the K2 blackpearl Server uses common Microsoft components, such as the .NET 3.5 Framework with SP1, which includes Windows Workflow Foundations (WF) and Windows Presentation Foundation (WPF).

Sample Example:

Let us develop a multi level approval workflow in K2 Studio or K2 Designer. (In my next article I will show the process of development)

Test the K2 Workflow in SharePoint Site:

Once the development is ready we can deploy the K2 workflow project into a SharePoint List. So in the SharePoint List, we will create a new item and verify the workflow steps.

Step 1: Follow the below screen shot for below points.

· First we created a new item in Site Access Request List and then the workflow process started automatically.

· Now the workflow status will be In Progress and pending with the Manager.

You can see K2 Worklist web part which shows the current tasks assigned to corresponding users. Here you will also get context menu where you can take action for each task item.

· Now Manager will login and she can able to see her Task in the K2 Worklist. She can take action by clicking on ‘Open’ or ‘Action(s)’ menu.

Step 2: Manager opened the item and approved the item.

Step 3: Now the task will be pending with Director.

You can also watch the current flow of workflow process by clicking on ‘View Flow’ of the Task item in K2 Work list.

Step 4: Director opened the item and approved the item.

Step 5: Now the workflow process has been completed and you can verify the SharePoint Task List.

Step 6: You can also verify the flow diagram of the item workflow process.

Step 7: Finally you can see the workflow status of the list item.

Conclusion:

K2 provides all types of event which you can use in the workflow process to interact with SharePoint, SQL Database etc. So we do not require writing any code even if it will be complex business requirement.