Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0050870 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Retail Modules] Retail API | trivial | always | 2022-11-14 09:37 | 2022-12-15 14:40 | |||||||
| Reporter | jrakotobe | View Status | public | |||||||||
| Assigned To | Triage Platform Conn | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0050870: RETAPCO_OrderCreation : having the c_order.c_order_id AND c_order.documentno in request line and header | |||||||||||
| Description | Today in EDL request, when in error or in success, it’s complicated to know which ticket has been pushed correctly or not We have the technical ID of the sales in the request line, but it is not useable without an access to the database. So when we need to re-process a specific ticket, we cannot determine which one it was. The goal is to have in request line, in addition to order ID the documentNo associated. These are the 2 data we should have at least in request line : c_order.c_order_id and the c_order.documentno | |||||||||||
| Steps To Reproduce | Normal uisage of webhook ticket : when a ticket is pushed to external system : GOTO EDL Request > RETAPCO_OrderCreation > Sub-tab request line We only have the order ID information, and this information is not exploitable without access to database | |||||||||||
| Proposed Solution | Having in request line and header : c_order.c_order_id and the c_order.documentno | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-11-14 09:37 | jrakotobe | New Issue | |
| 2022-11-14 09:37 | jrakotobe | Assigned To | => Triage Platform Conn |
| 2022-11-14 09:37 | jrakotobe | Triggers an Emergency Pack | => No |
| 2022-12-15 14:40 | rafaroda | Summary | RETAPCO_OrderCreation : having the c_order.c_order_id AND c_order.documentno in request line => RETAPCO_OrderCreation : having the c_order.c_order_id AND c_order.documentno in request line and header |
| 2022-12-15 14:40 | rafaroda | Proposed Solution updated | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |