-
Notifications
You must be signed in to change notification settings - Fork 59
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
Legal API: fix alteration of company type issues #24041
Comments
Steps to Reproduce:
|
Here are the updated requirements.
(and all the continued-in equivalents) |
@OlgaPotiagalova @vikas-gov Since we are enabling BEN->CC alteration, we need to document it somewhere that these businesses will be out of sync with COLIN until we introduce an equivalent filing type in COLIN |
How about another sync ticket? |
That's needed for sure. I was saying either we need to disable this using FF in PROD (unless we are ok with out of sync data) |
If we don't expect many (or any) business conversions from BEN to CC then we could do nothing ... but that's an @OlgaPotiagalova decision. What's the risk if this does happen? How much effort is creating an equivalent filing type in COLIN? |
Impact: Will fail to sync the specific alteration and subsequent filings in that business. Home team has to introduce this filing type and update all the relevant messaging (BN, MRAS, or any other). Once its in place we can update colin-api with the new filing type. |
BC -> BENBC Business: BC0883711 BC-> CCBEN -> BCBC -> ULCULC -> BCBEN -> CCULC -> BEN |
Continued In Limited Company -> CCC Continued In BEN -> CCC |
See results from #23941.
Steps to Reproduce:
Edit: Ensure the following works:
Also, ensure the above codes work for C, CBEN, CCC and CUL business types.Edit: Updated above codes to list every allowable alteration in lear. If any are missing let me know.The text was updated successfully, but these errors were encountered: