As you can see we have a column with an icon and text next to it.
From what I can tell the icon represents the status and the text represents the stage as shown here when using a different workflow
I'm all ok up to this point.
The problem comes with the change select. For both workflows it looks like this
So why does it say "Published [Published]"
What is the meaning/significance of this or is it a bug? I was expecting something like this when you have a custom workflow
Labels |
Added:
?
|
Why the transition and not the stage?
/me confused
Sorry typo, in brackets is stage after transition, not state after transition.
So it is "Transition [Stage after that transition]"
Why it was made like this you have to ask the inventor ... hope he or she reads and comments.
@bembelimen Could you confirm my understanding or corect me if I'm wrong, and explain why it was made like that? I think the reason was because for the "old" system we also used actions, i.e. verbs, and not status, i.e. not adjectives, for the pull down, is that right?
It's nothing to do with adjectives or verbs. Should it be stage or transition?
As I said: "Transition [Stage after that transition]"
Richard is right, it's "Transition [new condition]". The reason is very easy: you execute transitions (in theory multiple transitions can lead to a stage, so it makes no sense to put in the stage here) and not the stage.
Perhaps I'm wrong here, but the idea was from you Brian? So the user understand the new condition of the item.
You mean I am right not Richard ;)
It still confuses me that you select something in a list and the selected value is not what is displayed
Ups yes, sorry, I shouldn't write in the tram...ofc, you're right.
If I remember correctly (and I still fully agree to it), this combination helps people to see, if the article after execution is visible/disabled on the page, to prevent surprises. (Because now you don't see any condition based on the stage name)
The issue is that the value selected is not the value displayed
Let's say I was right on the left side - that there is a transition - and then you were right with the right side - that there is a condition and not a state - but this condition belongs to the state after ttransition, that's why bembelimen said "new condition", so I was not too much wrong with the right hand side.
I think the problem behind it is that you can define states and transitions with names not being as similar as e.g. "Publish [published]". So it might make sense to show both, so you know what action you do /the transition) and what is the result at the end (the new condition).
You could also have a "neutral" name like: "proofread" but it does not indicate if it's visible on the page (published) or not (unpublished). Probably the confusion comes from reusing the old names?
Actually it becomes more confusing when using your own names (thats how I spotted it)
For me the main issue is the difference between the selected value and the displayed value. Pretty certain that this fails accessibility rules
I guess it comes down to - do I need to know what the name of the transition is?
I need to know the stage that the article is in and the condition that means. I don't need to know the name given to the transition - do i?
Yes you need, because different transitions could go to a stage and you could have a plugin which does something on a transition but does nothing on another one.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-05-27 07:56:18 |
Closed_By | ⇒ | brianteeman |
Is doesn't say "Published [Published]", it says "Publish [Published]".
First one is the transition, to publish, the second one in brackets is the state after the transition, i.e. it will be published.