Edit UI: add support for correcting a BEN (AR, COA, COD)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Maybe this should be a story so we can:
- design the UI (or can devs simply follow the existing Edit UI filings?)
- create a new page
- **this may just be a reuse of the BEN IA correction page**
- add the necessary components
- **identify which fields can be corrected**
- create tickets for any new components (copy new components from original filings if possible)
- validation, save, resume, file
NB: BEN IA corrections are already implemented - see [BEN IA Corrections epic](https://app.zenhub.com/workspaces/entities-team-space-6143567664fb320019b81f39/issues/bcgov/entity/13093).
**Questions:**
1. what about correcting a BEN Alteration?
2. does the "BEN COA effective tomorrow" business rule impact the correction or the timing of the filing?
To Do List:
- [ ] Update requirements for each local filing type.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked BEN IA Corrections epic and review the existing BEN IA correction page as the proposed reference. Clarify the requirements for each local filing type, including correctable fields, BEN Alteration handling, and the effective-tomorrow rule. Done means the UI requirements cover design, validation, save, resume, and filing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100