Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0048644 | Retail Modules | Web POS | public | 2022-02-21 14:15 | 2022-02-21 14:15 |
Reporter | martinsdan | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | trivial | Reproducibility | sometimes |
Status | new | Resolution | open | ||
Platform | OS | 30 | OS Version | Ubuntu 18.04.1 LTS | |
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 | 0048644: Random document type when Issuing Sales Order | ||||
Description | The "Document Type for Shipment" configuration on the POS order is not used when using the Issue Sales Order on the touchpoint. That configuration should be used and only if it doesn't exist the current approach should be used. There is a workaround that is setting the desired document type as default. | ||||
Steps To Reproduce | As it is random depending on IDs, let's see the code. GoodsShipmentGenerator.createNewGoodsShipment uses the FIN_Utility.getDocumentType to get the doc type instead of using the configuration in the Order doc type. This can be changed. | ||||
Proposed Solution | Change the Shipment Generator to check if the configuration exists in the POS Order and use it. Otherwise keep the existing logic. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2022-02-21 14:15 | martinsdan | New Issue | |||
2022-02-21 14:15 | martinsdan | Assigned To | => Retail | ||
2022-02-21 14:15 | martinsdan | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |