Current Problem
A scenario for you! A query has been raised on an order, putting the order status to QUERYRASIED and because of the system setting, orders at this status cannot have a shipping label created. Magic. Stops us sending out order we don't want to / been told not to. However, we have seen it where orders at this status are manually marked as PICKED (or the status changed in another way) thereby moving the order away from QUERYRAISED. As the order is now not in a status where the creation of despatch labels is blocked (from the aforementioned system setting) the system allows a courier label to be created, allowing you to send the order that should not be sent. I've been informed that this improvement to the logic is a wish hence why I have created this. Surely if there is an active query on an order, you should not be allowed to create a shipment label as you will send order in error. Following this through, instead of the logic checking the ORDERSTATUS column of the Orders table to look for a value of '13' for QUERYRASIED (pretty sure this is how it has to be working to allow the above to occur) the logic should look at the QUERYSTATUSID in the OrderQueries table and if there is a reference to the relevant ORDERID in this table and the most recent value is either '1' (for NEW) or '2' (for OPEN) then the shipment should not be created. |
|
Idea to resolve Problem | Enhance the logic to check for active queries rather than rely on order status |