Hey folks,
We're looking at a fairly aggressive upgrade timeline for v12, with our only real upgrade window set for this August. That said, I haven't hear too much about v12 backwards compatibility.
Does anyone from the network or early beta testers have any insight?
I know that there is the password change to one way hashes, but is there anything else? Off the cuff, I'm curious and or concerned about price map changes. And also wondering what methods will be available for the new rules engine. Or will that be saved for v12.5?
Any insight is greatly appreciated.
Thanks,
James
Hi James!Looks like you found this already (great) but I'll say it for the benefit of all. Check out this page over on the Tessitura Developers website. It's a primer on what's new with the V12 SOAP API.
http://developer.tessituranetwork.com/pages/viewpage.action?pageId=26542800
Didn't know there is a Tessitura Developer website? We just launched it a few months ago. This site is open to all types of developers who use Tessitura (vendors or on-staff folks) and the purpose is to provide a place to share ideas and/or code, meet up with other devs and get documentation and API/services layer-related news. Unlike tessituranetwork.com which is open to members only, vendors are welcome to log into the Tessitura Developer site. Please be sure your web developers know about it. To get a login, email webmaster@tessituranetwork.com.
To answer the specific questions, v12 SOAP API backward compatibility has been maintained with the exception of UpdateSpecialActivity (see below) and the password encryption changes which were previously announced (see the May Network Update for details on password encryption or the developer site).
UpdateSpecialActivity
The solicitor parameter for this method is not totally backward compatible and relies on a worker_customer_no having been entered in the security application for each solicitor used. We now store the customer_no (from T_CUSTOMER) of the worker rather then their userid (from T_METUSER). The V12 security application allows optionally assigning a customer_no to each Tessitura login.
Regarding pricing setup, the changes introduced with V12 will maintain backward compatibility as well. During V12 migration, all price map setup will be migrated to the new table structures and format. Pricing rules will not be introduced until V12.5.
Hope this helps!Kristin
Thanks, Kristin!!!
That post is very helpful.