transition labels
moshe weitzman - July 12, 2006 - 19:10
| Project: | Workflow |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | moshe weitzman |
| Status: | active |
Jump to:
Description
i think it will be useful for admin to optionally provide labels for each transition. this could be done on a new admin page. the labels would be shown as links on a node and they would usually be verbs like 'reject' which describes the review => rework transition. these same links could show up in Views table listings. the destination of those links would be the workflow tab with the right destination state selected in the radio button. then all that is needed is to add a workflow comment and click submit.
#1
+1 for transition labels. This is a must for workflow-in-core-in-5.0.
#2
jvd or other - any comment beyond what i mentioned about where these labels should be used?
#3
Most workflow systems use the transition labels as labels for buttons that execute the transition.
In thinking about a very basic default workflow and UI for Drupal, I like the idea of comments not enabled by default, and clicking on the button executes the transition. That's about as simple as it gets.
For advanced workflows we could enable commenting and the workflow tab.
#4
thanks ... consider the 'published' checkbox on the node form in drupal core. if we turn that into a button, then how does that interact with the saving of the whole node form? i'm having some trouble visualizing how that will work. in some ways, the current mechanisms (checkbox in core, radio buttons for states in workflow) fit in better than buttons.
#5
i've already implemented this if anyone would like the code
#6
Attaching a patch here would be nifty.
#7
@MrTaco - plase provide patch if possible
#8
subscribing
#9
I got MrTaco's code and made a patch, but didn't see this issue and put it at #227038: Add named transition states. Then I apparently made an even bigger mess by making http://drupal.org/project/workflow_named_transitions. There are some bugs in it and I am working through them, but is this something I should be working back into core workflow or is it better off an a separate module?
#10
I'd like to see it in core workflow, even if it's not required by default (requiring named transitions makes configuration tedious for basic workflows).
#11
If could have a 'next' or 'default' transition that would go to the next node if it hadn't been created, but could be overridden if that transition had been explicitly defined. The caveat being that I would want to be able to force the 'next' transition to return to the same state so that I could put my Error states after the completion states and not worry about a default transition moving into the error state.