FINERACT-1430: Added social status and restricted high profile client access

[Satish11012007]

Summary

This PR introduces access restriction for high profile clients using a new social status field.

Changes included:

• Added Liquibase changelog to create m_client.social_status_cv_id
• Added foreign key constraint from m_client.social_status_cv_id to m_code_value.id
• Inserted new permission entry CAN_VIEW_HIGH_PROFILE_CLIENT into m_permission
• Included the new FINERACT-1430 changelog in db.changelog-master.xml
• Added socialStatus field in Client entity mapped to social_status_cv_id
• Enforced permission validation when reading a client with social status set
• Added PermissionConstants.CAN_VIEW_HIGH_PROFILE_CLIENT constant

---

Behavior

• If social_status_cv_id is null, the client can be viewed normally.
• If social_status_cv_id is not null, the system validates the required permission:

context.authenticatedUser()
       .validateHasPermissionTo(
           PermissionConstants.CAN_VIEW_HIGH_PROFILE_CLIENT
       );

[IOhacker]

In financial terms, there is not "high/low social status" this seems to be a segregation feature.

I don't approve this change

[Aman-Mittal]

In financial terms, there is not "high/low social status" this seems to be a segregation feature.

I don't approve this change

In financial terms, there is not "high/low social status" this seems to be a segregation feature.

I don't approve this change

Hi Victor, seems like this ticket is related to compliance usecase, There is no high and low social status but there can be High Net Worth clients (High Net Worth Indiviuals) or PEP (Politically Exposed Person). Maybe need to ask more to the reporter of this ticket for his usecase first.

[IOhacker]

@Aman-Mittal in finance we use a different wording and different approach either for KYC, AML/FT but never we use "social status" wording because at least in the uses cases that I have been working either on commercial or development banks use that for refering to a person and it is consider discrimination. That is the reason that I don't approve the change submitted in the PR.

[IOhacker]

I have added my comment in Jira too.

[Aman-Mittal]

@Aman-Mittal in finance we use a different wording and different approach either for KYC, AML/FT but never we use "social status" wording because at least in the uses cases that I have been working either on commercial or development banks use that for refering to a person and it is consider discrimination. That is the reason that I don't approve the change submitted in the PR.

Thanks for replying.