bcgov / bcgov/entity

Notice of Alteration

Open
#4,959 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

### Description
Alterations are dynamic so we need to identify what components changed in each NOALA to generate the correct information on the Alteration Application and know when to trigger a c/n cert

This ticket includes the following:
- [ ] Update schema with any new information
-- [ ] pre-existing provisions indicator
-- [ ] special resolution /court order date
-- [ ] something to indicate name change occurred?
- [ ] Reproduce the alteration application output using new formatting
- [ ] Update Notice of Articles to add special resolution (if any), pre-existing provisions, and remove benefit company statement
- [ ] Display filing and the following outputs in the recent filing history:
-- [ ] Alteration application
-- [ ] Notice of Articles
-- [ ] Receipt
-- [ ] Name Change certificate (if applicable)

EVENT_IDs for the NOALA:
![image.png](https://images.zenhubusercontent.com/5d814bb8edbc510001817803/078139d3-06a4-4a1b-92c1-f98f4b201aba)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the NOALA schema, EVENT_IDs, alteration application output, Notice of Articles, and recent filing history mentioned in the checklist. Done means the schema captures the listed alteration details and the specified application, notices, receipt, and conditional name-change certificate appear with the required formatting.

Written by the indexing model from the issue text.

Assessment

Domain
backend, database, 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.