Hi all, For a custom bug/issue/task tracker I was thinking about how to manage workflow. After some thinking I came to the solution to create a custom workflow engines based on state machines. Below is a summary of what I'm thinking about:
The main concepts are Object, State and Action. Objects have a State. Actions can change the State of an object. Rules determine which Actions are available for an Object in a certain state. Rules can also be subject to an ACL. The Statemanager is responsible for managing rules and state changes for a certain object. After initializing the Statemanager with the Object and Rules, an Action can be performed resulting in a state change. A more advanced version of the Statemanager could also dispatch Actions automatically. When there is only one possible Action and that Action doesn't require interaction, it could be performed. A similar concept might be a Trigger. Trigger are fired after a state change. Triggers don't have impact on the State of an Object. Further integration with the Zend Framework is possible. Actions that require user interaction should be able to communicate with Zend Controller. A special Workflow Controller could provide a kind of scaffolding access to the Statemanager. Another field of integration is on the Object side of things. Integration with models is almost a must. Integration with Zend_Db_Table, ActiveRecord and other automated model paterns would make sense. Does this sound a good plan to make a proposal? Anybody has a major issue to address before starting a proposal? Kind regards, Vincent de Lau [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Thoughts-about-Zend_Workflow-tp19279619p19279619.html Sent from the Zend Framework mailing list archive at Nabble.com.
