Learning, use, developing workflow engine for so long, agileflow has also been developed to version 0.8, but during this whole period, I have not found an engine that makes me feel excited; how reasonable positioning workflow engine border, reasonable Designing it to the outside interface, how to reasonably let the user perform non-compile-compiled ways, have been plaguing me; I tried to give an answer in AgileFlow, but I will not be good, I don't know, I don't know. But it is not found.
Learn OsWorkflow these two days, I finally found the feeling of very high! OsWorkflow basically solved the 98% of the problems I have considered before, and in many ways, it is the same as my idea; it is guaranteed the simplest logic of the code Under clear conditions, the strongest function is given, and this function does not need to have any mandatory restrictions on the user.
Here is its description:. OSWorkflow can be considered a "low level" workflow implementation Situations like "loops" and "conditions" that might be represented by a graphical icon in other workflow systems must be "coded" in OSWorkflow That's not to. say that actual code is needed to implement situations like this, but a scripting language must be employed to specify these conditions. It is not expected that a non-technical user modify workflow. We've found that although some systems provide GUIs that allow for simple editing of workflows, the applications surrounding the workflow usually end up damaged when changes like these are made. We believe it is best for these changes to be made by a developer who is aware of each change. Having said that, the latest version provides A gui designer That Can Help with the editing of the workflow.
What should OSWORKFLOW should do, what should not do, what goals should be achieved, completely consistent with my ideas. Excited, I found a confidant today.
