eve-git

Test in DEV: input the corp_num='C0181655'. I got the following error in namex-api log: ``` 2024-10-11 15:33:37,939 - namex - ERROR in api_resource:api_resource.py:14 - handle_exception: Error: MapRequestAttributesError("Error setting request attributes.\r\n\r\n'NoneType'...

The following corp_types are continue in corp types in legacy system: Here are the request type cd corresponding to continue-in in legacy system: based on the info above, I added...

I added the following entries to namex based on the request type in legacy namex: ``` REQUEST_TYPE ENTIRY_TYPE_CD REQUEST_ACTION CT C CHG CCCT CCC CHG ULCT CUL CHG BECT CBEN...

@severinbeauvais I am not clear what to update for Conversion and raw_nr_to_aciton_mapping. Please advise. Thanks

I think raw_nr_to_action_mapping and the alteration mappings are all good.

@severinbeauvais Request Action mapping in namerequest has MVE for continue-in. So, is it the type in request type mapping in api for continue in? https://github.com/bcgov/namerequest/blob/main/app/src/list-data/request-action-mapping.ts#L62

@severinbeauvais Let's just focus Name Change on this ticket. Thanks

I've added mappings for continue-in and restoration REH to the code. I did not include others because I couldn't find corresponding continue-in mappings in the RequestActionMappingI within namerequest.

The namex-api will be deployed alongside the NRO decommission. We plan to begin testing the namex-api starting tomorrow.

I'm not sure; Omid handles the releases and deployments