search

bcgov / entity

ServiceBC Registry Team working on Legal Entities
Apache License 2.0
23 stars 58 forks source link

UI Design: List of errors/exceptions/failure points for validation #19217

Open forgeuxGH5 opened 8 months ago

forgeuxGH5 commented 8 months ago

Create a list of errors/exceptions/failure points for validation and design handling for each

API Errors:

Page loading (either for whole page, or for individual pieces):

PPR Examples

Non- Payment Errors: https://docs.google.com/document/d/1T8CGhrV7WZr36OmaalCqaMfhKdMqZbgyw4GYkZg_L1g/edit#heading=h.kp4zbafwpq05

Payment errors: https://docs.google.com/document/d/17C6DTDnkDJ4bgYsDS2pb1KiBZN_MaxEBMGBgb7bo8eI/edit#heading=h.kp4zbafwpq05

Designs They are in UXPin in PPR, the file is labeled "Error" https://preview.uxpin.com/6b672d86df0756e8a753aa84b82497c39dab1608#/pages/139884293

steveburtch commented 8 months ago

@Apt766525 I think this is a separate meeting, walk through the standalone filing.

steveburtch commented 8 months ago

@Apt766525 please get in touch with the BA on Assets to see if they can help us characterize these errors.

lbergero819 commented 8 months ago

@doug-lovett @dimak1 I checked with Avinash and what they need is an extract of our error messages. Regarding the APP INIT keycloak, launch darkly flag and auth API failures, I referred him to OPS Patrick Wei. Can one of you attach an extract list of our messages to this ticket sometime this week.

dimak1 commented 8 months ago

@lbergero819 yes, we can extract and organize error messages from the UI. Let's create a ticket for it as we already have tickets for this sprint. cc: @arlentees

steveburtch commented 8 months ago

@dimak1 @lbergero819 @Apt766525 thx guys for pitching in on this. I think Avinash has already sent you an email explaining that we Kial will be working with our designers to address this, but just want to relate that3 we really appreciate your willingness to help!

mstanton1 commented 4 months ago

@forgeuxGH5 The linked tickets are showing as closed. Can this be closed as well or is there other work to groom? I would assume some of these things may still be the same (e.g. fee summary) but many other validations may have changed due to the significant changes in the significant individual form. If this is still open with work to complete should we move it back in the pipeline so it can be reviewed (at a later time when we dig into validations)?

forgeuxGH5 commented 4 months ago

@mstanton1 I don't see a ticket to do the actual error/exception design. It also seems like there is still a lot to sort out to actually design the error/exception handling. Would that be in a future linked design ticket? If so, that ticket would need to be linked to this ticket so I guess this one could be closed.

mstanton1 commented 4 months ago

@forgeuxGH5 there are a number of validation design tickets and I'm not sure I understand the breakdown, but the key is that it's logical and clear to the design team.

19217 (this ticket) - UI Design: List of errors/exceptions/failure points for validation

19302 - UI Design: Non-schema submission validations

20800 - UI Design: No Significant Individuals Exist error validation and scenarios

Since the other tickets seems specific to non schema and no SI's it doesn't appear we have another 'catchall' validation ticket. We could move this back into product backlog or create a new ticket on the epic for UI Design: Validation for add significant individual filing. What's your preference?