Osworkflow: An exciting workflow engine

After learning, using, and developing the workflow engine for so long, agileflow has also been developed to version 0.8, but during this period
I have not found an engine that makes me feel excited. How can I reasonably locate the boundaries of the workflow engine and design it rationally to provide
It has been bothering me to give external interfaces a reasonable way for users to extend non-compilation methods. I tried
I know a lot of questions, but I cannot find a solution. I learned osworkflow these two days and finally found a very high feeling!
Osworkflow basically solves 98% of the problems I previously considered, and has the same idea in many aspects.
Provides the most powerful functions to ensure the simplest and clearest logic of the Code.
Mandatory restrictions. The following describes the restrictions:
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
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. osworkflow what should be done to the workflow engine, what should be done, what should be achieved, and my ideas are completely different
Consistent. Excited. Today I found my friend.