bcgov / bcgov/entity

COLIN script - set AR reminder flag to false

Open
#30,922 0 comments 0 reactions 0 assignees View on GitHub
blocked Entities - Data Migration Needs Decision
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Note: need approval to do this from business + home team before we can proceed with this work**

It appears that even if a corp is frozen in the legacy system, AR reminders can still go out if the AR reminder flag is on.

We need a way to programmatically turn off the AR reminder flag after a corp has been migrated.

There needs to be some thought around how this will be done. Do we update the current COLIN freeze flow script or do we create a new script for AR reminder? I think a new script might make sense as it may be too easy to forget to flip freeze flow config key/values(`FREEZE_ADD_EARLY_ADOPTER`, `FREEZE_COLIN_CORPS`) appropriately for each scenario(COLIN freeze and AR reminder updates)

The current process is the following. We probably need to have a way of setting all AR reminder flags for the corps to be migrated to false either after step 2 or 3.
1. Run colin freeze flow(freezes + add corps to early adopter table) to freeze corps.
2. Get latest COLIN extract
3. Migrate corps to modernized system.

**Tasks**
- [ ] Add/update prefect flow to turn off AR reminder flag for migrated corps
- [ ] Make updates to COLIN extract ddl as required
- [ ] Ensure AR reminder flag update is tracked `colin_tracking` table. Thought needs to be put into how this will work with the colin freeze flow. do we update the same entry or add a new one?
- [ ] Determine when this flow should run in the migration process?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the current COLIN freeze flow and its Prefect entry point, then review the COLIN extract DDL and colin_tracking table. Determine where migrated corps should have their AR reminder flags disabled, how that update is tracked alongside freeze flow records, and when the flow runs. Done means the flow, required extract changes, tracking behavior, and migration timing are defined and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, python
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.