bcgov / bcgov/entity

UI Design | Liquidation: Validations (Post-Migration?)

Closed
#32,818 1 comment 0 reactions 0 assignees View on GitHub
Colin Egress UX UX Assurance
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**What we need**
Need confirmaiton on which fields should be required across the liquidation filings. We **may** need designs for what happens when a user tries to submit a form with missing required information

**Filings Built**
Intent to Liquidate
Appoint Liquidator
Cease Liquidator
Liquidator Change of Address
Liquidation Report

**Filings Not yet Built**
TBA

[Liquidation Filings — Component & Field Matrix](https://bcgov.sharepoint.com/:x:/r/teams/07717/Shared%20Documents/Entities%20Product%20Team/Liquidation/liquidation_matrix.xlsx?d=w95e70e5e669f415c8f0162ab6f4be077&csf=1&web=1&e=6hAUDs)

### Resources
[Filing Sequence for Liquidation](https://bcgov.sharepoint.com/:w:/r/teams/07717/_layouts/15/Doc.aspx?sourcedoc=%7BF1986AA7-98A2-4C48-BEC2-E5C7EB520C39%7D&file=Filing%20Sequences%20for%20Liquidation%20Filings.docx&action=default&mobileredirect=true)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the linked Liquidation Filings — Component & Field Matrix and the Filing Sequence for Liquidation resource. Confirm which fields are required for each listed filing and document the agreed behavior and designs for submitting forms with missing required information.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.