-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add corrected certificate for a Coop #18282
Comments
Mihai will explore with Ops about this happening within their team. |
From OPS: we can't create a correction certificate. So we need someone to create a correction filing for this COOP then we can update generated values in Database to match the pdf file for YEOMAN TREE SERVICE CO-OP - CP1003220. [2pdf20231108.pdf] |
Nov. 22/2023:
|
The corrected certificate must reflect the filing it pertains to. For instance, A name change on an incorporation application filing should NOT say "Name Change Corrected", it should say "Incorporation Application Corrected" A correction to a name change filing would say "Name Change Corrected' |
@Mihai-QuickSilverDev any chance this can get worked on soon.. its related to a high priority ops ticket. also a new one came in that might be fixed by this ticket... if not, can you create another high priority ticket for this fix. |
For the the other instances of this we issued the correction certificate directly to the client and set the dashboard to "Request a Copy". |
@rarmitag Thank you Richard! This is exactly what was agreed with the Business for the foreseeable future, for any such tickets!!! |
Related to Ops ticket https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/issues/gh/bcgov-registries/ops-support/3202
The text was updated successfully, but these errors were encountered: