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 scrutiny due to GDPR and security breaches.
Such privacy sensitive element should be implemented in tighter permissions applied than we generally apply to screens/forms/fields etc. Best regards, Pierre Smits *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) since 2008* Apache Steve <https://steve.apache.org>, committer On Tue, Apr 9, 2019 at 10:19 AM Aditya Sharma <adityasha...@apache.org> wrote: > +1 > > Best Regards, > Aditya Sharma, > http://ofbiz.apache.org > > > On Tue, Apr 9, 2019 at 1:09 PM Swapnil M Mane <swapnilmm...@apache.org> > wrote: > > > +1 > > > > > > - Best Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana <suraj.khur...@hotwax.co> > > 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 marital status* > > > > > > - 1 - Married (and not separated) ... > > > - 2 - Widowed (including living common law) ... > > > - 3 - Separated (and not Divorced) ... > > > - 4 - Divorced (including living common law) ... > > > - 5 - Single (including living common law) > > > > > > Please share your thoughts. > > > > > > -- > > > Best regards, > > > Suraj Khurana > > > TECHNICAL CONSULTANT > > > mobile: +91 9669750002 > > > email: suraj.khur...@hotwax.co > > > *www.hotwax.co <http://www.hotwax.co/>* > > > > > >
