[
http://www.jahia.net/jira/browse/SENSEI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35374#action_35374
]
Thomas Draier commented on SENSEI-51:
-------------------------------------
We don't map automatically any workflow role based on acls, so that's normal we
don't see anything in the workflow subengine by default. There is no default
initialization of roles. ACLs and workflow are separate roles. The only
available role in 2 steps workflow is the publish role which is not assigned by
default.
The fact that the admin can validate anything cannot be changed and is not
linked to any workflow role - it's just because it's an admin of the page.
About adding users who can't see the page - we might want to limit to the users
who have write access to the page.
About inheritance, workflow roles behaves the same way as acl - inherited by
default, and can be broken at any level, for changing workflow type or just
roles. However the workflow subengine is not very clear - when inherited, we
don't see the inherited roles like in the acl engine.
> N Step UI: default user or group mapping should be displayed
> ------------------------------------------------------------
>
> Key: SENSEI-51
> URL: http://www.jahia.net/jira/browse/SENSEI-51
> Project: Jahia Workflows
> Issue Type: Bug
> Affects Versions: Workflow 6.0
> Environment: 22692
> Reporter: Stephane Croisier
> Assignee: Thomas Draier
> Priority: Major
> Fix For: Workflow 6.0
>
>
> The 2 step workflow is replacing the old std worklfow. We are also
> automatically mapping ACL on the different steps. However when you open your
> workflow sub-engine, ACL mapped by default in the 2 steps rules are not
> displayed. So you do not know which users or groups currently are able to
> perform which actions.
> Moreover the behaviour of adding a new user or group is not clear: does it
> mean that the default values will be broken and that only the newly added
> users in the 2 steps workflow rule will be able to validate a page? or is it
> an "ADD" command (but which would be the sense to add a user which has no
> permissions on the current page).
> So I think we should initialize the default value with the ACL values but
> that such values should be then displayed in the workflow rule engines so
> that they could be edited (= most of the time restricted to certain users
> only).
> Finally there is still the behaviour of the workflow inheritance. What if I
> restrict some rules on the Page A and then I break the workflow on page
> Sub-A? Does it inherit back from the parent workflow rules or from the ACL of
> the current page? most of the time I think a user would like to have the same
> workflow behaviour than the parent workflow object with the same rules.
> Possible?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
