Tessitura
Software Development
Article
Resource Update
Tessitura v15
0739b71c-e0bb-4d70-907b-07b7b0af3682
https://xmc-tessituraneab9a-tessiturane5642-staging.sitecorecloud.io/-/media/Images/Network-Updates/Playlist-Illustrations/playlist_DEV.jpg?h=465&iar=0&w=768&ttc=63891212613&tt=BE1C098D9A60E849E04F8279C01ADB55&hash=956321FA23D340186FC1FE9FA6FF8A39
Version 15 will include some major technical enhancements. Plus, we have extended support for the legacy SOAP API.
Updates from Tessitura Development
6/27/2018
Version 15 Development
Beta testing for Tessitura Version 15 with Tessitura Analytics is about to start, with the general release now scheduled for early fall of this year. In addition to Tessitura Analytics, Version 15 contains several big technical changes like the ability to use Windows credentials to log into Tessitura, the merging of the two Tessitura databases into a single database, and a complete rewrite of the report scheduling functionality.
Along with everyone else here, the Development department is getting ready for TLCC in Orlando, where we’re happy to present the Developer Hub once again.
Tessitura Processing Server
In Version 15 we are completely rewriting the Tessitura Report Server, combining the functionality of the Print At Home Server and the Report Server into a new Windows service, called Tessitura Processing Service or TPS. Eventually we see this as an all-purpose processing service which will handle many different types of Tessitura tasks, including things like emailing confirmations. We’ve also made several changes to report scheduling and maintenance to make it easier to use and administer.
First, Report Setup has been moved into the main client application so that a user with the appropriate security rights can add and edit reports right from the report menu.
The Tools/View Reports window has been redesigned so that each user can see more information about each report that is run, including any errors that may have occurred.
And a new window, Tools/Schedule Reports Queue, lets authorized users see reports that are currently in the report queue, hold any report (to stop it from running), delete a queued report, or respond to an error by allowing an instance of a report to be rescheduled.
Combined, these changes will make it much easier to maintain, schedule, and troubleshoot reports. It is also one less component to install and be responsible for. It’s part of our effort to make the Tessitura suite easier to deploy, especially in our hosted environment.
SOAP API End of Life Extension
In February of 2017 we announced that the Tessitura SOAP API would be maintained only until the 2019 release of a major Tessitura version. As we noted at the time, there were many advantages of the newer REST-based API, and Tessitura Version 14 saw the REST API eclipse the older SOAP API in functionality.
We have heard from many of you who are in the process of transitioning your websites to the new technology. Here at the Network we are doing the same. TN Express Web (TNEW) is on its way to using the new API exclusively. New technologies in Version 15, due to be released this fall, will make it even easier for our consultants to use the REST API for TNEW customizations.
At the same time, many of you have expressed concerns about meeting the 2019 deadline, either with custom website code or with third-party applications. Our goal, as always, is to minimize impact on your business, so we have extended support for the legacy SOAP API until June 30, 2020.
Transitioning to the new API will mean different things to different members. If you use TNEW to power your web transactions, then your transition will be as simple as following the standard TNEW upgrade path. TNEW organizations that have implemented TNEW customizations will need to work with Tessitura Consulting to transition those customizations before the deadline. We’ll be sending out a notification later this year to inform you when the TNEW platform is ready to fully support REST API customizations, so please be on the lookout for that. If you have any questions in the meantime, please reach out directly to our Consulting team.
It is important to remember that while this may provide more time for transitioning to the new technology, it does not mean that new functionality will be added to the legacy API. We will be careful to maintain backward compatibility, but will add no new features. All new features and functions will be supported through the REST API only. More information on the transition can be found here.
Development Sandbox Now with Full v15
The Development sandbox has now been updated with a recent build of v15, and we invite you to log in and try out some of the new features, including Tessitura Analytics. If your organization doesn’t already have a login and you would like one, contact us (roadmap@tessituranetwork.com) and we will set you up.
Topics
Software Development