Closed JohnamLane closed 2 years ago
@janisrogers and @jennyschan I have entered draft pop-up messages for each of the scenarios covered in the spreadsheet above. Can you please review these and revise as needed. Also, please complete the column named "Pop up Buttons"
@janisrogers I see lots of pending content. I was hoping to get this into the next sprint. Can you please focus on finalizing the written content for these messages? Kial has already provided the scenarios so it's known that we will be encountering/detecting these issues.
@kialj876 I have a few questions. Can we meet to discuss this?
@janisrogers This must be worked on next sprint. Please book time and get these messages 100% or we will need to proceed with the draft messages. Please confirm content/actions in time for grooming September 13th. If this isn't possible please let me know.
ToDo (John)
To be logged separately.
Hey team! Please add your planning poker estimate with Zenhub @kialj876 @thorwolpert @lekshmimallika-aot @ritvick @Ashna-FreshWorks @seeker25 @MatthewCai2002
@janisrogers @Ashna-FreshWorks
NOTE: accounts to test the various error scenarios can be found in here https://docs.google.com/spreadsheets/d/1UTpFigwN9sj8z9gIGLouCw4XBalHUPYkub7qsNmc4FU/edit#gid=345382686
Also, 3 scenarios described in the original ask are not implemented (I went over these with John already, but letting you know for testing).
The post payment screen currently cannot be accessed without first clicking on 'view documents' from the purchased doc table. If this needs to change then we need a ticket to rewrite how that page is 1st setup/loaded (out of scope for this ticket). The current behavior will redirect the user to the dashboard if they were to go t it directly (i.e. bookmark etc.).
With the current workflow described above the purchased document expired scenario and loading purchased business documents on that same screen (Letter under seal etc.) will never happen. After talking with John he agreed we can pull these scenarios out.
The other one not completed in this ticket is the popup dialog on the bcregistry page. This page is in Nuxt 2 so it cannot use the shared code from search and there are no other products that use this workflow yet. After talking with John he agreed we can take this out and implement it later for all the products on the page. If we wait until it is in Nuxt 3 it will allow us to use the shared code used in search as well
The scenarios and desired message will be here
This ticket encompasses the first tab of the spreadsheet https://docs.google.com/spreadsheets/d/1tnFaDPzRojK60R-TzKh-iXFE9I5a30ydDow3iWkvIhM/edit#gid=0
Wireframes
https://preview.uxpin.com/b8c15ffc26e45b791ebef7e502aec9b9f5c46cb6#/pages/157232208