Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0045234 | Retail Modules | Web POS | public | 2020-10-16 09:14 | 2020-10-16 09:14 |
Reporter | aferraz | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | major | Reproducibility | have not tried |
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 | 0045234: TicketUtils.newTicket fails when running from new POS as it reads OB.Constants | ||||
Description | TicketUtils.newTicket fails when running from new POS as it reads OB.Constants | ||||
Steps To Reproduce | Check TicketUtils.newTicket is using payload.constants.fieldSeparator and payload.constants.identifierSuffix. payload.constants is loaded in OB.UTIL.TicketUtils.addTicketCreationDataToPayload as follows: newPayload.constants = { fieldSeparator: OB.Constants.FIELDSEPARATOR, identifierSuffix: OB.Constants.IDENTIFIER }; | ||||
Proposed Solution | Two alternatives: a) Create OB.App.Constants wrapper for OB.Constants, same as we did with OB.App.Security, and use this wrapper in TicketUtils.newTicket. b) Define both constants inside TicketUtils.newTicket. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2020-10-16 09:14 | aferraz | New Issue | |||
2020-10-16 09:14 | aferraz | Assigned To | => Retail | ||
2020-10-16 09:14 | aferraz | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |