Hello,
I looked for a workflow engine written in php and found the ez components workflow-classes (http://ezcomponents.org/docs/api/latest/introduction_Workflow.html). After work with the examples I have two general problems with the understanding of the (general) workflow-functionality:
1.) If I have defined a general workflow (for example for publish an article after a review) – each posted article has actually start a new “instance” of my general publish-workflow. Is this right? Or how does I handle it when the same workflow is used for many different articles/data-sets?
2.) How does the basis-application have to work with the workflow-component? If in the publish-process an email has to send to the person who has to review the article – where has the code placed for sending this email? Is it the right approach to send the email directly in the workflow, for example in the execute-method in a WorkflowServiceObject? Or does the sending of the email just placed in the application-code (after save an article or set the state of an article) and the state of the workflow has to set to the next node/level after sending the email?
Thanks for some answer (and sorry for my bad english ;-))!
Timo