Making a workflow Engine from scratch, what are your features?
csc_n00b via StackOverflow
Companies such as Activiti and jBPM have already created and implemented Workflow Engines with high level features such as...
- Worker (helper function) allocation and authentication to complete processes
- Worker task assignment and prioritization
- Ability to query the engine's processes/workers/tasks (a worker completes one or more of a set of tasks that all belong to one process)
- A persistent task queue
- History interface to view previous activities
If you could implement a Workflow Engine of your own, what features would you implement and why? Said in another way...if you could customize your own Workflow Engine, what features would you choose?
Thanks, Cameron
Please DO NOT REPLY directly to this email but go to StackOverflow:
http://stackoverflow.com/questions/24414192/making-a-workflow-engine-from-scratch-what-are-your-features
salaboy via StackOverflow
that's one of the questions that we are trying to answer with jBPM. Notice that jBPM is not just a Process Engine anymore. When the project decided to merge forces with the Drools team we started working together to build a whole platform of integrated technologies where new concepts and future technologies can be integrated with it. So I would say that if you have a process engine you will be likely to have a rules engine + any other technology that helps you to gather business knowledge to automate. In drools and jbpm there is a current effort to refactor the APIs so it allows easy integration with other frameworks which you might want when you use a process and rule engines.
HTH
Regards
Please DO NOT REPLY directly to this email but go to StackOverflow: