[
https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818753#comment-16818753
]
Paul Foxworthy commented on OFBIZ-10921:
----------------------------------------
Thanks Pierre.
I agree implementers may well change this to suit their own needs. Changing
marital status to an enum will facilitate customisation, so I'd be happy for
Suraj to proceed with that. And I'm happy with attached patches for different
use cases.
After that, there should probably be some default demonstration data as there
is for many other entities. Some implementers will not care much about this and
won't change from the defaults. So I'd prefer that our demonstration data
should be minimal and lowest common denominator. When a new OFBiz developer
uses the standard demo data, we should keep it simple and minimise the chance
of embarrassment, distraction and objections from potential clients.
> Marital Status not managed properly in Person entity
> ----------------------------------------------------
>
> Key: OFBIZ-10921
> URL: https://issues.apache.org/jira/browse/OFBIZ-10921
> Project: OFBiz
> Issue Type: Improvement
> Components: party
> Affects Versions: Trunk
> Reporter: Suraj Khurana
> Assignee: Suraj Khurana
> Priority: Major
>
> 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 refer discussion over ML:
> [https://markmail.org/message/5b33qm3osy76if24]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
