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?
This is kind of silly and scary but there is the purge credit card account data report (if you have the rights to it) in the data management folder that you can runwhich seems to have the ability to be scheduled.It doesn't have a "include" list sadly but I guess in theory you could "exclude" everyone except that patron.Obviously this is something that you would want to take great caution with if you decide to attempt.Hopefully there are better solutions out there.
Good luck!
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
As a work around, have you considered a custom element in the contitent header for a special note type. This would give you a way to put the "post it" on the account instead of your monitor. Then whoever ran a transaction for that constituent would see a note telling them to delete the credit card after processing. (The "Post It" note type wouldn't have to be limited this specific senario and could be used for any notes you wanted an end user to see for processing.)
Another option may be to add a T_DEFAULT setting for CC_STORE_ACCOUNT and set it to ‘No’. This will prevent credit card numbers from being automatically saved when a payment is made. It will also prevent credit card numbers from being added to a constituent account via the Customer Accounts window. You are still able to add credit card accounts to a customer via the Constituent Account – Transactions – Credit Cards area. It is true that employing this method would cause no credit card number to be automatically saved, but you can still add numbers as needed (for billing purposes, for instance) via the constituent’s record.