[
https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282564#comment-14282564
]
Gil Portenseigne commented on OFBIZ-5959:
-----------------------------------------
Quick answer to illustrate my way to deal with the given scenarii, then i'll
read the doc you link about the UDM....
The fact that makes me have this opinion is that, for such kind of screens, i
use to customize the screen to show only the roles that should be usable in the
customer process, not the global list. Then the customized screen let us choose
any party without ensuring that he possess the good role, and behind that, the
creation of *Entity*Role record, will create the PartyRole if needed.
The way you describe the first scenario imply that we have to manage each party
role independantly before associating the party to the Agreement (PartyRel or
so). I do not find that convenient, and i'd appreciate to have more testimony
about this matter.
For the second scenario, i'm not sure that automation is the good way to do.
It's like adding the option to terminate all EntityRole records of the party
and given role. It might be useful in specific cases. But i think that to know
if the role is active or not, it's better to check *Entity*Role, than
PartyRole...
> Add lifespan fields to PartyRole
> --------------------------------
>
> Key: OFBIZ-5959
> URL: https://issues.apache.org/jira/browse/OFBIZ-5959
> Project: OFBiz
> Issue Type: Improvement
> Components: party
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Labels: role, roles
>
> Currently the assignments of roles to parties are boolean (there or not
> there).
> However, these role assignments also have a lifespan. This can be achieved by
> adding fromDate and thruDate fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
