-
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
UI Design: Draft IA with Expired NR Flow #18237
Comments
@janisrogers I created a design ticket to address the bug you found. The bug is considered P2 atm. |
To review the scope when this ticket is picked-up. |
PO Input: Limit the scope to updating the modal content to: Out of scope: Any nice to haves.
|
Slight snag here: when you resubmit a NR, you get a new NR number. But the NR number is baked into the IA, so they won't be able to "continue" the IA unless Ops goes into the db to update their IA. |
So an expired NR is a throwaway? |
By resubmitting an expired NR, users save some time by not having to reenter all the previous details. And once re-submitted, they get a new NR, new pay, and the expired NR goes to waste. I think we literally have thousands of these, if not tens of thousands. |
Scenario:
The user starts an incorporation application from an NR. The user leaves the draft filing for enough time elapses that the NR is expired when the user resumes the draft. When the user returns to the draft filing, then the user has a few options.
1. The user may want to resubmit the NR while keeping the draft filing.This should not be allowed as it is not currently possible to add a new NR to a draft filing2. The user may want to delete the draft filing, and resubmit the NR.
3. The user may want to do nothing.
We need a design that covers these scenarios so that there is a good way to close the user flow loop.
Wireframes (WIP)
https://preview.uxpin.com/7f88c9d90092025bf1206292dbd74a127c938cb4#/pages/164684803
The text was updated successfully, but these errors were encountered: