-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filings UI: Admin Freeze should not show on ledger #16967
Comments
This can be handled by the Legal API (by not providing the ledger entry for display)... unless we want to provide it to API users? @thorwolpert |
Pinning this for consideration for 18.2 |
Was thinking we update the BE to provide a flag to indicate whether a filing should be displayed on the ledger. The UI will need be updated to make use of this. Thoughts @severinbeauvais @thorwolpert ? |
Update: irrelevant comments! See new comment below. |
I don't think it will be in the business response if I'm understanding your question correctly. This flag will be specific to a filing. So the displayLedger flag can be returned in the GET /filings and GET /filings/<filing_id> endpoints I think. I was thinking just add a dictionary to the BE that defines filings that shouldn't be displayed on the ledger. And these two filing endpoints will just use to set the flag accordingly. At the end of the day, for our use case, we probably only need to update the GET /filings endpoint. Examples |
We decided a while back not to add hide/open ledger items. |
Argus, I was confused -- never mind my last comment! Yes, Business Filings UI would need a small change to not show this filing in the ledger, according to your new flag. |
@elizabethanneespinosa Hi Elizabeth, could you please re-confirm the reason behind not showing an Admin Freeze on the ledger? My understanding is that we are trying to avoid having the clients calling BC Registries, and questioning our actions. Instead the communication for missed payment, which is usually a reason for the freeze, would take place on different channels. |
https://docs.google.com/presentation/d/14ZPjw-VT2kniECBEMqc5E_jBW6TxV6HA/edit#slide=id.gf495bffbf0_0_14 this show the history of the requirements as captured by Sarah E. Let me know if you have any questions. |
This ticket can be implemented but not tested until #18490 is implemented. |
From description:
Where should staff add comments? Not to the "Admin Freeze" (or "Admin Unfreeze") ledger items since we're removing them. |
Staff would add comments, at any moment, as needed, here highlighted below, independent of the Freeze/Unfreeze filings themselves. |
OK, perfect, thanks. |
@Mihai-QuickSilverDev any update on this one? |
@Mihai-QuickSilverDev @davemck513 are there any updates on this one please? |
@davemck513 @Mihai-QuickSilverDev Should we show the freeze and unfreeze filings in the ledger to staff users? If not, how will they see any detail comments that they put in? (We could move/copy the freeze/unfreeze comments to the staff comments section but that would require extra code changes.) |
@severinbeauvais This was discussed before in this ticket. No comments would be handled part of the freeze/unfreeze filing. Staff would go separately and use the Staff comments already existing on the Entity's dashboard. |
Thanks, Mihai. Yes, I found the conversation on Nov 7, 2023. BTW, as this ticket is no longer blocked, we should perhaps move it to the current sprint. |
When an entity is frozen this should not show on the ledger.
Staff should still be able to add comments.
Any existing Freezes should be removed from the ledger.
Requirements located here: https://docs.google.com/presentation/d/14ZPjw-VT2kniECBEMqc5E_jBW6TxV6HA/edit#slide=id.gf495bffbf0_0_14
To Do List:
Example:
Private Zenhub Image
The text was updated successfully, but these errors were encountered: