I'm working on an upgrade from MM4.13 to MM5.5.
Our current store has an application guide that allows the customer to choose products that fit their specific widget. We store the information about the customer's widget in a table that keeps the relation to the product in the basket table. We use this information to double check our application guide for errors as well as to show the customer that they got what they ordered.
It was easy in MM4.13. All I had to do was hack db.mv to add or delete records from our table when the customer added or deleted items from the cart.
I'm considering my options now that we're going compiled. I was going to use triggers on the BASK page to call external functions with toolkit, but then I decided to write a system extension module. The module will work fine except for one thing. How can I delete records from our associated table when the basket has timed out and is deleted by the system?
Clear as mud?
Thanks,
Todd
Our current store has an application guide that allows the customer to choose products that fit their specific widget. We store the information about the customer's widget in a table that keeps the relation to the product in the basket table. We use this information to double check our application guide for errors as well as to show the customer that they got what they ordered.
It was easy in MM4.13. All I had to do was hack db.mv to add or delete records from our table when the customer added or deleted items from the cart.
I'm considering my options now that we're going compiled. I was going to use triggers on the BASK page to call external functions with toolkit, but then I decided to write a system extension module. The module will work fine except for one thing. How can I delete records from our associated table when the basket has timed out and is deleted by the system?
Clear as mud?
Thanks,
Todd
Comment