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
Hey, one more thing -- upon inspection, I actually have an lwp_CLR_AlterTicketExpiration proc in my db.
Looking back at my archives I think these CLR procs are all part of a "TNEWSqlBridge.dll", which I believe was installed in tandem with a TNEW customization we had consulting build for us.
If memory serves, this TNEWSqlBridge component is not proactively supported -- that is, the installation files are not published and updated code is not distributed unless there's a problem with a consulting-originated customization. So perhaps your set of CLR procs is an older iteration than mine, and that's why they don't include AlterTicketExpiration.
I for one find this very unsatisfying -- if this code isn't going to be actively supported, then it should be open-sourced so people like you can use it to solve problems without relying on awkward hacks or duplicating effort by reimplementing something that already exists. I have no idea what would happen if you asked on TASK for these installation files not in connection with a formal consulting arrangement. Didn't we hear something about a TNEW web dev toolkit at TLCC, or was that a figment of my imagination?
After the virtual coffee conference call today I dug back in to the notion of creating my own CLR bridge assembly and subsequently my own CLR procedures. Through much trial and I did actually get it to work. It does require a little bit of C# knowledge (or possibly VB), but not nearly as much as you'd think. Unfortunately, there is no way that I found to replicate all the API methods en mass - each method has to get individually wrapped in a C# function - I'm guessing this is why the CLR procedures that the consulting team has made are somewhat limited. At any rate - for anyone who stumbles across this forum post in the future - it can be done.