[
http://jira.nuxeo.org/browse/NXP-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50460#action_50460
]
Anahide Tchertchian commented on NXP-3273:
------------------------------------------
we could have a method JbpmService#getTaskInstances(Collection<String> actors,
JbpmListFilter filter) and move out the actor ids retrieval (based on current
user name or groups) or permissions retrieval (as you described) out of the
service.
it would fit the need right?
plus the current logic is dupplicated in getCurrentTaskInstances and
getTaksInstances.
we could also use the same trick for getCurrentProcessInstance, and move out of
it the "business logic" tied to the process initiator.
> add the possibility to attribute task on permission (or other properties)
> -------------------------------------------------------------------------
>
> Key: NXP-3273
> URL: http://jira.nuxeo.org/browse/NXP-3273
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Reporter: Alexandre Russel
> Assignee: Alexandre Russel
> Attachments: jbpm-service-fragment.java
>
>
> In the JbpmService, when getting a user's tasks, the considered tasks
> are those with actor id or pooled actor id like "user:theUser" or
> "group:oneOfTheUserGroup".
> Would it make sense to have a mechanism enabling permission assignation
> for tasks ? Actor id / pooled actor id could be something like
> "permission:aSpecificPermissionRequiredOnDoc".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
