MHR API fix saving tenants in common group sequence number to DB2.

[doug-lovett]

See https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/issues/gh/bcgov-registries/ops-support/3154 for background.

A new MH registration created in MHR is not displaying the owner group information correctly in the legacy application when the owners are tenants in common. By comparing an existing legacy MH registration with tenants in common owners and a one created with the MHR API, the MHR API is not setting the owngroup table grpseqno value correctly with a tenants in common group structure. The grpseqno appears to represent the active group sequence number starting with one.

Developer Notes:
In the DEV environment, test that MH registrations and transfers with a tenants in common group work as expected in the UI.
In TEST:

1. Create a MH registration in the legacy application with a tenants in common group structure and view it in the legacy application.
2. Create a MH registration in the modernized UI with the same tenants in common group structure and view it in the legacy application. The owner group information should match including the fractional interest.

[chdivyareddy]

Verified in DEV using MHR 107825.

Private Zenhub Image

[chdivyareddy]

Hey @doug-lovett , please take a look at the following examples from TEST.

• Create a MH registration in the modernized UI with the same tenants in common group structure and view it in the legacy application. The owner group information should match including the fractional interest.

Current behavior: Tenancy type for the Groups 1 & 3 displays 'Tenants in common' instead of 'N/A' in the legacy application.

MHR 107264 in TEST created in the new application

Home owners view before filing registration:
Private Zenhub Image

MHR info screen:
Private Zenhub Image

Search Output:
Private Zenhub Image

Legacy application view:
Private Zenhub Image

• When an MH registration is created in the legacy app and searched through the modernized UI to view the home owners table structure, then the ownership interest is not displayed:

MHR 107263 created in the legacy application

Private Zenhub Image

modernized application view (search output):

Private Zenhub Image

MHR info screen:

Private Zenhub Image

[doug-lovett]

@chdivyareddy thanks Divya, looks good to me. In the ops ticket from prod the screenshot only shows the first tenants in common group. @mstanton1 can you please confirm?

[doug-lovett]

@chdivyareddy and to confirm, "N/A" for the tenancy type is modernized only.

[mstanton1]

@chdivyareddy this is as I would expect it to appear. I understood that "N/A" is for modernized only. When this moves to PROD I can ask for a secondary verification of the initial issue reported in PROD by staff.

[chdivyareddy]

@doug-lovett @mstanton1 Thank you for confirming.

For the second scenario mentioned, when an MHR 107263 is created in the legacy application, the ownership interest is not displayed in the new application search output. Is that as expected or does it not include as part of this ticket?

[doug-lovett]

@chdivyareddy looking at the 107263 now. I just searched on 004192 in DEV which is a legacy TC home and it is displaying the fractional ownership correctly:

2023-10-05_BCMHR_Search_Result_004192_14283.pdf

[doug-lovett]

@chdivyareddy 107263 is a search report issue. Your test registration has no interest text, almost all legacy registrations have a variation of "UNDIVIDED". The report is not displaying the interest and fractional ownership because there is no interest value. The report fix would be in another ticket.

[chdivyareddy]

@doug-lovett Perfect! Thank you for taking a look, will move this ticket along for now.

Created #18097 for the report issue.