A question has arisen regarding expired credit cards and whether they can be inactivated so that they do not show up in the list when taking orders; the order taker finds it inconvenient. Unfortunately, since the particular card she was trying to inactivate had already expired, the system wouldn't let her inactivate it, telling her it was an invalid entry.
Is it possible to just inactivate these expired cards on the back-end via some quick little script? I'm not sure of the implications on the system at large. Or is there instead some way to keep them from showing up in the list?
Thoughts? Comments?
A question has arisen regarding expired credit cards and whether they can be inactivated so that they do not show up in the list when taking orders; the order taker finds it inconvenient. Unfortunately, since the particular card she was trying to inactivate had already expired, the system wouldn't let her inactivate it, telling her it was an invalid entry. Is it possible to just inactivate these expired cards on the back-end via some quick little script? I'm not sure of the implications on the system at large. Or is there instead some way to keep them from showing up in the list? Thoughts? Comments? This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Reiterating what Tom said—test it a lot—but it will do exactly what you’re after! It is called the credit card tokenization and deletion utility.
Hi all,
Related to Tom and Sheila's point aboot testing... In our own testing, we discovered a defect with the credit card tokenization and deletion utility that could cause it to delete a card that was just recently used despite the criteria used in the report parameters.
The cause: The utility is designed to check for activity, such as recent payments, by customer_no and act_id - not just act_id. However, there is nothing in the database that enforces that rule. For example, the database allows a customer_no and act_id combination to be used in t_payment while a different customer_no might be used in t_account_data for that same act_id.
This is generally a rare occurrence; however, we have recent examples of this in our database. Tessitura's current plan is to fix the issue allowing that scenario to occur in the first place (see defect 70845). While that is good, my concern is that there is nothing stopping some future change from reintroducing this issue since the customer_no/act_id relationship is not enforced in the database.
We are in the process of writing our own custom utility based on the credit card tokenization and deletion utility that resolves this issue, as we need to be able to purge old data without inadvertently deleting a recently used card.
Anyway, if you are considering the utility - test, test, test - and check for customer_no/act_id mismatches in your database.
Thanks,David