bcgov
Auth Web: FE filing should not display as Draft
Also, user should not have action to delete it.
- [ ] Status should be "Future Effective - Paid".
- [ ] Action should be "Open Application" (or Open Registration). No delete action.
- [ ] Also need to check what a paid-but-not-completed filing like.
Note: This needs to apply to filing :
-
[ ] Incorporation app,
-
[ ] Registration,
-
[ ] Amalgamation,
-
[ ] Continuation In
-
[ ] Reactivate in BC or Extra-Pro
I removed blocked label since we now have an API ticket for the necessary changes.
Guidance from Andy (from ticket #21978):
As for future effective, I was thinking that we might want to show something special in the MBR when an application has been Filed and Paid (and Approved if applicable) and is just awaiting the FE date/time to arrive. Right now we label those "Drafts" but they are different from drafts that still need to be filed.
@severinbeauvais What about just labelling them 'Future Effective'? Perhaps with a tooltip indicating the date? I seem to recall there was a ticket for this.
Also, should we show something special in the MBR if an application has been filed but payment is stuck? (In this case, the application state is Pending.) Either the user needs to retry payment (or try to pay another way) or Ops needs to reset some software module or something.
Whatever the state is on the entity dashboard, the MBR should reflect that. Either 'Pending' with an alert/tooltip or more explicitly 'Pending | Payment Incomplete' or something along those lines is my first thought.
Here's a better Figma link: https://www.figma.com/design/wVF8EcUCUR20YyqA0wHVJp/Continuation-In-V5?node-id=2983-13864&t=5xdDTS49a4MSC8d3-0
-
[x] Deployment in Test Env - @avnisalhotra @avni-work ~1400 hrs (08/13)
-
[x] Sanity check in Test Env and confirmation to move to Production ~EOD 08/13- @riyazuddinsyed
-
[x] Code deployed to prod in the next cycle (08/14) - @avnisalhotra @avni-work
