As I mentioned yesterday, I am working on an update for Workflow for Movable Type 3.2. Version 1.5 of Workflow will be available only for Movable Type 3.2 and above and it will feature some changes (for the better) that MT 3.2 helps facilitate:
- No more external CGI scripts. There will be no need to install and configure a CGI script for Workflow. It will simply extend the functionality of the MT interface.
- Streamlined configuration. No longer will Workflow users have to step through a configuration setup process. All that you will have to do is visit the plugin configuration page and select who can and cannot publish entries. If you have any existing Workflow permissions settings, it will import them, otherwise reasoanble defaults will be used (only users who can edit all posts (i.e., Editors) can publish). The grant publish permission has been removed as MT now has its own controls over who can and cannot edit pluigin configurations.
- Dynamic template support. What few tags that are supplied by Workflow will be extended to support dynamic templates.
- Additional notification options. I still need to work out the specifics for this. Any suggestions are more than welcome.
I am also in the very early planning stages for Workflow 2.0. While I still have not fully fleshed out what I want to do with it, I will be working hard to ensure that one major feature makes it into the next big release of Workflow: entry workflow/revision tracking.
- Who first submitted the entry and when?
- Who has changed it since it was submitted and when?
- What changes were made and when?
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
This sounds like an interesting development. I'll keep my eye out for its release.
One feature I though might have a use is a way of limiting which authors an entry can be transferred to.
for example, Author 1 can only transfer to Authors 2 or 3.
Author 4 can transfer to any author, and so on.
That might make formalising the editing structure a bit easier.