Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0052401 | POS2 | POS | public | 2023-05-09 15:27 | 2023-05-09 15:27 |
Reporter | migueldejuana | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | trivial | 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 | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0052401: Cash Management description is truncated to 60 but we could use 255 | ||||
Description | In https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/src/org/openbravo/retail/posterminal/ProcessCashMgmt.java#L75 [^] we are truncating description to 60. Then, we are saving that value in 3 places and in 2 different entities, OBPOSPaymentcashupEvents(length--> 60) and FIN_FinaccTransaction(length--> 255). We could save more length of the description in FIN_FinaccTransaction | ||||
Steps To Reproduce | Create a Cash management in POS2 and add the maximum length description | ||||
Proposed Solution | Do the corresponding substring in each use of description (3 places). We create one OBPOSPaymentcashupEvents(length--> 60) and two FIN_FinaccTransaction(length--> 255). | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2023-05-09 15:27 | migueldejuana | New Issue | |||
2023-05-09 15:27 | migueldejuana | Assigned To | => Retail | ||
2023-05-09 15:27 | migueldejuana | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |