Show transitions instead of actions on content-objects about silverstripe-advancedworkflow HOT 6 OPEN

Are you referring to the button that was previously titled 'Update workflow'?

from silverstripe-advancedworkflow.

Not sure where the "Update Workflow" button was. I am referring to when you go to the PagesAdmin, navigate to a page with a related workflow and see a button at the bottom who's label is whatever the current-action's name is.

Unless, I misunderstand the correct context and use-case for these action buttons in this location, there is no way to perform any of the transitions prior to executing the action - just straight to the action.

Basically, I see a scenario where a content-editor would like to see the page's changes, before rejecting/accepting those changes (in a 2 step workflow for example) but as things stand, all they can do is skip the transitions and go straight into actioning that action, if that makes sense?

from silverstripe-advancedworkflow.

Yep, not sure who it was but someone in NZ changed it from being a generic "Update workflow" to using the current action as the title of that button, which is where the subsequent request for having a separate label field came from.

The real solution (that was horrible to attempt to implement in SS2, thus the selection of transition from a dropdown) is for the transitions to be the labels of the buttons, and to have as many buttons as transitions. The problem then is to figure out where to place these buttons...

To sum all that up, I think the problem is that "Update workflow" was deemed too unspecific, and the workaround for that was to use the current action title as the label instead, but that carries its own issues.

from silverstripe-advancedworkflow.

Can we please use 'authors' and 'publishers' as the terminology here?
That's an established convention. We typically use 'editor' to refer to
TinyMCE, and you're muddying that prior separation...

E.g. Publishers are those who can "save and publish", who can change the
"Published Site", etc.

On 20 November 2012 12:38, Russell Michell [email protected] wrote:

Selecting a WorkflowInstance in the CMS, allows editors (or "approvers")
to run the next transition in the current action. However when viewing the
Target object in the CMS (e.g. a "Page"), the action itself is shown as a
button "Editor Approve" (for example).

Should this UI be re-defined to show the available transitions as
opposed to jumping directly to the next action these transitions lead-to?

This is likely low-priority - see issue #51#51

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63.

Sigurd Magnusson
Business Relationship Manager
SilverStripe

DDI: +64 4 978 7332
Mobile: (NZ): +64 21 42 12 08
Skype: sigurdmagnusson
twitter.com/SigurdMagnusson
www.silverstripe.com

from silverstripe-advancedworkflow.

Of course. I had quickly gotten so used to the button-label change, that it became the source of another issue - thanks for taking the time to point that one out.

Agree re: transitions as buttons - hence the issue-title - but given an imminent API core change (1st comment on #50 & #51) probably shouldn't be actioned just yet.

from silverstripe-advancedworkflow.

Yup, that should hopefully give a graceful solution for this

from silverstripe-advancedworkflow.