Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0049166 | POS2 | Restaurants | public | 2022-04-28 15:54 | 2022-05-27 16:39 |
| Reporter | timothee_catteeuw | ||||
| Assigned To | mtaal | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | guilleaer | ||||
| OBNetwork customer | No | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0049166: JIRA 2926 - Something's wrong when calling api kitchen (AjouterNouvelleCommandeWI) | ||||
| Description | it remains something wrong in API kitchen about the field NumeroCommande when using AjouterNouvelleCommandeWIProduct line number in the order is always equals to 0 for example :if I have 2 products linked to pager as delivery control method , numeroCommande is the same 50069D601D0 and 50069D601D0instead of 50069D601D0 and 50069D601D1 This is correctly managed when cancelling, 2 calls are done on 2 different numeroCommande (ex : 50069D601D0 and 50069D601D1) | ||||
| Steps To Reproduce | Configure 2 products in order to link it to delivery control method “pager” Go to product window and select 2 products Go to product organization information for both In that tab, add a record for the restaurant you are used to base your test on, and link it to a pickup point and delivery control allowing to associate the product to “pager” (delivery control method = pager) 5. this configuration will call API kitchen (function = AjouterNouvelleCommandeWI) when you buy these products. For that : Go to WebPOS Select both products Go to payment and pay, 2 calls has done to API kitchen but with the same numeroCommande The Product line number in the order has to be managed starting from 0 (cf. the example previously described) | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2022-04-28 15:54 | timothee_catteeuw | New Issue | |||
| 2022-04-28 15:54 | timothee_catteeuw | Assigned To | => Retail | ||
| 2022-04-28 15:54 | timothee_catteeuw | OBNetwork customer | => No | ||
| 2022-04-28 15:54 | timothee_catteeuw | Triggers an Emergency Pack | => No | ||
| 2022-05-12 12:12 | mtaal | Assigned To | Retail => mtaal | ||
| 2022-05-13 01:47 | mtaal | Status | new => scheduled | ||
| 2022-05-13 01:47 | mtaal | Note Added: 0137245 | |||
| 2022-05-13 01:47 | mtaal | Status | scheduled => resolved | ||
| 2022-05-13 01:47 | mtaal | Resolution | open => fixed | ||
| 2022-05-27 16:39 | guilleaer | Review Assigned To | => guilleaer | ||
| 2022-05-27 16:39 | guilleaer | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||