We have a patron who has explicitly instructed us not to save his credit card information in Tessitura after purchases.
I can't think of any way to automate this other than employing "post-it note technology" on the side of my computer monitor.
Is there any automated way to do this with this single account? Any suggestions for handling this with several users potentially selling into this account?
Just to add, I have run this utility against a list containing every patron apart from one constituent and it did work - the list took a very look time to generate though and I guess if you are going to be scheduling it you will need to have it regenerate the list every time to make sure you're excluding new patrons.
Siobhan
If you were feeling Very Brave, you could write a trigger on t_account_data (don't tell Chuck I said that) that purged any entry added for a customer with a specific attribute or constituency whenever it was added (perhaps a "Paranoid" attribute - could be useful for other situations?) - after checking how the purge script actually works to make sure that's viable, of course.
On the other hand, adding triggers to t_account_data migh invalidate the PABP certification, so that might be a bit Too Brave.
Ken