State has customized the class AddressDataIntakeApplicationListener non-compliantly to support their business

Details about the issue

Detailed description of the issue

State of missouri have customized the class AddressDataIntakeApplicationListener non-compliantly to support their business needs in the following methods preMapDataToCuram(), createTempAddressLinkEntity(), createResidentialAddressEntity()


Detailed steps to reproduce the issue in an out-of-the-box environment

N/A


If the issue cannot be replicated in an out-of-box environment, describe the detailed steps that are necessary to help emulate the customized environment in order to highlight the underlying out-of-the-box issue

N/A

Details of any on-site investigations that have been done

N/A

Description of any workarounds / potential solutions that are being used

MO have previously worked around this issue by non-compliantly customizing the OOTB listener class - AddressDataIntakeApplicationListener and customized the following methods

1. preMapDataToCuram() - MO customized this to ensure that this method is executed for HPE and HCR applications.

isTaxReturnCurrentIncome and isESIncomecurrent attributes were not defined for HPE applications. As this method is executed for HPE and HCR, MO added a filter to set these attributes only for HCR in application entity.

For Each person entity, Records are inserted into address table by fetching the data from mailingAddress. MO added the same logic for TempAddressLinkMailing, tempAddressLinksTransient and empAddressLinksFFMHome entities along with mailingAddress.

2. createTempAddressLinkEntity() - while creating the child entity TempAddressLink, MO added setTypedAttribute() method for it's custom attribute - 'addressVerificationStatus' in this entity.

MO creates a custom child entity 'TempAddressLinkMailing' along with the OOTB entity - 'TempAddressLink'.

3. getAddressData()-

MO customized the logic to store stree1 and street2 values as addressLine1 and addressLine2 in AddressFieldDetails struct instead of using addressLine2 and addressLine3 [OOTB]

MO used a default string if the street1 value is empty
Mo used mocounty which is another attribute for county and added a custom logic for this attribute.



configreport.zip file created by running the Cúram configreport Ant target.

N/A

================================================================================

Details about the Impact of the Issue

Describe the business impact of the issue on the end user

the State of Missouri's requirements cannot be compliantly implemented resulting in a maintenance burden due to non-compliant implementation.


When was the issue first identified?

N/A

How often does the issue occur?

Anytime Applications are submitted on intake process

Does the issue affect all users?

Yes

================================================================================

Environment

Exact version of IBM Curam

v7.0.7

Type of environment

OOTB

Does this appear to be a regression?

No

Has the issue been replicated in another environment?

N/A

Details of any customizations that have been made in the affected area

N/A