Open shekarpendem opened 6 years ago
@tram We have a couple of error messages for you to review. the first is the global error message when there is a 500 error. Per conversations with @bryanmcfadden, we changed the text from 'Server error' to 'We were unable to process your request.'
The next error is when we get an error response from pay.gov. We are on the fence about including the pay.gov error message, but we decided to put it in there in case a user needed to relay the message to customer service. What are your thoughts there?
👍 Humanizing "Server error". 🤔 In what instances are people most likely to see these errors? I'm wondering how long "please try again later" is recommending to wait—try again now or in an hour or tomorrow. If they should try again now, maybe something like…
<div class="usa-alert usa-alert-error" role="alert">
<div class="usa-alert-body">
<h3 class="usa-alert-heading">Sorry, we were unable to process your request. Please try again.</h3>
<p class="usa-alert-text">If you continue to get this error, please contact<a href="mailto:fs-permitting-project@gsa.gov">fs-permitting-project@gsa.gov</a>.</p>
</div>
</div>
good recommendation @tram. This should 'never' happen, however, sometimes servers do go down. In this case, the error would be if there is a misconfiguration on pay.gov or if pay.gov's server is down. In most cases, please try again should fix the issue.
Updated per your feedback @tram
Cool! You should also be able to remove the "Sorry for the inconvenience, but…" line since it's handled in the h3
now.
@tram, good catch. I removed that line.
:+1: Ship it!
This task flow has been updated to swim lanes for readability.
user_task_flow_permit_purchase_168.pdf
First draft:
Notes
Acceptance Criteria
Tasks
Definition of Done