Has anyone attempted to use the AlterTicketExpiration method from within the TNEW purchase path?
I'd like to add a couple of minutes to the ticket expiration timer on a session when a customer logs in to their account. It seems like I could do this using the Login validation point in the LWP_VALIDATE_CART procedure, but I can't seem to figure out how to call an API method. Their are some existing CLR procedures that appear to make API calls, but not one for the AlterTicketExpiration.
Has anyone been able to make up their own CLR procedures for TNEW? If so would you be willing to share the steps? We are also a RAMP client.
Thanks,
Bill WaughStarlight Theatre
Not to shoot down this idea too quickly, but are you sure the Login validation point in LWP_VALIDATE_CART actually fires? I've been refactoring our gigantic procedure over the past few days, and realized that the 1-10 validation points don't completely match up with the Item Types available in LTR_TNEW_VALIDATE_CART. It's actually 9/10 -- there's no Login trigger available in that table. (I think it's Gift Certificate that's missing from the procedure.)
That said, I'd be interested in learning if there's a way to extend the session through some other means. I always wondered if it was possible to reset the countdown timer whenever something new was added to the cart.
Additionally (and I was asking this in the TNEW forums but didn't get any response) -- does anyone know where the TNEW CLR procedures are documented? I've always been very unclear about how they are being versioned and who supports them.
I know it's possible to develop your own CLR procedures, but I believe the process involves writing .NET code in Visual Studio (or technically any language that can target the CLR environment). It would be great to have a t-cast or session on this, but I don't think there's been one.
Finally, it's also technically possible to target an HTTP API from within TSQL code by using OLE automation procedures and the msxml2.serverXMLHTTP object. If you use Mail2 there's an example in one of their db procedures, and just today I was experimenting with using these to target Slack channels with database alerts. Pretty crazy, though.
Tiny followup after marinating in LWP_VALIDATE_CART a little more -- it looks like the post-login validation point is something that you are intended to engineer by replacing all of the login links on your site with a ReturnUrl parameter that targets a precart validation point. So, possible, but tricky.