Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0050600
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Retail APImajorhave not tried2022-10-20 14:512023-07-11 10:23
Reporterazzeddine_meftohView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionduplicateFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0050600: Multiple event OBDOAPI_UpdateDOQuantities for one DO reception confirmed in AWO

Descriptionwhen confirming the reception of a DO in AWO the event OBDOAPI_UpdateDOQuantities is triggered for each line.
we should send only one event when confirming the reception.
Steps To Reproducewhen confirming the reception of a DO in AWO the event OBDOAPI_UpdateDOQuantities is triggered for each line.
we should send only one event when confirming the reception.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of design defect 0052774 closedTriage Omni WMS [RM-7065] API event" Update Distribution Order quantities through goods movement" is sending the DO as many times as #lines 

-  Notes
(0142356)
azzeddine_meftoh (manager)
2022-10-20 14:53

 for info we get as many event as lines present in the DO
(0144010)
vmromanos (developer)
2022-11-22 14:39

 Design defect:

Each time we confirm a distribution order reception we are individually confirming each of the tasks associated to the lines.

Each task confirmation updates the DO's quantities, so an OBDOAPI_UpdateDOQuantities event is triggered for each task/line.

When the transaction ends, the events are added to the queue to be launched afterwards (in an asynchronous way). In the moment that they are launched, the system generates the Distribution Order JSON with the information found in the Database at this moment, so the user is receiving the same json information as many times as tasks where confirmed behind the scenes.


If you don't want to have this behavior, you can subscribe instead to the OBDOAPI_UpdateDOStatus which is sent just one time when the DO is closed.
(0152311)
mtaal (manager)
2023-07-11 10:23

 The observed behavior is as expected, a new event is introduced to allow DO header level events. See duplicate issue.

- Issue History
Date Modified Username Field Change
2022-10-20 14:51 azzeddine_meftoh New Issue
2022-10-20 14:51 azzeddine_meftoh Assigned To => Triage Platform Conn
2022-10-20 14:51 azzeddine_meftoh Triggers an Emergency Pack => No
2022-10-20 14:53 azzeddine_meftoh Note Added: 0142356
2022-10-20 15:05 vmromanos Assigned To Triage Platform Conn => AtulOpenbravo
2022-11-22 11:49 vmromanos Assigned To AtulOpenbravo => vmromanos
2022-11-22 11:49 vmromanos Status new => acknowledged
2022-11-22 14:39 vmromanos Note Added: 0144010
2022-11-22 14:39 vmromanos Type defect => design defect
2023-06-26 12:07 mtaal Relationship added has duplicate 0052774
2023-07-11 10:22 mtaal Assigned To vmromanos => mtaal
2023-07-11 10:22 mtaal Status acknowledged => scheduled
2023-07-11 10:23 mtaal Relationship replaced duplicate of 0052774
2023-07-11 10:23 mtaal Note Added: 0152311
2023-07-11 10:23 mtaal Status scheduled => closed
2023-07-11 10:23 mtaal Resolution open => duplicate

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker