Hi all,
I'm in the process of scoping out what we need to let our web developers know about BEFORE we move to v12. Currently, our website is set up with a "Forgot Your Password" button that sends the actual email in a reminder, which I know needs to be changed to sending a reset link instead.
So my question is:
- Does anybody have any documentation or any guidelines on how the web guys should set up the "Forgot Password" links now? What calls to use, that sort of thing?
- Are there any other changes to the Web API that I should give them a heads-up about? I was assuming that the password was the big one but are there other things that I should warn them about?
Cheers,
Matt
Hi Matt -
The password was the big one for us - it also changed how and what we could store in some session variables, which made some of our sticky functionality not work right out of the box. We also ran into a side issue with how we uploaded and cached package data which needed to change to incorporate some of the new ways that Tessitura caches pricing and performances. I'm pretty sure we are an edge use case, and the majority (if anyone) people out there won't run into those same issues.
So basically, what I'm saying is that the things we ran into were things that occurred because we had been taking advantage of what some people would call loop holes in the system. As those loop holes get tightened or fixed we've had to re-engineer some of our web functionality. So do leave time to test!
- Heather