Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

Hello, I have created a ticket here . -- Best Regards, Suraj Khurana TECHNICAL CONSULTANT mobile: +91 9669750002 email: suraj.khur...@hotwax.co www.hotwax.co On Thu, Apr 11, 2019 at 6:14 PM Suraj Khurana wrote: > Thanks, everyone for

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

Thanks, everyone for your inputs. Nicolas, Yes, we can manage things with PartyClassification to maintain time span of it as well, it brings some complexities to handle now, as a party can be in multiple classifications on the same time, etc etc, maintaining PartyRelationship is a high-level

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1 Thanks & Regards, Devanshu Vyas. On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana wrote: > Hello, > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1. Best Regards, -- *Rishi Solanki* | Sr Manager, Enterprise Software Development HotWax Systems Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore, M.P 452010 Linkedin: *Rishi Solanki*

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1 Jacques Le 09/04/2019 à 10:59, Suraj Khurana a écrit : +1. Technically, as per Pierre, we should also mark this field as encrypted in the entity definition. -- Best Regards, Suraj Khurana TECHNICAL CONSULTANT mobile: +91 9669750002 email: suraj.khur...@hotwax.co *www.hotwax.co

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1. Technically, as per Pierre, we should also mark this field as encrypted in the entity definition. -- Best Regards, Suraj Khurana TECHNICAL CONSULTANT mobile: +91 9669750002 email: suraj.khur...@hotwax.co *www.hotwax.co * On Tue, Apr 9, 2019 at 2:08 PM Pierre

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

Although I am inclined to agree with having the options come from appropriate records/values in the Enumeration entity, I must caution about how the final solution will be implemented in our code base. We all know that this falls in the category of sensitive data which has come under a tighter

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1 Best Regards, Aditya Sharma, http://ofbiz.apache.org On Tue, Apr 9, 2019 at 1:09 PM Swapnil M Mane wrote: > +1 > > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana > wrote: > > > Hello, > > > > Currently, *maritalStatus* is

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana wrote: > Hello, > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > >

Re: ***UNCHECKED*** Marital Status not managed properly in Person entity

+1 Jacques Le 09/04/2019 à 09:20, Suraj Khurana a écrit : Hello, Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* entity. I think we can enhance it and make it derived from *Enumeration* pattern. *Classification of legal marital status* - 1 - Married (and not

***UNCHECKED*** Marital Status not managed properly in Person entity

Hello, Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* entity. I think we can enhance it and make it derived from *Enumeration* pattern. *Classification of legal marital status* - 1 - Married (and not separated) ... - 2 - Widowed (including living common law) ...