Granted:

  • Peter should not be able to initiate publication when workflow is installed for an app (same as 4.5, was the ground for SUPPORT-3625)

Problem:

  • Eric can edit and publish on standard content apps, while Peter cannot do anything really.
    • Ideally, Eric should edit only, and Peter should publish only (kind of manual workflow).
  • This would lead to inconsistencies between apps with workflow installed and standard content apps, e.g.:
    • As Eric: "Why is publish enabled in Pages (via workflow), but not in Assets (plain activation)?"
    • Vice-versa as Peter: "Why is publish disabled in Pages, but enabled in Assets?"
    • As whoever: "What is the meaning of the publish action?" (will it go straight to public or not)

This issue has to be solved on UX level first, before we implement some silly workaround.
We could maybe communicate the different semantics better between those two flavors of publication, through appropriate phrasing of the actions.

Side note:
The difference is not so much about CE vs. EE, but rather whether or not workflow is installed for that app.

Change By: Mikaël Geljic (28/Oct/14 12:11 PM)
Summary: Peter cannot Eric can edit &  publish  anymore in CE and EE  while Peter is powerless on apps without workflow
Labels: ux
Environment: CE
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to