For my current project, I use the Workbench Moderation module to let my editors set states on their articles and others interact with nodes which have certain states. The automated revisioning and setting up custom permissions on each state, where some users may perform only certain transitions is a cool thing that delivers this module.

I have a customer request where the last state (in Workbench Moderation it's usually the published state) should not be published, but simply 'done', which stands for that this article has no more tasks. This does not mean that this article should be published. The editors should instead be able to seperately determine if this article is being published or not (As already implemented by Drupal Core).

This feature request would bring some major changes to Workbench Moderation's behavior when the published state will be optional. At the moment, when you create a new version of an already published node, Workbench Moderation does not set this new one to be published (status == 1), the editor has to do this manually. When this feature request would come into the module, Workbench Moderation just should not care about this at the last state.

Maybe additional configuration UI should be provided, like a checkbox next to "Delete" for "Publish on this state" in admin/config/workbench/moderation.

Thanks for your time and feedback.

Comments

srjosh’s picture

Could you just make a "Done" state and have all transitions eventually lead to that, and only allow "publish" from that state?

Manuel Garcia’s picture

Issue summary: View changes

I think what @sqrt was going for here is to be able use workbench_moderation for other workflows other than content moderation, say for example a complaint system, where different users get involved in the workflow at different states, etc. In those situations, the only thing preventing you from using workbench_moderation is the fact that you currently have to have a published state.

mxh’s picture

Thanks for your answers srjosh and Manuel, I ended up with a custom solution, since Workbench has some other predefined features which just dont "suit" to more complicated situations (Workbench is still a great all-in-one solution for simple editorial workflows though).

I leave this issue open, if some other needs a similar change like described above. Feel free to close it.