Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0043770Retail ModulesWeb POSpublic2020-04-17 13:262020-04-21 10:24
Reporterplujan 
Assigned ToRetail 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0043770: [UX] Improve the message shown when an unexpected error is shown
DescriptionWhen an unexpected error is detected, there is a message about the situation. This message should be improved.
Suggestions about the content: It should say that because of the detection, information will not be lost but that a reload will be triggered. It should mention some relevant data to help 1st and 2nd level support to trace the log. The "sorry for the inconveniences" text is not required.
Steps To Reproduce(1) errors in the browser log:
[2020-04-17T01:29:58+0000] [SEVERE] web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js 212:14 "[checkBlocked][transaction]The order does not exists or is frozen. Wrong write in c_order avoided [undefined][VBS1001/0000069-1] - Caller: G.d.save (web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:51169:18) - callerInfo: \nObject.OB.Dal.save (web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:8088:22);\nG.d.save (web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:51169:18);\nsaveAndTriggerEvents (web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:51443:14);\nweb/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:51511:9;\nG.d.modelOfAnOrder.calculateTaxes (web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:77114:7); line: web/js/gen/53a2f6b3fbc1d0b997a68bf119bfc6c6.js:8470:26 (*)"
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng 01_29_59 FAILED_ CancelAndRplReturn.png (173,950) 2020-04-17 13:26
https://issues.openbravo.com/file_download.php?file_id=14337&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2020-04-17 13:26plujanNew Issue
2020-04-17 13:26plujanAssigned To => Retail
2020-04-17 13:26plujanFile Added: 01_29_59 FAILED_ CancelAndRplReturn.png
2020-04-17 13:26plujanOBNetwork customer => No
2020-04-17 13:26plujanTriggers an Emergency Pack => No
2020-04-21 10:24dbazNote Added: 0119289

Notes
(0119289)
dbaz   
2020-04-21 10:24   
Agree with "summary description" comments.

Ideally the "technical description" of the error should be in a collapsable area like this ( https://miro.medium.com/max/1132/0*NxLoRrrvV2eF63Vc [^]) to avoid 'stress' the user with data that he doesn't understand, but with this approach maybe this information is lost if the user decides to take an screenshot to send it to support team.