Currently this module is modeled to act exactly the same with the rest of a stock Zen Cart installation works in the administrative interface. Basically a list of items (customers in this case) are listed to the left. When an item in the list is selected, buttons used to interact with the selected item are displayed to the right. This was done to ensure anyone familiar with the Zen Cart administrative interface can quickly get started using this module.
Are you proposing an extra "confirmation" step should be added? What business purpose does adding such a "confirmation" step provide? I'm not unwilling to listen, but there are some very good reasons why no such "confirmation" step exists.
Here are just a few of the reasons why no "confirmation" step exists:
- Creating a new order does not alter existing database entries and can be easily undone. If an order is accidentally created (or the wrong customer was selected), one can simply delete the order. In most UIs actions which require minimal effort to undo do not include a "confirmation" step.
- The process of creating a new order is quick (typically less than a half a second). In most UIs actions which occur in a short period of time typically do not include a "confirmation" step.
- Every additional step requiring user interaction causes the process to take longer and be less efficient. In business time is money. By not including a "confirmation" step, time is saved in the process of creating an order.
- Adding a "confirmation" step to a process for an event which is not destructive typically leads to end user apathy in regards to the "confirmation" step. Basically the more times one see's a "confirmation" request, the more likely one is to ignore future "confirmation" steps (and thus defeats the purpose of having a "confirmation" step).



Reply With Quote
