The BPM.NET Suite is built for Microsoft Windows Workflow 4.0+. The purpose of the tool is to deliver the capability of Business Process Management for .net platform by leveraging the power of windows workflow.
The engine of BPM.NET suite is fully built on top of Windows Workflow 4+ and compatible with all the features provided by Standard Windows Workflow and Visual Studio such as Source Control, Debugging, Tracking Participants, WCF and Workflow Sql Instance Store, etc.
As BPM.NET strictly follows the standard of Windows Workflow, it can be seemlessly designed and hosted in IIS and Appfabric. Sample source codes are also avaiable under the commercial license to show IIS auto deployment using Microsoft Web Deploy and RESTful support using WCF REST.
The BPM.NET Designer is a standalone tool from the BPM.NET suite which helps to deliver a BPM authoring tool to the business users. The designer also provides features such as Execution, Tracking, and External Assembly Referencing etc. The defined process can be exported by the business users to the developers who can use the BPM.NET for Visual Studio to continue the development.
If you are a Windows Workflow developer, you would find it is extremely easy to migrate from a Flowchart workflow or any other windows workflow to a BPM workflow. We have samples to show you how easy and great it is! We are using the Hiring Process as our product sample which is officially provided by Microsoft.
Although human interactions can be in the body part of State activity with Receive activity etc, the Task activity is a more recommended way because it provides lots of features out of the box with best performance.
BPM.NET comes with APIs to retrieve Tasks from the instance store with different search criteria.
To submit the task back to the process, BPM.NET provides a customized WorkflowHostingEndpoint called BusinessProcessControlEndpoint. The endpoint also provides other actions such as assign a task to a user, assign a task to groups and change task due date etc.
In the Hiring Request sample, there are three Tracking Point been added to the process for tracking and reporting purpose. They are StartTP, RejectionTP and ApprovalTP. Based on these three tracking point in the process, it is quite easy to generate process statistic reports such as average processing time, count of rejected and approved requests in a period of time.
Functions can also be built to support the business users to have ad hoc report utilising the tracking data from the genertic Tracking Point.
See how our product helps you build process oriented report in Real Time:
Start from version 2.0, bpm.net adds new features for visual tracking. In the rehosted designer, all the activities except for the trigger in bpm.net can be highlighted. This is going to help the users find out the state in the whole process. You can see the sample from microsoft by clicking the link HERE. This is the screenshot of the visual tracking in bpm.net.