Purchase request QA 2.0
See original GitHub issue- A few times, I was not able to purchase request with a new user. I cannot reliably reproduce.
- Do not see the error event
Purchase request failed to submit
firing. i.e. every time the “send request” button is clicked and it fails, we need to report the reason for the failure.
Everything else seem to be firing perfectly! Reference issue: https://github.com/artsy/force/issues/463
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (11 by maintainers)
Top Results From Across the Web
IT Purchase Request/Acquisition Form
IT Purchase Request/Acquisition Form. This form must be completed for all hardware and software purchase/acquisition requests. All requests for approval for.
Read more >PART 46 – QUALITY ASSURANCE - Acquisition.GOV
(a) Requirements are provided on the purchase request in EBS. 46.105 Contractor responsibilities. (b) The contractor is required to maintain calibrated ...
Read more >QA Report 2.0.34 | Documentation@ProcessMaker
Features Bugs. Release 2.0.34. Pre-Sales Process. Employee Onboarding. Expense Report. Invoice Approval Process. Purchase Request. Leave of Absence Request.
Read more >QAP 2.0 - Quality System & Internal Audits - MTC Engineering
I. Purpose. To establish the quality loop within Industrial Welding & Engineering (IWE) and MTC Engineering (MTC) which applies to interactions between ...
Read more >[Authentication] Ensure the user never needs to fill out details twice ...
when an existing user is found by their email address, we show that address in the copy, but we don't pre-fill the text...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, my intention was that the error event is fired every time the
send request
button is pressed but the request does not go through. We could gather the errors (though i am not sure any error messages display, just fields light up in red) in a hasherrors
property.Looks great! I wasn’t able to reproduce the new user issue either on staging. Signing up and existing user flows seem good to me 👍
One tiny thought, maybe we could pre-fill the already entered email on this screen?