This week, the Gflow architecture is adjusted: comparison: http://blog.9cbs.neet/muse2008/archive/2004/10/15/137323.aspx1. Join log management in the bottom layer, operates, system action The error message is recorded, and the text file log log is not used because the system is considering the system pair .NET operation permission limit. 2. Add group management to the user management to facilitate the selection of people. 3. Increase the support process operation core module - the upper layer of the workflow engine (Fengine) is used as a control point, the operation process is started, and the retreat. Engine Call all possible function modules in the system to complete its scheduling function. 4. Increase the form of a single base (PageBase), longitudinally packaged all of the function modules, and the global variables that must be in transversely encapsulated. This is the base class that eventually do secondary development to the user. Users can modify this base class, join custom functions, or skip this layer, call the underlying module to complete the custom function. 5. User Custom Interface (UCI) Inherits PageBase for the Specific Business Processing page, the user secondary development, and adds the code to complete the business feature, call the function driver process in PageBase. If you have some suggestions, please reply, and I want to know the specific application of XML in the workflow. I hope interested friends will communicate together, my msn: museestudio@hotmail.com
