/
Pusher implementation for bulk orders Release

Pusher implementation for bulk orders Release

Owned by Saurav Kumar Ram
Last updated: May 02, 2023
3 min read

Multiple orders can be marked unhold in these two ways ;-

  1. By selecting many orders in bulk through the top check box

  2. By selecting many orders one by one the side check box

In this document, we will be mentioning the approach taken to release orders in bulk.

Steps taken :-

By selecting many orders in bulk through the top check box

  1. When the user selects many orders in bulk through the top check box, we get a request body from frontend mentioned below. It contains the algolia filters of the orders released.

    { "data" : "(orderReceivedOn>=1673289000000)AND(orderReceivedOn<=1675880999999)" }

  2. On the basis of this algolia filters, extract the externalShipmentIds from Algolia and store them in a list<String>

  3. If response from algolia is null or empty then throw exception and return the below response to the frontend else move to step 4

    { "message" : "Something went wrong. Please try again after sometime."" }

  4. Pass the list<String> externalShipmentIds through a taskqueue

    POST API path - /_ah/api/esb/v1/mark-unhold/bulk/listener taskqueuname - orders-mark-unhold-queue

  5. Return the response to the frontend

    { "message" : "Releasing your orders" }

  6. In the bulk listener API, using this list of exetrnalShipmentId, fetch the details from wms DB required to call unhold API.

    1. note the following condition : -

      1. Details of only those orders will be fetched whose esb shipping is true and riskScore is high

        SELECT channels.`externalChannelID`, orders.`customerOrderNumber`, shipments.`externalShipmentID`, accounts.`account_slug` AS accountSlug, order_items.`lineItemSequenceNumber`, order_items.`itemId`, order_items.`quantity`, order_items.`orderItemId`, order_items.`id` AS orderItemId_PK, shipments.`trackingID`, shipment_status_logs.`remarks` AS shipmentStatusRemarks FROM order_items LEFT JOIN orders ON orders.id = order_items.order_id LEFT JOIN shipments ON shipments.id = order_items.shipment_id LEFT JOIN channels ON orders.`channel_id` = channels.`id` LEFT JOIN accounts ON channels.account_id = accounts.id LEFT JOIN shipment_status_logs ON shipments.id = shipment_status_logs.shipment_id WHERE shipments.`externalShipmentID` IN (:externalShipmentIdList) AND order_items.onHold = '1' AND orders.thirdPartyShipping = '0' AND orders.riskScore = 'high'

  7. define variables for releasedOrderCount, failedOrderCount, releasedOrders

  8. If the result from query is null or empty then return an empty map else prepare a shipmentMap on the basis of externalShipmentIds. e.g., Map<String, List<OnholdOrderItemDetailsDto>> shipmentwiseMap where key = externalShipmentId and value = List of dto

    { "releasedOrders": [ ], "failedOrders" : ["internalTest13-5865-8578","internalTest16-5865-8579"], "releasedOrderCount" : 0, "failedOrderCount" : 2 }

  9. Iterate over each shipmentwiseMap key and

    1. check if pincode is not serviceable and the tracking id is null or empty.

      1. To check if pincode is serviceable => shipment_status_logs.remarks fetched through above query should not be equal to “Pincode not serviceable“.

      2. Note - If pincode is not serviceable and tracking id does not exist then we don’t have to mark the orders unhold. add the externalShipmentIds in failedOrders list.

    2. pincode is not serviceable and the tracking id is null or empty then continue else move to step c

    3. If pincode is serviceable or tracking id exists, then call unhold API for that externalShipmentId. Also collect the order_items (primary keys) of that order to sync in algolia.

      POST API - /orders/unhold curl --location 'https://eshopbox-wms-api-dot-eshopbox-wms-staging.el.r.appspot.com/api/orders/unhold' \ --header 'proxyHost: tab' \ --header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6IlJVVXdSREZCUVRSRFFqQkdORFUxTVVZeE16ZEdPRFJHTnpORk5EaEJSVEU0TVVORk5qVTJOdyJ9.eyJodHRwczovL2FwcERhdGEiOnsiYXBwQ2xpZW50SWQiOiJiN2UzMDM0N2M5ODYxMGQwMjBlYTg0ZWY0OTRjYTY3MyJ9LCJodHRwczovL3VzZXJEZXRhaWxzIjp7ImlkIjoxMDEyLCJ1c2VyVHlwZSI6ImRlZmF1bHQiLCJlbWFpbCI6ImFwcHVzZXI5OEBlc2hvcGJveC5jb20ifSwiaHR0cHM6Ly9hY2NvdW50cyI6W10sImh0dHBzOi8vd2FyZWhvdXNlV29ya3NwYWNlcyI6W10sImh0dHBzOi8vd2FyZWhvdXNlcyI6W10sImh0dHBzOi8vcGFydG5lcnMiOltdLCJpc3MiOiJodHRwczovL2VzaG9wYm94LXBheW1lbnQtcmVjby5hdXRoMC5jb20vIiwic3ViIjoiYXV0aDB8NWZkOWJhZTQ0Mjg0M2EwMDZlMzRhY2ZiIiwiYXVkIjoiaHR0cHM6Ly9lc2hvcGJveC1wb3J0YWwtZGV2LmFwcHNwb3QuY29tIiwiaWF0IjoxNjc1NzU0MjcxLCJleHAiOjE2NzgzNDYyNzEsImF6cCI6Inc4dllYa2ZMSWZmOFl2Mmo0TzNUOUplYWoxUzNxOHJlIiwiZ3R5IjoicGFzc3dvcmQifQ.W_1Gas11K-QhLyN4Quv5yMEE2UtC9-FiyhczY1qBjwwURn5EOBXTuOUqt7OcTxl6tH-x41VLKNZXVUPr1KnaHnwvHpjpyyOFez74cSzA2x5_NFrjb7hXtlktHhfDyZC0v646N76HDmhusxf7ujKi2PFQ0N1J4zZg-G75auvaLcicoWSlEQmcjK8usAWQ5-XjGwiKdULm4GNXa3brGyJ6exjDcaK2DSzitbfW0WmiMuxR6wtvv2H5dHCBB0in1s4PNlE59ze7Xv6WUms7IifNL8JXUssTlZ9aiLpRGCnMP6DhcJ-o3v8JIR9p0ni73YCMzEN9X9F4DDT3T3MuZd55Bw' \ --header 'Content-Type: application/json' \ --data '{ "externalChannelId": "CH5876", "externalShipmentId": "24345252342-5876-8785", "customerOrderNumber": "24345252342", "items": [ { "itemId": "46233433932076", "quantity": 1, "lineItemSequenceNumber": "13678999470380", "orderItemId": "24345252342-23922395" }, { "itemId": "46384626237740", "quantity": 1, "lineItemSequenceNumber": "13678999470380", "orderItemId": "24345252342-23922396" } ] }'

    4. Pass the order item (primary keys) collected in algolia sync object preparation function

    5. Based on the response returned from algolia sync object preparation function, prepare the response as shown below

      { "releasedOrders": [ { "currentOrderStatus": "New", "orderStatus": "New", "shipmentNumber": "internalTest11-5865-8574" }, { "currentOrderStatus": "New", "orderStatus": "New", "shipmentNumber": "internalTest12-5865-8575" } ] }

       

  10. sync all the successfully released order item ids in Algolia

  11. prepare a response body for pusher with message name - "ONHOLD RELEASED ORDERS"

    { "releasedOrders": [ { "currentOrderStatus": "New", "orderStatus": "New", "shipmentNumber": "internalTest11-5865-8574" }, { "currentOrderStatus": "New", "orderStatus": "New", "shipmentNumber": "internalTest12-5865-8575" } ], "failedOrders" : ["internalTest13-5865-8578","internalTest16-5865-8579"], "releasedOrderCount" : 2, "failedOrderCount" : 2 }

By selecting many orders one by one the side check box

  1. When the user selects many orders one by one the side check box, we get a request body from frontend mentioned below. It contains the list externalShipmentIds of the orders released.

    { "externalShipmentIds":["Test-order-7-5865-6206","Test-order-8-1175-0089","Test-9-776"] }

  2. if the list of externalShipmentIds from the request body is null or empty, then return the following response to the front end else move to step 3.

    { "message" : "Something went wrong. Please try again after sometime."" }

  3. Repeat all the steps from step 4 to step 9 mentioned in By selecting many orders in bulk through the top check box (mentioned above)

Add label

Related content