bcgov
Create new Entities dashboard page
Currently many of the changes within this epic take place on the entity dashboard. Due to legal name work and Vue3 upgrade in flight there are delays if we wish to write to the existing entities tombstone. A proposed solution is to create our own page, lifting from what was done in the Business Search side. Entities can point to this page at a later time.
Note: To-do list is part of this epic and the proposal is to handle this using flags that are already in place with Entities. A key action would be to review and ensure the logic supports having more than one active to do item - and does not prevent filing of other documents when that to do items is pending. Business Rule for SI Filing: Only prevent SI filings for companies that are historical or frozen. This will not address changes in the company information page. That could be tackled when Entities has completed their Vue3 upgrade and is not critical for MVP.
Wireframe/Screenshot Samples https://www.figma.com/design/igaZgN1ZaHwM7pJPb8Bu9Y/Dashboard?node-id=2064%3A2249&t=VJ8Zn1i6At7mSBa2-1
Business Dashboard “Versions” Client, BC Registries Staff/BCOL Helpdesk/SBC Staff (TBD) Draft, Business State versions (Business Status) Active, Historical, Frozen, Others TBD
Business Dashboard Features
Errors/Exceptions Dashboard Unavailable
Badges Business Status
Alerts Not in good standing
To Do (count) Filings due (AR) (File Now) Draft filings (AR, Director Change, etc.) (Resume/Cancel) Authorization Requests (Do not Authorize / Authorize)
Errors/Exceptions LEAR unavailable PayBC unavailable / available
- Payment pending/incomplete (Resume/Cancel Payment)
- Payment Unsuccessful (Retry/Cancel Payment)
- Processing Payment (busy)
BCOL and PAD errors/exceptions
TBD
- Basic account: Online banking
- Premium account: EFT(invited user only)
Recent Filing History (count) Filing Future Effective Filing Errors/Exceptions Filing Pending / Payment successful
Disabled/Other states Draft filing in progress (disabled Change buttons) Not in good standing (disabled To Do buttons) Historical (no Change buttons)
Draft Dashboard Draft details – Incorp/reg type/NR number Incorporation / Registration (Incorporate using NR/Cancel) Draft filing (Resume/Cancel) Name Request details Errors/Exceptions
- PayBC unavailable
- Payment pending/incomplete (Resume/Cancel Payment)
- Payment Unsuccessful (Retry/Cancel Payment)
Processing Payment (busy)
Staff / BCOL Helpdesk Dashboard Additional Features Comments Staff filings – modals, context sensitive depending on business status Corrections – links correction to filing Details – text comments per filing
Suggested Option
- create in it's own project with it's own deployment
- leverage existing API, this is UI work only
- build as if it will be the new version of this page leveraging what was done for the business search version
- move components over to nuxt UI
- when entities upgrades they will update the code base and link to the new page
Unknown
- how would they adopt this from us?
High Level Requirements
- attached below. Note, these include variation for staff and client.
@mstanton1 Differences noted between Staff and Client view: https://docs.google.com/document/d/1pMBL0GxZW7HPraaaeEB7K2HgC0j2Af_9/edit?usp=drive_link&ouid=100179527247507750986&rtpof=true&sd=true
T-shirt sized at 3 sprints.
Key unknown is what automated testing exists (and if any, could we use those as opposed to having Guna write more). @gunanagar can you check with Riyaz to see if there is any Cypress testing that can be re-used?
- create page template with common layout components (header, footer, breadcrumb, current tombstone from BTR) and create repo (dev and test access) - add dependency label because patrick wei will be needed for URLs, will need to update password for configs
- update business tombstone (needs requirements on additional entities functionality)
- create office address section
- create directors section
- create alerts section
- create to do section (story to be broken down)
- create recent history section (story to be broken down)
- create staff dashboard version (story to be broken down)
- create comment widget (part of staff dashboard story)