You are currently reviewing an older revision of this page.
As of April 30, 2021, version 16 of Tessitura and TNEW are announced and (at least Tessitura is) in internal alpha testing. Closed beta is expected to occur in Q3 of the calendar year.
TNEW Customizations (by which we mean database procedures which are invoked by hooks and URL routes inside the TNEW application) may be affected by changes in v16 in a few important ways:
The usage of LWP_VALIDATE_CART will be replaced by a local procedure execution path for the same hooks. This means that in LTR_VALIDATE_CART, where you enable validation point hooks for various TNEW events, you will instead identify a local procedure to be invoked in place of LWP_VALIDATE_CART for each hook. In theory, this does not represent a loss in functionality, but more research is necessary to discover the best practices for refactoring existing LWP_VALIDATE_CART functionality into individual procedures. (Possibly this could be accomplished with some kind of wrapper procedure that reuses LWP_VALIDATE_CART, but many customizations use extended validation point logic that would require some changed URLs and other methods of invocation.)
The SOAP API removal represents a much more impactful change for those customizations that leverage the TNEWSqlBridge CLR procedures. At present, the next-generation answer to this has not yet been implemented, but it does remain in scope for V16's general release, and some preliminary design intentions do exist: TNEW will provide for something akin to a webhook infrastructure, where the same validation points that exist with precart can now invoke an external web service, which presumably will be provided with some context about the session such that it can easily make API calls back to the services with session context. It is recommended to wait for this feature to be implemented and fleshed out before rebuilding customizations that currently use the CLR procedures for v16.
New development happening today against v15.1 does not have many good options, in the event that bridging to the services layer is necessary from within a TNEW customization. If you build using the CLR procedures, you will just have to rearchitect the customization as a web service when v16 is available. The only way to avoid this while staying inside the database is to instead make calls to the REST services using OLE Automation, which tends to be very delicate and challenging code.