-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer order rejection #903
Comments
Discussed following points:
|
…tch rejection reasons and to reject order item(hotwax#903)
…c when user reject order items(hotwax#903)
@dt2patel Sir, are we going to create a separate parking for TO rejected items, similar to what we have created for bopis rejected items? |
Rejected item parking |
As discussed, we need to rethink on the TO rejection flow due to the NetSuite specific case, so moving this ticket to Hold. |
Added notes: Items of a transfer order can only be rejected when no fulfillments have been issued against that TO. Partial rejections are also not allowed for TOs, only entire rejections. Because the entire order will be rejected, there is no need for the rejected order tab. |
Removed logic to display rejected items and the corresponding actions and services Implemented support to reject entire order at once, only if any of the order items are not shipped
Implemented: support to reject transfer order items(#903)
TO rejection is working as expected for the above points. Issue found with the "Not in Stock" rejection reason for Admin Users:
NOTE:
https://docs.google.com/spreadsheets/d/1b1QklVS-8Er6TlpLF5vC8W7ylp4dUjj3U-oubyP5bQ8/edit?usp=sharing |
What is the motivation for adding/enhancing this feature?
If a TO item has not been shipped yet, allow the item to be rejected:

Once a reason is selected, the rejection selection can be cleared by clicking the clear button on the chip:

After selecting items to reject, the user will submit their choices from this button at the bottom. This button will only show if there is at least one item selected to be rejected:
The text was updated successfully, but these errors were encountered: