. NET open source workflow Roadflow use and integration

Recently the company wants to organize the internal OA system, need to use to workflow, so began the open source workflow selection, use, to integrate into the company's internal system work.

First in the Internet search documents, oneself also have to add, tidy up several domestic work flow comparison, because not all break type research so insufficient place also hope Haihan.

To send the comparison content chart:

Given the table's content, combined with the company's technology and needs, we chose the Roadflow workflow engine.

Below embark on the journey of Roadflow.

Download, deployment, and use of Roadflow

Official website: http://cqroad.cn/

Official Document: Http://cqroad.cn/Doc/Default.aspx

Official source Download Link: http://cqroad.cn/Download

After the project download is complete,

1, from the database script, execute to the local database, it is OK.

2, open the project, because most of our company said the project is using MVC, so I choose Webmvc Project, remove WebForm project, can also keep to see Kazakhstan.

3, configure the database link string in the webconfig, note that there will generally be a version of the problem or mode problem, the Red page can be solved without much difficulty.

4, then is to open the/login/index page, follow the prompts to log in.

5, according to the document, oneself a little groping forward.

I groped almost, feel the company general process requirements here is can be satisfied, and consider the integration of cost and technology implementation, also feel no problem, after all, the code is in hand, haha. And then get up.

Roadflow Open source Workflow integration into the company's internal OA system

First understand a strange project, I was fencing from the database, because I look at his project structure, there is no very special thing, is the general MVC project.

The data structure is as follows:

1, basic platform: Log table, database configuration table, data dictionary table.

These tables in the Roadflow are almost single-table operation, relatively independent, do not have to do too much analysis on a glance.

2. Organizational structure, working Group, personnel information

3. Roles, permissions, personnel information

4, form, process, button, step, etc. workflow related core table

It is important to note that you build your own form field storage table, and then when binding the form, you can choose the data of their own data table for binding mapping.

After the analysis of the table structure, it is their own login rights integration and JS decompression analysis, integrated into the appropriate internal system. After all the hardships, it is easy to integrate the page.

Oh, when the middle bound custom event, encountered the reflection assembly path problem, here to give you a simple share. Modify the next path to do it.

<summary>////Execute custom Method///</summary>//<param name= "EventName" ></param> <returns></returns> public Object Executeflowcustomevent (string EventName, Object Eventpara MS, String dllName = "") {if (Dllname.isnullorempty ()) {dllName = EventName.                Substring (0, Eventname.lastindexof ('. '));            DllName = dllname.substring (0,dllname.lastindexof ('. '));            } System.Reflection.Assembly Assembly = System.Reflection.Assembly.Load (dllName);            String typeName = System.IO.Path.GetFileNameWithoutExtension (eventName);            String methodName = eventname.substring (typename.length + 1); Type type = assembly.            GetType (TypeName, true);            Object obj = System.Activator.CreateInstance (type, false); var method = type.            GetMethod (MethodName); if (Method! = null) {return method. Invoke (obj, new object[] {eventparams});            } else {throw new MissingMethodException (TypeName, methodName); }        }

Summary

Because workflows are not a small project, and are too complex, it is recommended that you use an open source framework without special requirements.

Also, if you also use the workflow, then we can exchange learning together, the upper left is my group, welcome to join.

Let me show you the results below.

Process Design Integration

Form Design Integration

Backlog integration

Well, good thing say three times, I again explained, if you have any criticism of this content or want to exchange learning together, welcome to the top left corner of my technical Exchange group.

Go shopping with my daughter-in-law tonight, the time is a little tight, finishing up a more than a picture of the blog, delayed my Redis, tomorrow insisted on my Redis series.

. NET open source workflow Roadflow use and integration