Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0045611 | Retail Modules | Web POS | public | 2020-12-17 07:52 | 2020-12-17 07:52 |
| Reporter | marvintm | ||||
| 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 | 0045611: master.LoyaltySubscription could be included inside main BusinessPartner request | ||||
| Description | Currently it seems there are the same number of requests to master.LoyaltySubscription class as master.BusinessPartner class, particularly when remote mode is used. The number of both requests is really large in a customer using remote mode. Maybe this could be optimised, by including the loyalty information inside the business partner request, thus saving half of the requests. | ||||
| Steps To Reproduce | Access the WebPOS in remote mode. Verify that when using business partner functionality, both separate BusinessPartner and LoyaltySubscription requests are done. This could be improved. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2020-12-17 07:52 | marvintm | New Issue | |||
| 2020-12-17 07:52 | marvintm | Assigned To | => Retail | ||
| 2020-12-17 07:52 | marvintm | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |