AUTH-WEB - NR's for COLIN actions should not advise to add the business in MBR

[Mihai-QuickSilverDev]

• Name Change NR, for a BC Ltd. company is instructing the user to add the business to the MBR, in order to proceed with the name change.
• Also Alteration from BC Ltd. to ULC.
• Because the BC Ltd. is not in BCROS, the affiliation would fail, and most likely we would end-up with a call/ticket.

How to replicate the issue:

• Login to BCROS TEST as BCREG0020
• Locate this NR
  Private Zenhub Image
• Click on Change Name Now
• Observe the message displayed on the screen:
  Private Zenhub Image
  To Do List:
• When clicking on Change Name Now launch a redirect to COLIN instead.
• [ ]
  There are more NR types in this situation, work can start now, and would update this ticket for Thursday.

[Mihai-QuickSilverDev]

Message from Dave to Travis:
Hi Travis,
I just wanted to give you a heads up, we found a bug. I believe it’s in Auth Web when a user should be redirected to COLIN as part of the Way of Navigating. Mihai is creating a ticket right now and I’ve asked him to assign the ticket to you.
If you don’t think it’s there or rightly be assigned to my team, just let me know.
Thanks,
Dave

[Mihai-QuickSilverDev]

@davemck513 @severinbeauvais @seeker25

[severinbeauvais]

A quick solution would be to use the "IA" feature flag to determine whether to open the business locally or redirect to COLIN

(The IA FF determines whether to handle IAs locally or redirect to COLIN, depending on whether the entity type is supported. This should be OK initially because we don't handle IAs or name changes or alterations for the unsupported entity types. Ultimately, name change and alteration should have their own FFs.)

Ultimately, we might want two new FFs, so that we can deploy new IAs separately from new name changes or alterations.

[jdyck-fw]

@seeker25 @PCC199 - I believe this is intended to be in Relationships sprint.

[seeker25]

I've put in a check to look if it's a modernized entity (looking at the IA feature flag). If it isn't, it redirects to COLIN. If it is, the error above still persists.

DEV has this feature flag wide open, TEST and PROD are way more limited (should see the redirect to COLIN).

[seeker25]

Should be on test in 15m

[severinbeauvais]

Ultimately, we might want two new FFs, so that we can deploy new IAs separately from new name changes or alterations.