Legal API: Future Effective regular filings can't display POA/Court order - filing.data object issue

bcgov / entity

ServiceBC Registry Team working on Legal Entities

Apache License 2.0

23 stars 58 forks source link

Legal API: Future Effective regular filings can't display POA/Court order - filing.data object issue #23651

Open ArwenQin opened 1 week ago

ArwenQin commented 1 week ago

For 2 regular filing types: Alteration and Voluntary dissolution, they can be filed Future Effective. The ledger doesn't display the POA/Court order now. This is because the "get filings" call returns an array of filings with redacted data and doesn't have a filing.data object yet.

Sample VD: https://github.com/user-attachments/assets/0a737322-b7cc-4ae5-81f4-885f16bbb17e https://dev.business.bcregistry.gov.bc.ca/BC0871344?filing_id=151370&accountid=3040

FE IA/ContIn is good because for a bootstrap filing, the get filings call returns a single filing with all JSON data.

ArwenQin commented 1 week ago

@vysakh-menon-aot To show court order / POA on a regular FE filing, we'll need to decide how to provide that data in the redacted filings data. What the data structure should be for a FE filling? Do we include the filing.data object anyway?

cc: @severinbeauvais

severinbeauvais commented 1 week ago

After discussing today with Olga, Mihai and Vysakh, it was decided to worry about implementing this later. Consider:

COLIN doesn't show court order info in the ledger (whether FE or not)
the FE filing, once effective, will show court order info
staff haven't asked to show court order info in this situation
we don't want to increase the data returned in the "get filings" response
we could instead make an extra call from the UI to fetch the filing JSON and get the extra data

So, for now, I've put this ticket in the Product Backlog. We will consider it low priority for now.