Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0043770 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Retail Modules] Web POS | minor | have not tried | 2020-04-17 13:26 | 2020-04-21 10:24 | |||||||
| Reporter | plujan | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | pi | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0043770: [UX] Improve the message shown when an unexpected error is shown | |||||||||||
| Description | When 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 (*)" | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  01_29_59 FAILED_ CancelAndRplReturn.png [^] (173,950 bytes) 2020-04-17 13:26
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0119289) dbaz (developer) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2020-04-17 13:26 | plujan | New Issue | |
| 2020-04-17 13:26 | plujan | Assigned To | => Retail |
| 2020-04-17 13:26 | plujan | File Added: 01_29_59 FAILED_ CancelAndRplReturn.png | |
| 2020-04-17 13:26 | plujan | Triggers an Emergency Pack | => No |
| 2020-04-21 10:24 | dbaz | Note Added: 0119289 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |