On Oct 19, 11:12 pm, Jeff Coughlin <[EMAIL PROTECTED]> wrote: > modius wrote: > > Workflow... watch this space.
We're working with a sponsor to build a framework for workflow. This will enable folks to add a lot of functionality between draft content and live content. Like all things we FarCry, we intend to include default behaviour that should let you hit the ground running. Workflow will follow the same extensibility guidelines as webskins -- ie. you will be able to use the default core, and override/extend workflow in plugins and the project. It will be built in phases. We plan to release Phase one with 4.1 -- though this is not set in stone. > It would be great if the workflow had a notification system that was a > little more detailed: > - There is currently an ownership piece built into FarCry that we're not > doing much with at the moment. Perhaps when "Requesting Approval", allow > the person who is requesting approval to request it from a group or a > single person (not multiple checkboxes, but one choice). Then not only > is it pending, but we know who currently is holding up the process (ie, > when clicking on an HTML object, it would not only say "pending", but > that person "XYZ" (or group "ABC") has been reviewing the item for "X" > period of time). The initial release will allow you to define a pool of tasks. These tasks can be tackled in any order. All tasks must be complete before a content item can move from draft to pending for approval. A task in essence will fire a view on the underlying content item. This view can be anything you want. Tasks will at least be bound to roles and possibly permissions. You will be able to independently generate reports, UI and alerts to users who are allowed to perform the task. > - Allow a publisher to forward a pending request to a different publisher. In phase one tasks will be bound to a role and not a specific user. However, we hope to include the ability to build your own escalation rules. > - The original requester gets an email letting them know it was rejected > or accepted and by whom (in case it was passed around) with a link to > the item in webtop and the frontend. We're replacing commentlog with a farLog content type. Log entries will represent all kinds of auditable activity in the framework. Combined with the ability to build your own escallation rules this will hopefully allow you to construct whatever alert you need. > - Be able to see a history of the item as it is being passed around and > reviewed (we already have a history view. During the review process, > knowing how long someone held onto an item could really help for > internal employee reports. Adding a column to the history page called > "Duration" which just calculates based on the already existing datetime > stamps could easily work). See above. > I have several more thoughts on workflow if interested :) We're always interested! Thanks for the feedback. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
