You sent a post to the list in July stating you (Daemon) were working on specs for a plugin-able workflow object, in terms of an API for custom workflow methods.
I was just wondering what the progress was on this (either the basic specs or an API). I'm interested how this would work
Well I have started the spec :) But its not ready for prime time. I'll release to the site for review and comment given its such a major piece of work.
You mentioned in that post that there would likely be a config for workflow, where the workflow object type would be specified. I'd wonder how you'd attach different workflow types to different parts of a tree. For instance (using examples from other posts in that thread), one department required only a serial path for approval, whereas another department needed approval from a committee
What I'm trying to work through for workflow is ambitious. Essentially I want to set up a workflow object with templates that correspond to individual workflows -- ie so you can customise the workflow easily for each installation.
The idea of a specific workflow object is so that you can have default workflow in the system -- replicating existing functionality -- but be able to overide this workflow with a template for specific content types, roles or even object instances.
The proposed workflow object has a WDDX routing slip that keeps track of the workflow instance data: including steps of the workflow, current progress and so on. This will hopefully allow users to create an instance specific workflow within the contraints of the provided template -- eg. they might select the individuals they want to approve from a list of approvers.
I'll post more as we have it... I'm working on this part-time until we have a corporate sponsor (any takers?).
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
