Filings UI: local filings need to "return" to Dashboard UI
As per #21469, a new Dashboard UI will be created and will serve as the launching and return point for all filings, including the "local filings" currently done in Filings UI (and which will stay in Filings UI).
In this ticket, the following filings need to "return" (actually, redirect) to the new Dashboard UI.
- [x] if filing fails to start/load
- [x] on Save and Resume Later
- [x] on Cancel
- [x] after successful File and Pay
- [x] check misc error dialogs for exit/return/cancel options
- [x] check App.vue for potential startup errors
The affected filings are:
- AGM Extension
- AGM Location Change
- Amalgamation Out (WIP)
- Annual Report
- Consent for Amalgamation Out (WIP)
- Consent for Continuation Out
- Continuation Out
- Correction (of otherwise unsupported filings such as Annual Report and Conversion)
- Digital Credentials (not technically a filing but managed in Filings UI)
- Standalone Directors Filing (aka Change of Directors)
- Standalone Office Address Filing (aka Change of Addresses)
A Feature Flag needs to be used to support both the old and new functionality (for cutover purposes).
See also #22822.
Note that the local filings depend on Filings UI to load tombstone info (like user and business data and config). I expect this will continue to be done by "App.vue" when Filings UI starts up, before routing to the subject local filing.
(In other words, the local filings are not standalone and need to run in a framework that contains various tombstone data.)
@OlgaPotiagalova I'd recommend we hold on this until BTR is closer to go live. If implemented early we need to make sure that we aren't actually pointing to our page in PROD right away.
@severinbeauvais I have connected with @OlgaPotiagalova and she is comfortable with this being split. Can you create a ticket for redirection to the filing, and leave this ticket for returning back? @OlgaPotiagalova will connect to discuss sizing / scheduling. Our goal is to schedule to redirect to the filings as soon as possible.
The new ticket is #22822.
Thank you @severinbeauvais for creating #22822. Hoping it ends up being small and something your team can fit in soon:)
Thank you @severinbeauvais for creating #22822. Hoping it ends up being small and something your team can fit in soon:)
@mstanton1 We are planning to work on this in sprint 22.6, and to use a feature flag to conditionally enable the new functionality. Does that work for you?
@severinbeauvais that works. Thanks for sharing your planning. Does it make sense that my team supports with testing for the scenario where the flag is turned to return to our new dashboard?
@mstanton1 Makes sense to me, but I'd want to check with the testers to see if they want the testing split up like that or not.
@riyazuddinsyed What do you think about testing old (FF=off) vs new (FF=on) Filings UI functionality?
Test Note: Please Verify: all should redirect to the new Dashboard
- AGM Extension: Cancel, File and Pay
- AGM Location Change: Cancel, File and Pay
- ~~Amalgamation Out:~~ not enabled so cannot be tested
- ~~Amalgamation Selection:~~ not enabled so cannot be tested
- Annual Report: Cancel, File and Pay
- ~~Consent for Amalgamation Out (WIP):~~ not enabled so cannot be tested
- Consent for Continuation Out: Save and Resume, Cancel, File and Pay
- Continuation Out: Save and Resume, Cancel, File and Pay
- ~~Correction (of otherwise unsupported filings such as Annual Report and Conversion)~~ - not needed, correction is in edit UI
- ~~Digital Credentials (not technically a filing but managed in Filings UI)~~ - not needed
- Standalone Directors Filing (aka Change of Directors): Save and Resume, Cancel, File and Pay
- Standalone Office Address Filing (aka Change of Addresses): Save and Resume, Cancel, File and Pay
Comment by SB: the breadcrumb should also redirect to the new dashboard when the FF is True.
@mstanton1 This code is now deployed to Dev, but I have disabled the FF until the new business dashboard is ready to use. For your testing, you can create a rule in LaunchDarkly to enable the FF conditionally for specific users or whatever. Let me know if you need help.
The new FF is https://app.launchdarkly.com/projects/entity-ui/flags/use-business-dashboard/targeting?env=dev&env=test&env=production&selected-env=dev