The main goal of this system needs to make actual users can easily set their own actual processes. Now it is mainly used on the approval process, which should be easy to use in other processes. Now talk about a few main ideas:
1. Rebra a set of UserManager modules to replace Shark. Shark is a built-in user table, which is changed to users directly using my existing system. easier. Because Shark is sealed, the UserManager module is changed, and all other don't move.
2. Some tables recorded access and methods were built outside of Shark. And hook with the specific documents.
3, the process design tool writes a set of non-Java programs, mainly maps, because there are ready-made process components. The goal is to easily make customers get up quickly, and customers don't have to know what packages, what Application.
In the process design, in addition to generating the corresponding XPDL file, UpdatePackage, User Maping, Application Mapping is automatically implemented.
4, other components involved in Worklist, relatively simple. Call some Shark's API directly.
5. Write a work allocation module to solve the problem of task allocation in accordance with the department attributable to the role.
6. At the same time, this system has an interface through the Socket port and my instant messaging tool. Relevant personnel can be notified by instant communication tools when task allocation can be implemented.
The entire system time spends more than the process design tool, because it is more difficult to let customers use it. Other time less. Now I am not too much time to do this, I can only deal with it. Fortunately, it can be used
I found that Shark is good, mainly slow, starting slow when starting. When someone's standby task reaches hundreds, the Worklist is overlooked throughout the time.
