You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2014/10/20 12:45:33 UTC

[jira] [Updated] (OFBIZ-5827) Have party selection in screens based on relation(s) in stead of role

     [ https://issues.apache.org/jira/browse/OFBIZ-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Smits updated OFBIZ-5827:
--------------------------------
    Summary: Have party selection in screens based on relation(s) in stead of role  (was: Have party selection in screens based on relation in stead of role)

> Have party selection in screens based on relation(s) in stead of role
> ---------------------------------------------------------------------
>
>                 Key: OFBIZ-5827
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5827
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Pierre Smits
>
> This is the umbrella task to have party selection based on relations in stead of role types.
> Currenly party selection is (in most situations) based on role. Meaning anybody in e.g. role picker can be assigned to a picking activitiy without consideration of the internal organisation. Of course this works very well for implementations where there only one internal organisations (and only 1 facility). But when the implementation has multiple internal organisations (multiple departments) with persons assigned to a specific organisation and/or department this is not enough. 
> In general, the manager of one organisation isn't allowed to manage the actions of persons in another organisation. OFBiz should reflect this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)