Investigate - NAMES /NRA Alter existing function issue /Nov 1 /NRA /NR 6345564 - initial and NR 5990064 - staff resubmit

[ozamani9gh]

Related to OPS Issue:
https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/issues/gh/bcgov-registries/ops-support/3258

NRA/NAMEX issue

Client submitted NR 6345564 via the new NRA pathway for ULC to BC however request type populated as "ERROR!!" in NAMEX
Staff subsequently replaced it as a workaround with NR 5990064 and received the same result.
Staff workaround was to replace NR via the "New BC Incorporation" request type pathway with success under NR 7441883
It seems there is an issue with the way the new pathway for "Alteration" types in NRA is translating in NAMEX

Private Zenhub Image

Private Zenhub Image

Private Zenhub Image

Severin can provide help with investigation:

Some help for whoever investigates this:
I created a NR for altering a ULC to a BC in Namerequest UI - Dev. Here is the initial NR data. I am not sure if anything is weird in here.

Private Zenhub Image

The bug reproduces (as seen in Namex - Dev):

Private Zenhub Image

[eve-git]

#16310 added two alteration request types but not in name-examination.

[eve-git]

Ready to test in the TEST environment. Here are the improvements:

1. The error in the screenshot above is no longer there.
2. In 'name-examination->Edit Request,' the corp number is now editable.
3. No errors occur when retrieving the NR during the alteration in BCROS

[oanyahuru]

Private Zenhub Image
The issues raised did not show up in testing.