The answer would be yes for both the let me explain in a bit more detail to give you a better perspective.
#1. The ability to suppress an email to the customer (regardless of order status)There are many times when we are manipulating an order for many reasons, where certain triggers execute, and emails are sent out, sometimes you need to manipulate an order let's say five times within a short timeframe. It doesn't look professional if a customer gets hit with five different emails in a short amount of time, and could actually trigger a spam filter protection on his end. Sometimes these changes are very small, and a customer does not need to be aware of it by getting an email every time.
Please note that the ability to suppress an email is only from the customer's point of view, if you have an entry for BB (blind copy), that email should always execute.It is imperative to us to always maintain a copy of the original order insert ("NEW") status for our records. Sometimes one of my people just makes a serious blunder, and having a copy of the original order helps tremendously.
Our old system had a checkbox in the backend, in the order header that read "No Email sent to Customer", this checkbox would reset itself every time you would reopen the order.
This checkbox would override any triggers set, and instead of the code looking for a not true value, it would check the status of the checkbox.
#2. The ability to save a NEW order with a different statusRight now because the coding, your "NEW" status and insert mode are interconnected, they are locked together. It just might be beneficial not only for myself, but the many others, if this would become
unlocked, and an admin in the backend processing a brand-new order (insert mode) would be able to change the status to something different before saving. This not only would print and get stamped on an email, but it also prevents the user from having to go back in and edit the newly created order just for the purpose of changing it status.
I know this may not seem like a lot, but when you're dealing with a lot of orders on a daily basis, it is time-consuming.
All the triggers which are set to "NEW" order would still execute, it's just that they're executing now based on the table being in insert mode, and not an order set to "NEW" status.
I hope this more detailed explanation helps.
-Ray
Edited by user Friday, March 18, 2022 12:37:21 PM(UTC)
| Reason: Not specified