A couple of weeks ago, we had a real issue. We have a "newer" person doing payables for us, and she was doing a cheque run. She has done them before, but this time after she hit "Post", she realized she had missed a step, and so she hit the "Cancel" button.
This created a HUGE problem. We had to crawl through all of our payables, as what happened was that invoices that had not been chosen to be paid were now paid, and invoices that were supposed to be on the cheque run were not. Basically, the computer pretty much was randomly paying invoices whether or not they were supposed to be paid.
All because of the "Cancel" button. Now, I know one of the first things I was told when I started using Adagio was that: "DO NOT INTERRUPT A RUNNING PROCESS". That is HOW I was told, in BIG letters.
So my question is this: If it makes SUCH a mess when something is interrupted halfway, why have that button? I was told that if you realize, once something is posting, that there is going to be an error, let it run, and then check afterwards to see what errors you need to fix. Makes sense. So if I should NOT interrupt a running process, why is there a button that allows me to do that? Can Softrak disable the button, or should you rename it?
Perhaps calling it a "Doomsday" button would be better than a "Cancel" button. Or it could be something longer, if space permits, such as "You are going to be sorry if you use this button".
Anyway, would it be possible and wise as well, to NOT have the ability to cancel a running process??