Open sahil-ondc opened 8 months ago
Other Flows
on_select
- available count can't be greater than maximum count for item id: STO-ITEM-2023-00007-500 Gms:Manikonda - S, STO-ITEM-2023-00017-500 Gms:Manikonda - S
Available count of 99 means the stock is available and maximum count of 33 means maximum 33 qty can be ordered in one order, then available count will be greater only. Please confirm if I am missing anything here ?
on_init
- gps coordinates in fulfillments[0].end.location mismatch in /select & /on_init
In init request the buyer app has changed the fulfillments[0].end.location from select API, we as a seller app sent the GPS as received in init request
on_confirm
- /message/order/quote must have required property 'ttl'
- /message/order/tags/0/list/0 must be object
- fulfillments[0].end.location gps is not matching with gps in /select
@sahil-ondc, @bluecypher - Please check the reverts for the above and confirm..
@harshpwctech
@bluecypher, @sahil-ondc, @BLR-0118
Please help in reviewing the logs...I have submitted the logs for flow 1 and flow 3 through Ref Buyer App. The other logs were tested through Mappls, since in their pre-prod instance they are facing some issues and hence we submitted the revised logs from Ref Buyer App.
Further the issue raised for on_search:
Here the area_code , i.e. 500089 belongs to Hyderabad which have a std code of 040, further the seller is servicing to std code 040, However as an edge case the official std code of 500089 isn't 040, hence we have enabled the seller with std code of 040 as well.
@harshpwctech
@BLR-0118, @sandeepshahi, @sahil-ondc, @NishthaMonga - Please help in clearing the logs as the revised logs are submitted in latest PR. And help in addressing the below queries.
on_search_full_catalog_refresh
- STD code does not match with correct area_code on /on_search
As mentioned above, the area_code, i.e. 500089 belongs to Hyderabad which have a std code of 040, further the seller is servicing to the buyer apps for std code 040, However as an edge case the official std code of 500089 isn't 040, hence we have enabled the seller with std code of 040 as well.
Flow 4
on_cancel
- order.created_at timestamp should match context.timestamp
The order.created_at timestamp wouldn't change and the same is provided by the buyer app during confirm API. Further order.updated_at should be less than or equal to context.timestamp
@harshpwctech
Flow 1 is an edge case and what's being done is ok as long as the same store is not sent multiple times under different cities; @harshpwctech @NishthaMonga
@BLR-0118, @sandeepshahi, @sahil-ondc, @NishthaMonga - Please help in clearing the logs as the revised logs are submitted in latest PR.
@harshpwctech
Flow 1
on_search_full_catalog_refresh
on_search_inc
Flow 3
on_select (out-of-stock)
error.message in the response should have the list of corresponding item ids referenced in stringified object notation, e.g. if items "I1" is out of stock, error.message would be encoded as: "[{\"item_id\":\"I1\",\"error\":\"40002\"}]"
Other Flows
on_select
on_init
on_confirm
on_status
@harshpwctech