Receive shipment enhancement #402
Assignees
Labels
Comments
1 task
ravilodhi
moved this from ⏸️ Dev complete
to 👀 In review
in Digital Experience Platform
ravilodhi
added a commit
that referenced
this issue
Oct 22, 2024
… items instead of doing multiple calls for creating/adding shipment and items. Also used the common flow for shipment, return and po to import the json file and processing the item receiving at backend. (#402)
|
This is dependant on OMS release 5.18.0. |
ravilodhi
added a commit
that referenced
this issue
Nov 18, 2024
Improved: Receive shipment enhancement (#402).
ravilodhi
moved this from 👀 In review
to ⏸️ Dev complete
in Digital Experience Platform
|
Verified and working fine in release v2.29.0. Hence, closing this issue. |
github-project-automation
bot
moved this from ⚒️ In QA
to ✅ Done
in Digital Experience Platform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the motivation for adding/enhancing this feature?
Currently, the receive shipment functionality processes items one by one, making multiple requests equal to the number of items in the shipment. This approach is not scalable. Uploading a JSON of the items to be received and letting the backend logic handle the processing will make it more scalable.
What are the acceptance criteria?
Shipment items should be uploaded in a single API call and processed on the backend synchronously using the RECEIVE_SHIP_ITEMS data manager configuration. If any item fails, the shipment should not be marked as 'Received,' and the user should still be able to attempt receiving those items. No item should be successfully received more than once.
Can you complete this feature request by yourself?
Additional information
The text was updated successfully, but these errors were encountered: