Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0047905 | Retail Modules | Web POS | public | 2021-10-21 16:50 | 2021-10-21 16:51 |
Reporter | rafaroda | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | No | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0047905: WebPOS is allowing to generate JSON Messages bigger than the column that is allowed in C_IMPORT_ENTRY | ||||
Description | WebPOS is allowing to generate JSON Messages bigger than the column that is allowed in C_IMPORT_ENTRY | ||||
Steps To Reproduce | * Do a very large ticket with several payments on it and reach > 1.000.000 chars * You are able to pay for it, but then the JSON Message is not enterying properly in C_IMPORT_ENTRY table | ||||
Proposed Solution | Inform in POS that the JSON beaing geenrated is becoming too big: When? * If we do in Done / Fionaliser it is too late, some payments have been added, not user friendly and have to go back deleting payments and some products * If we do in Pay Total, could be the best way * Or if we do in AddLines | ||||
Additional Information | |||||
Tags | NOR | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2021-10-21 16:50 | rafaroda | New Issue | |||
2021-10-21 16:50 | rafaroda | Assigned To | => Retail | ||
2021-10-21 16:50 | rafaroda | OBNetwork customer | => No | ||
2021-10-21 16:50 | rafaroda | Triggers an Emergency Pack | => No | ||
2021-10-21 16:50 | rafaroda | Tag Attached: NOR |
There are no notes attached to this issue. |