[
https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282450#comment-14282450 ]
Gil Portenseigne commented on OFBIZ-5959:
-----------------------------------------
Hi Pierre, here is my point of vue and I tend to agree with Scott.
Imho, a role need a context to be. I try to get your point but i didn't find a good example of a global role, i.e. a role that won't be link to another Entity which give the context. Sure there are examples, but the context is implicit, and in our datamodel, my opinion is that implicit should be avoided.
I did met that issue with a customer, who tried to understand the use of partyRole data (without context). I had to rethink over it to be able to answer him.
Indeed, i used to have some partyRole positionned directly on the party, to make it appear in specific lookup, but I think that is a bad conception...
I like to see PartyRole as the entity of the roles that a party have or used to have. But to know and filter active roles, i must go on XXXXRole entities.
> 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)
Locked
