Re: All roleType entities should maintain lifespan

Nothing was added for almost 2 weeks. So I think we reached a lazy consensus, let me summarise it here, as I see it: 1. We don't want to add lifespan (add from/thruDate fields) to roleType entities; so OFBIZ-5959, its subtasks and related tasks should be closed as won't fix 2. We want (conti

Re: All roleType entities should maintain lifespan

Le 16/11/2017 à 07:05, Deepak Dixit a écrit : PartyRole is a technical entity as functional entity (it's border line :) ). Prefer to manage this role lifespan information with PartyRelationship and hidden PartyRole value to end user. You are right Nicolas, These kind of information should be ma

Re: All roleType entities should maintain lifespan

>>>PartyRole is a technical entity as functional entity (it's border line :) ). Prefer to manage this role lifespan information with PartyRelationship and hidden PartyRole value to end user. You are right Nicolas, These kind of information should be managed in PartyRelationship entity, In case of

Re: All roleType entities should maintain lifespan

Hi Suraj, Though it's obvious when you look at the figure 4 of http://www.universaldatamodels.com/Portals/9/udm_Publication_Articles_11_05_Models_Patterns.pdf I missed to say that I agree about removing the FK from EntityNameRole entities to PartyRole. Jacques Le 15/11/2017 à 17:38, Jacques

Re: All roleType entities should maintain lifespan

Hi Suraj, All, It makes sense to have roles of parties limited in time But unfortunately adding from/thru dates to PartyRole would entail tremendous changes as Nicolas and Adrian and Gil in OFBIZ-5959 mentioned. We had this discussion so many times (with some variants and confusion: http://ofb

Re: All roleType entities should maintain lifespan

Hi Nicolas, Could you elaborate on the "hidden PartyRole value"? How is it hidden? What does that mean exactly? Is it only about a hidden field in a form for pre-selection? Thank Jacques Le 29/09/2017 à 19:59, Nicolas Malin a écrit : Add lifespan to PartyRole seems to me just to complex perh

Re: All roleType entities should maintain lifespan

Hi Scott, Thanks for your response. In figure-4 he **re , it is specified that we do not need to manag

Re: All roleType entities should maintain lifespan

Add lifespan to PartyRole seems to me just to complex perhaps impossible. If you want indicate (as example) that a party is a customer from / to with a lifespan on PartyRole they missing the information customer from who ? PartyRole is a technical entity as functional entity (it's border line

Re: All roleType entities should maintain lifespan

Hi Suraj, I still haven't seen an example of a useful use case for adding from/thruDate fields to the PartyRole table. Did you have anything in mind that it might help with? I'd honestly prefer to remove it rather than expand it. Regards Scott On 29 September 2017 at 20:41, Suraj Khurana < sur

All roleType entities should maintain lifespan

Hello, There has been already a discussion under OFBIZ-5959 regarding this. I would like to bring this point again into attention and would like to suggest that we should introduce lifespan to all such entities. Also, PartyRole FK constraint shoul