Has anyone created criteria for List Manager that will allow you to exclude someone who has used a pricing rule from getting the pricing rule again?
Michele
That's a great idea, although timing is going to be tricky:
1) You'll need a mechanism for updating the list: it's not going to regenerate until some process operates on it.
2) When you come up with that mechanism, you'll need to be sure that you do not include people who have that price rule on one of their sub line items but have not yet completed their order.
Since list regeneration can be expensive, I'd be tempted to start with a manual list, and then add a stored procedure to LP_CUSTOMER_RANK that determines if a pricing rule has been used by that customer, and if so, add them. There you can pare down your queries to only look for a specific customer and also time limit the searches over orders (LP_CUSTOMER_RANK will fire, among other times, at the completion of an order, so you can limit to orders last updated within a few minutes) to minimize the process time.
Definitely good to keep in mind. We are getting ready to go LIVE with our TNEW website soon, and, while we still have some time before most of our single tickets go on sale, all of this has been in my mind as I try to figure out the best way to implement all of the pricing rules and events we will need to have in place.
I already had the idea of using a list in the back of my mind, but it was not really shaped, and the idea of just having it live as a manually created list that is updated by a procedure sure sounds nice.
Thanks, and keep the ideas coming!