BE - make a limited restoration historical again

[severinbeauvais]

When a limited restoration's expiry date is reached, it needs to be made historical again.

Questions:

• Is there a new filing to dissolve it again? (Put Back Off?)
• Can we / should we reuse existing batch job?
• Should this ticket be done at the same time as work to dissolve a business not in good standing?
• What should be the state change, go back to dissolved?

To Do:

• [ ] Create new batch job to make the entity historical.
• [ ] Fit this into the bigger Dissolution work?

Ref: Dissolve Expired Limited Restotations

[jdyck-fw]

This ticket is dependant on the state model.

[jdyck-fw]

For involuntary resolution we can look at an RFC for batch jobs, for this one we will have Thor review the work.

[jdyck-fw]

@davemck513 will connect with @thorwolpert to discuss this.

[jdyck-fw]

This should likely happen after the migration to GCP.

[NaveenHebbale]

@thorwolpert Can we / should we reuse existing batch job? What will happen after GCP implementation

[thorwolpert]

If the existing job is just a container that gets executed (if it uses standard k8s cronjob) then it becomes a CloudRun Job and gets scheduled in CloudScheduler. CloudScheduler is maintained by the SRE team, so you just need to let them know the name of the job and they will schedule it in. Best to open a tix for the SRE team so that it gets tracked as a dependency.

[severinbeauvais]

This ticket has some big questions in it:

• what should happen when the limited restoration expires? (ie, need business input)
• is there an existing batch job?
• should we add this to an existing batch job or create a new, specific batch job? (ie, need design)
• should we do this at the same time as other automated dissolutions? (ie, need planning)

Then, we can implement what's needed and get it configured into CloudScheduler as Thor has described.

[NaveenHebbale]

@argush3 @OlgaPotiagalova

• Is there a new filing to dissolve it again?
• Can we / should we reuse existing batch job?

[thorwolpert]

Ideally the business is closed again with a dissolution filing. Having an end of life filing is helpful for any future restoration processes. There are a few ways a business is dissolved that block it from being restored - or at least a self-serve restoration.

[NaveenHebbale]

Input from Argus [3:33 PM] Chiu, Argus 1 CITZ:EX i talked to Thor a bit and i think we can create a new batch job for dissolutions. we can use the existing dissolution schema. one of the outstanding questions is which existing dissolution type do we want to use for these dissolution filings. [3:33 PM] Chiu, Argus 1 CITZ:EX https://github.com/bcgov/business-schemas/blob/main/src/registry_schemas/schemas/dissolution.json#L22-L31 business-schemas/src/registry_schemas/schemas/dissolution.json at main · bcgov/business-schemas Manages the JSONSchemas for the BCRegistry Legal Filings. - bcgov/business-schemas [3:34 PM] Chiu, Argus 1 CITZ:EX We have involuntary which is typically system driven and there is also administrativewhich is typically done by staff. i'm assuming we use involuntary but you can confirm with the business what they want.

[severinbeauvais]

Blocked on requirements.

I added @davemck513 's team label as this is related to GCP and batch jobs.

[vikas-gov]

Needs further discussion before it can be estimated.

[severinbeauvais]

Per @Mihai-QuickSilverDev , a limited restored business just becomes historical again -- no need for involuntary dissolution flow.

@davemck513 @JazzarKarim @argush3 Does your involuntary dissolution flow specifically ignore businesses that are active but limited restored?

[argush3]

Yes, involuntary dissolution flow will ignore businesses that are in limited restoration status.

Involuntary dissolution eligibility criteria