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

PAY-DB - Ensure BCRS-SHARED-COMPONENTS filing enum is satisfied in production #18453

Closed
seeker25 opened this issue Nov 3, 2023 · 3 comments
Closed
Assignees
Labels
ENTITY Business Team Relationships Ops Relationships Work for Relationships team

Comments

@seeker25
Copy link
Collaborator

seeker25 commented Nov 3, 2023

**Hi All, no filings of any sort should be done for BC Ltd companies in BCROS Production. BC Ltd companies would not be in Production until the COLIN Modernization Phase I, sometimes in 2024. This record was created in BCROS by mistake about one year ago.
To Do List:

Delete the Address Change draft filing in BCROS.
Block/freeze this record in BCROS as per instructions already in place from Elizabeth.
Add banner to redirect the user to COLIN.
Transfer as needed in COLIN any filings done in BCROS only.
Complete the address change for the user in COLIN, as they already paid for it.**

Private Zenhub Image

https://github.com/bcgov/bcrs-shared-components/blob/main/src/enums/filing-codes.ts

@seeker25 seeker25 added Relationships Work for Relationships team Relationships Ops and removed Relationships Work for Relationships team labels Nov 3, 2023
@seeker25
Copy link
Collaborator Author

seeker25 commented Nov 3, 2023

Analysis - from PROD:

select * from fee_schedules where filing_type_code in ('OTCON')
order by corp_type_code, filing_type_code;


--ADDRESS CHANGE - BCADD - missing for BC on PROD - What about BC/CC/ULC?
--ADDRESS CHANGE - OTADD - CP
--AGM_EXTENSION - AGMDT - BC, BEN, C, CC, ULC
--AGM_LOCATION_CHANGE - AGMLC - BC, BEN, C, CC, ULC
--AFFIDAVIT - AFDVT - CP
--ALTERATION - ALTER - BC, BEN, CC, ULC
--ALTERATION BC TO ULC - BC, C, CUL, ULC
--ANNUAL REPORT - BCANN - BEN, BC, ULC, CC
--ANNUAL REPORT OTHERS - OTANN - BEN, CC, CP
--CHANGE OF REGISTRATION - FMCHANGE - SP/GP
--CONSENT_CONTINUATION_OUT - CONTO - BC, BEN, C, CC, CUL, LTD, ULC
--CONTINUATION_OUT - COUTI - BC, BEN, C, CC, CUL, ULC
--CORRECTION - CRCTN - BC, BEN, CC, CP, ULC
--DIRECTOR_CHANGE_BC - BCCDR - BEN - What about BC, CC, ULC? 
--DIRECTOR_CHANGE_OT - OTCDR - CP 
--DISSOLUTION_ADMINISTRATIVE - DIS_ADMIN - BC, BEN, CC, LTD, ULC
--DISSOLUTION_COURT_ORDERED_LIQUIDATION - BC, BEN, CC, LTD, ULC
--DISSOLUTION_INVOLUNTARY - DIS_INVOL - BC, BEN, CC, LTD, ULC
--DISSOLUTION_RESTORED_IN_ERROR - DIS_RSTR - BC, BEN, CC, LTD, ULC
--DISSOLUTION_VOLUNTARY - DIS_VOL - BC, BEN, CC, CP, GP, SP, ULC
--DISSOLUTION_VOLUNTARY_LIQUIDATION - DIS_LQD - BC, BEN, CC, CP, LTD, ULC
--FM_CHANGE - FMCHANGE - GP, SP
--FM_CONVERSION - FMCONV - GP, SP
--FM_CORRECTION - FMCORR - GP, SP
--FREE_DIRECTOR_CHANGE_BC - BCFDR - BEN - What about BC etc?
--FREE_DIRECTOR_CHANGE_OT - OTFDR - CP 
--INCORPORATION - BCINC - BC, BEN, CC, LTD, ULC
--INCORPORATION OTHER - OTINC - CP
--REGISTRATION_GP or SP - FRREG - GP, SP
--RESTORATION_FULL - RESTF - BC, C, CC, CUL, QE, ULC - no BEN?
--RESTORATION_LIMITED - RESTL - BC, C, CC, CUL, QE, ULC - no BEN?
--RESTORATION_LTD_EXTEND - RESXL - BC, C, CC, CUL, QE, ULC - no BEN?
--RESTORATION_LTD_TO_FULL - RESXF - BC, C, CC, CUL, QE, ULC - no BEN?
--SPECIAL_RESOLUTION - SPRLN - CP
--SPECIAL_RESOLUTION_NAME_CHANGE - OTCON - CP

@seeker25 seeker25 self-assigned this Nov 3, 2023
@seeker25
Copy link
Collaborator Author

seeker25 commented Nov 3, 2023

Low risk these aren't launched:

https://github.com/bcgov/lear/blob/main/legal-api/src/legal_api/models/filing.py

Private Zenhub Image

Restoration isn't an issue, it's still in development.

The top 3 still apply, but aren't launched in prod.

image

Backend:
image

image

image

image

@Mihai-QuickSilverDev
Copy link
Collaborator

  • This ticket is not to be continued on, for the initial purpose it was created.
  • We do not have active BC Ltd. filings in BCROS at the moment.
  • If there are any questions left for fee codes for new entity types coming to BCROS in the future, I will open a new ticket as needed.
  • Closing this ticket down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENTITY Business Team Relationships Ops Relationships Work for Relationships team
Projects
None yet
Development

No branches or pull requests

2 participants