After summarizing the previous development lessons and experience, after testing in the actual environment, prepare the persistence layer of AgileFlow as follows:
described as follows:
1) This design guarantees the thermal upgrade characteristics of the business process, accompanying the heat upgrade of the workflow engine, the user's application system
You can upgrade
2) This design ensures rapid development of application systems
3) Combining the SelectionHelper component in the Common component concentration in the AgileFlow version 0.9, users do not need to consider the application system
Database design problem of the process operation section; of course, inquiry and report sections or suggestions as a persistent layer
4) I considered to change the Element of the field to Attribute, but found that more memory space is
5) Here is a pattern of a schedule, of course, a table is also possible, but after weighing, it is found
A process of a schedule is good
6) A pattern of a field can consider using a database method, but use file mode will not use it.
7) In order to facilitate processing, when defining fields, should also be separated by activity, consider defining in the Node definition of the process definition
Business data, so easy to handle when completing
8) This design allows the AgileFlow to transform into a BPM system
9) AgileFlow's future, not just a workflow engine, it is still a workflow application system and a BPM system development framework, it
The goal is to facilitate the rapid development of users, and ensure the flexibility, scalable and easy test of the architecture.
10) Workflow engine will be pluggable in AgileFlow, agile is an optional workflow engine, you can also choose Shark,
Other workflow engines such as OSWORKFLOW, JBPM, users do not need to modify any code, you can switch workflow engines
