Additional UI widget or indicators for multiple button scenarios about silverstripe-advancedworkflow HOT 4 OPEN

https://skitch.com/clarkepaul/849t1/actions-panel-and-status

Note the above changes are occurring in 3.1 and we should work with these in mind

from silverstripe-advancedworkflow.

I'd suggest the following rough workflow for sorting this out:

• Design: Come up with a layout mimicing Paul's design.
• Dev: Abstract that into a description of actions like "these are the primary actions, these are the secondary actions" that will fit into the 3.1 actions API.
• Dev: Implement, and come up with some graceful degradation for 3.0.

I wouldn't too much about polishing the solution in 3.0 UI to solve the problem if it's solved nicely in 3.1. The module needs to function well in 3.0 but the UI doesn't need to be optimal.

from silverstripe-advancedworkflow.

See https://groups.google.com/forum/?fromgroups=#!topic/silverstripe-dev/GdM4_4nxM8A for some context.

from silverstripe-advancedworkflow.

A related issue:

The initial action on a WorkflowInstance shows a button in the CMS content-editing UI next-to "Save Draft". This gets really confusing when - as a author - you accidentally select the workflow action button, and not "Save Draft" and wonder why the heck content isn't showing where it's supposed-to - a newbie issue if you will, but a UI issue nonetheless.

Depending on how the new API is implemented, I would suggest disabling the workflow action button if no version of this content-object yet exists ("Save Draft" has not yet been selected by any author on this content-object). so the only relevant button is "Save Draft" and when selected, the action button is automatically enabled.

from silverstripe-advancedworkflow.