Filings UI: handle multiple draft states and other changes

[severinbeauvais]

New Description

• [x] make the minimum changes to unblock remaining development of continuation ins
  • handle new states in proper lists (Todo, Pending, Filing History) [Draft, Submitted, Change Requested, Resubmitted?, Approved, Rejected]
  • don't worry about button labels
  • do add split menu to delete the authorization/application from Todo list
  • BTR team will make the full new design changes in the new code base (business dashboard)

Old Description

At a minimum:

• Draft status redirects to Create UI (does Todo list item look different from now?)

• Change-Requested status redirects to Create UI (does Todo list item look different from now?)

• Approved status redirects to Create UI (new)

• Awaiting Review status shows in Pending list (does item look different from now?)

• Paid and Completed status show in Filing History List (no change from now?)

• other UI changes per new design (need to constrain this, or create new ticket)

• [x] show NR expiry

• [x] action names (draft vs application)

• [x] show reason in gray block

New design: Continuation: Dashboard States

[severinbeauvais]

Reason in gray block:

[vikas-gov]

https://www.figma.com/design/rNe2jn8wyFykKRzwiBo6ar/Continuation-In-V6?node-id=100-4595

[severinbeauvais]

This ticket is blocked until we meet with BTR team, on Oct 8 at 3pm, to decide how to handle this Dependency ticket.

[severinbeauvais]

I have unblocked this ticket as we can now work on it.

I reduced the estimate as we are now doing the minimum to permit the new continuation in designs. (It may still be high depending on your definition of "mininum").

[severinbeauvais]

I merged Arwen's code changes. If there are remaining changes, they can be done in another PR or another ticket.

UX peeps, please have a look at the changes.

[jacqueline-williams-549]

@ArwenQin

• Changes Requested Design
  • update language for changes requested dashboard state: "Please make the following updates to your continuation authorization document."
• there has also been changes to the language of the cards on the dashboard (should this be captured in a new ticket @severinbeauvais)
  • When it is in the authorization stage, the filing is called 'authorization'
  • When it is in the application stage, the filing is called 'application'
  • When it is in the authorization stage, use the language 'submitted' instead of 'filed' (see designs)

[severinbeauvais]

OK, moving back to In Progress for further changes.

[severinbeauvais]

This ticket (Filings UI) is the dashboard. Do you mean that we should change some language on the "registry" (MBR)?

I think we can make the language changes in this ticket (no need for a new ticket).

[jacqueline-williams-549]

We decided to keep the language on the MBR as is, but to update the language on the dashboard so the card says 'authorization' instead of 'application' (when the user is still on step 0). Can you confirm this @janisrogers ? Yes this is confirmed.

[severinbeauvais]

Sounds good. Yes, we can make the text changes in this ticket.

[severinbeauvais]

Do you want the BC Registries contact info on certain cards, like the Change Requested one above?

[jacqueline-williams-549]

The authorization pending review state does also show contact info.

Designs are here: https://www.figma.com/design/rNe2jn8wyFykKRzwiBo6ar/Continuation-In-V6?node-id=100-4595

[severinbeauvais]

This ticket is more complicated than I expected so I've updated the estimate to 5.

[ArwenQin]

FE Application design please see:

The future effective text and contact info were not in the original design ( https://www.figma.com/design/rNe2jn8wyFykKRzwiBo6ar/Continuation-In-V6?node-id=100-4595&m=dev&focus-id=664-72490) - design is at the bottom

[ArwenQin]

@jacqueline-williams-549 Hi Jacqueline, we just finished this ticket, so further UI updates will be in a new ticket. (Exception: if something is broken by this PR then we keep working on it.)

[jacqueline-williams-549]

@ArwenQin Okay that sounds good, thanks Arwen

[jacqueline-williams-549]

SB says: the following comments have been moved to new tickets.

1. Entity Dashboard: Authorization Approved State - Resume the Continuation Application

2. Entity Dashboard: Pending Review State - Button language updated

3. Entity Dashboard: Rejected State - Wanting to make the 'Rejected' text bold so that it passes accessibility standards. Other language updates shown in screenshot. (Sorry there wasn't a design for this earlier - Rejected Authorization Design - Should I put this in another ticket @ArwenQin ?)

4. My Business Registry: Authorization Approved State - Button language updated. When the authorization is approved, on the MBR the button should say "Resume Application"

5. Entity Dashboard: Submit Authorization Modal - Can remove this constraint on the file upload section of the Continuation Authorization?

[severinbeauvais]

Thanks for the feedback! Can you please move it into a new ticket? Thanks.

[jacqueline-williams-549]

Yes no problem! Moved it here: Entity Dashboard and MBR: Authorization and Application States 23935

[severinbeauvais]

Thanks, Jacqueline!

FYI, I broke up 23935 into a couple of other tickets because the changes are in different projects.