You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/10/09 11:47:00 UTC

[jira] [Commented] (OFBIZ-13329) Manage marital status type history for person

    [ https://issues.apache.org/jira/browse/OFBIZ-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125504#comment-18125504 ] 

ASF subversion and git services commented on OFBIZ-13329:
---------------------------------------------------------

Commit e4599c139ee7ca44822baeb7ca18b382acbc64fe in ofbiz-plugins's branch refs/heads/trunk from Devanshu Vyas
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=e4599c139 ]

Fixed: Administrator profile on ecommerce shows FTL error (OFBIZ-13475) (#358)

### Description
When logged in using the admin user on the Ecommerce homepage, the
viewprofile screen throws an FTL error because of the deprecated
`maritalStatusEnumId` field on the `Person` entity (which was deprecated
in OFBIZ-13329 and replaced with `maritalStatusTypeId`).

### Changes
- Updated `ViewProfile.ftl` to use `person.maritalStatusTypeId` and
query entity `MaritalStatusType`.
- Updated `EditPerson.ftl` to query `MaritalStatusType` and name the
select element `maritalStatusTypeId`.
- Updated `CustomerEvents.xml` map processor to process
`maritalStatusTypeId`.

> Manage marital status type history for person
> ---------------------------------------------
>
>                 Key: OFBIZ-13329
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13329
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>            Reporter: Nicolas Malin
>            Assignee: Nicolas Malin
>            Priority: Minor
>              Labels: history, marital, person
>         Attachments: OFBIZ-13329.patch
>
>
> Currently, on the framework we can add a marital status to a person through enumeration on entity Person. 
> But we can't manage the history of change. After scan the data model book, we proposed to improve party model entity with two new entities :
>  * MaritalStatus : to stock the history of marital status change
>  * MaritalStatusType : like Len Silverton suggest on his book to isolate these types.
> We move the current field *maritalStatusEnumId* to deprecated and introduce a migration service to move field *maritalStatusEnumId* to *maritalStatusTypeId*
>  
> Thanks to Charles Steltzlen for this improvement



--
This message was sent by Atlassian Jira
(v8.20.10#820010)