Delay of Dissolution - LEGAL-API changes
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-01-17. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjA4NTM4)._
1. Allowable actions, disable other actions while in D1
2. Request for delay with create a delay of dissolution filing
3. Delay of dissolution is considered a filing, business-schema changes
4. Documents coming back (very few)
5. Delay of dissolution - client limits 2 - CRA / STAFF - unlimited - Column? Table? On the fly calculation?
6. Delay time rules are still undetermined (WIP)
7. Backend route for flags ( status for business etc)
8. Task - something we should do (on TOP) - Generated by the backend (might not do this, pending with Ethan)
Reuse dissolution filing, with a sub type.
https://github.com/bcgov/entity/blob/main/rfcs/rfc-business-states.md
https://github.com/bcgov/entity/blob/main/rfcs/rfc-colin-states-mapping-to-lear.md
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.