Openbravo Issue Tracking System - POS2 | ||||||||||||||||||||||||||
View Issue Details | ||||||||||||||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||||||||||||||||
0056345 | POS2 | POS | public | 2024-09-03 08:10 | 2024-09-05 15:39 | |||||||||||||||||||||
Reporter | migueldejuana | |||||||||||||||||||||||||
Assigned To | sreehari | |||||||||||||||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | |||||||||||||||||||||
Status | scheduled | 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 | 0056345: External Orders API | |||||||||||||||||||||||||
Description | When building the request for External Orders we do not define a proper request data in some tipe of actions. SEARCH and LOAD actions send a request with a wrong structure having data inside data: data: { data: { ... } } We should only have one data instead of 2 nested datas. We can take COMMIT action as example. | |||||||||||||||||||||||||
Steps To Reproduce | - In Organization check "Enable External Orders" - In External System window, create a new onw with Protocol "Javascript - Frontend" and set JS Class Name to "OB.EXOTEST.ExternalOrdersSimulator" - Create an Event Subscription of type "External Event Order" and select created External System - Login in POS2 and got to option menu External Orders - In the filter write "00" - SEARCH action is launched and we can see in the console the request sent with data nested - Click on one row and - LOAD action is launched and we can see in the console the request sent with data nested - Complete the ticket and - COMMIT action is launched and we can see in the console the request sent WITHOUT data nested | |||||||||||||||||||||||||
Proposed Solution | We have to send the request without nested data and change External Simulator to adapt it to the new structure | |||||||||||||||||||||||||
Additional Information | ||||||||||||||||||||||||||
Tags | No tags attached. | |||||||||||||||||||||||||
Relationships |
| |||||||||||||||||||||||||
Attached Files | ||||||||||||||||||||||||||
Issue History | ||||||||||||||||||||||||||
Date Modified | Username | Field | Change | |||||||||||||||||||||||
2024-09-03 08:10 | migueldejuana | New Issue | ||||||||||||||||||||||||
2024-09-03 08:10 | migueldejuana | Assigned To | => Retail | |||||||||||||||||||||||
2024-09-03 08:10 | migueldejuana | Triggers an Emergency Pack | => No | |||||||||||||||||||||||
2024-09-03 08:13 | sreehari | Assigned To | Retail => sreehari | |||||||||||||||||||||||
2024-09-04 08:09 | sreehari | Status | new => scheduled | |||||||||||||||||||||||
2024-09-05 05:50 | hgbot | Note Added: 0168754 | ||||||||||||||||||||||||
2024-09-05 08:24 | hgbot | Note Added: 0168755 | ||||||||||||||||||||||||
2024-09-05 08:24 | hgbot | Resolution | open => fixed | |||||||||||||||||||||||
2024-09-05 08:24 | hgbot | Status | scheduled => closed | |||||||||||||||||||||||
2024-09-05 08:24 | hgbot | Note Added: 0168756 | ||||||||||||||||||||||||
2024-09-05 15:31 | sreehari | Status | closed => new | |||||||||||||||||||||||
2024-09-05 15:31 | sreehari | Resolution | fixed => open | |||||||||||||||||||||||
2024-09-05 15:39 | sreehari | Status | new => scheduled | |||||||||||||||||||||||
2024-10-08 09:22 | sreehari | Relationship added | causes 0056683 |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|