Experience of Using shark to complete the actual workflow system

The main goal of this system is to allow actual users to easily set their own actual processes. Now it is mainly used in the approval process, and it should be easy to use it in other processes. Here are some main ideas:

1. Write a set of usermanager modules to replace shark. Shark is built into a set of user tables, the system is changed to directly use my existing system users. Relatively simple. Because the shark is encapsulated, The usermanager module is changed, and nothing else is changed.

2. In addition to shark, some other tables are created to record the processing opinions and methods. And linked to specific documents.

3. Process Design tools use non-JavaProgramI wrote a set of key graph characters because there are ready-made process components. The goal is to make it easy for customers to get started quickly. Customers do not need to know any package or application.

In the process design, in addition to generating the corresponding xpdl files, the updatepackage, user maping, and application mapping are automatically implemented.

4. It is relatively simple to use worklist. You can call some shark APIs directly.

5. Write a work assignment module to solve the problem of assigning tasks by role and department ownership.

6. At the same time, the system has interfaces with my own instant messaging tool through the socket port. You can use instant messaging tools to notify relevant personnel when assigning tasks.

The whole system takes a little more time on the process design tool, because it is difficult for the customer to use it easily. Other time is relatively small. It is a pity that I have not had much time to do this, and I have to deal with it first. Fortunately, it can basically be used.

It is found that shark is good for others, mainly because it is slow and starts slowly. When someone has hundreds of pending tasks, the worklist time is very slow.