Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filings UI: NR error after filing an application #18736

Closed
severinbeauvais opened this issue Nov 24, 2023 · 5 comments
Closed

Filings UI: NR error after filing an application #18736

severinbeauvais opened this issue Nov 24, 2023 · 5 comments
Assignees
Labels
bug Something isn't working ENTITY Business Team Priority1

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Nov 24, 2023

After filing an IA or registration (and eventually, amalgamation), Filings UI displays the filing in the ledger. At this time, the "new business" is still identified by its "Txxx" number (not its BC/FM number). This is a special IA/reg flow. In this flow, the NR that was used (if not a numbered company), is fetched. This step passes if the application is still pending, but fails if the application is Filed and Paid. It fails, presumably, because the NR has been unaffiliated as part of its consumption.

Private Zenhub Image

Private Zenhub Image

Potential solutions include:

  1. since we do not know the NR's phone or email key, we could go back and add it to the filing JSON in Create UI; then in Filings UI we would have access to it
  2. change the Legal API to not fail if the NR is consumed (assuming it's still affiliated, or despite it)
  3. change Legal or Auth API to not un-affiliate the NR once consumed
  4. see comments below
@severinbeauvais severinbeauvais added bug Something isn't working ENTITY Business Team Priority1 labels Nov 24, 2023
@severinbeauvais
Copy link
Collaborator Author

@severinbeauvais severinbeauvais changed the title Filings UI: don't fetch NR once IA is completed (filed and paid) Filings UI: NR error after filing an application Nov 24, 2023
@severinbeauvais
Copy link
Collaborator Author

Sample URLs that demonstate the error: (login as BCREG0020 or IDIR)

@severinbeauvais severinbeauvais self-assigned this Nov 24, 2023
@severinbeauvais
Copy link
Collaborator Author

severinbeauvais commented Nov 24, 2023

Potential solutions (cont):

  1. change Filings UI to NOT fetch the NR once the application is completed or paid

^^ This is the solution that I am implementing in this ticket.

@severinbeauvais
Copy link
Collaborator Author

Test Notes

To see this working, you need to load an "application dashboard" (ie, using Txxx number) after a named incorporation/ registration/ amalgamation application is filed.

I have tested this locally, ie

The application dashboard:
image

The business dashboard for the same entity:
image

@severinbeauvais
Copy link
Collaborator Author

@riyazuddinsyed

I verified this in Dev (https://dev.business.bcregistry.gov.bc.ca/Ty2i5TVeku?filing_id=147244&status=Q09NUExFVEVE).

I have also verified this in Test -- you can try loading the 3 URLs above that previously failed.

This was referenced Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ENTITY Business Team Priority1
Projects
None yet
Development

No branches or pull requests

2 participants