<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communitytest.tessitura.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Transitioning TNEW Customizations to V16</title><link>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16</link><description>Wiki for creating community documentation.</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator><item><title>Transitioning TNEW Customizations to V16</title><link>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16</link><pubDate>Fri, 28 May 2021 04:26:14 GMT</pubDate><guid isPermaLink="false">fd08b0f2-65fa-4b2b-916a-cce3e88b61d0:73db91eb-b056-4847-957b-3d550d685a98</guid><dc:creator>Nick Reilingh</dc:creator><comments>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16#comments</comments><description>Current Revision posted to Community Docs Wiki by Nick Reilingh on 5/28/2021 4:26:14 AM&lt;br /&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;As of May 28, 2021, everything&amp;nbsp;on this page is superseded by information in the &lt;a href="https://www.tessituranetwork.com/en/Items/Videos/Webinars/2021/Open-Studio-May-2021"&gt;May 2021 Open Studio&lt;/a&gt; (45:30).&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;few important ways:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The LWP_VALIDATE_CART execution path will be deprecated (or removed? currently unconfirmed.)&lt;/li&gt;
&lt;li&gt;The legacy SOAP API is being removed, which will affect any customizations currently making use of the &amp;quot;TNEWSqlBridge&amp;quot; CLR procedures which are used to invoke SOAP methods from within a database procedure.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;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&amp;nbsp;each&amp;nbsp;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.)&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;has not yet&amp;nbsp;been implemented, but it does remain in scope for V16&amp;#39;s general release, and some preliminary design&amp;nbsp;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&amp;nbsp;implemented and fleshed out before rebuilding customizations that currently use the CLR procedures for v16.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: tnew customization, tnew, v16&lt;/div&gt;
</description></item><item><title>Transitioning TNEW Customizations to V16</title><link>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16/revision/2</link><pubDate>Sat, 01 May 2021 04:14:50 GMT</pubDate><guid isPermaLink="false">fd08b0f2-65fa-4b2b-916a-cce3e88b61d0:73db91eb-b056-4847-957b-3d550d685a98</guid><dc:creator>Nick Reilingh</dc:creator><comments>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16#comments</comments><description>Revision 2 posted to Community Docs Wiki by Nick Reilingh on 5/1/2021 4:14:50 AM&lt;br /&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;few important ways:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The LWP_VALIDATE_CART execution path will be deprecated (or removed? currently unconfirmed.)&lt;/li&gt;
&lt;li&gt;The legacy SOAP API is being removed, which will affect any customizations currently making use of the &amp;quot;TNEWSqlBridge&amp;quot; CLR procedures which are used to invoke SOAP methods from within a database procedure.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;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&amp;nbsp;each&amp;nbsp;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.)&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;has not yet&amp;nbsp;been implemented, but it does remain in scope for V16&amp;#39;s general release, and some preliminary design&amp;nbsp;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&amp;nbsp;implemented and fleshed out before rebuilding customizations that currently use the CLR procedures for v16.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: tnew customization, tnew, v16&lt;/div&gt;
</description></item><item><title>Transitioning TNEW Customizations to V16</title><link>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16/revision/1</link><pubDate>Sat, 01 May 2021 04:13:55 GMT</pubDate><guid isPermaLink="false">fd08b0f2-65fa-4b2b-916a-cce3e88b61d0:73db91eb-b056-4847-957b-3d550d685a98</guid><dc:creator>Nick Reilingh</dc:creator><comments>https://communitytest.tessitura.com/topical_groups/developers/w/community-developer-documentation/788/transitioning-tnew-customizations-to-v16#comments</comments><description>Revision 1 posted to Community Docs Wiki by Nick Reilingh on 5/1/2021 4:13:55 AM&lt;br /&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;few important ways:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The LWP_VALIDATE_CART execution path will be deprecated (or removed? currently unconfirmed.)&lt;/li&gt;
&lt;li&gt;The legacy SOAP API is being removed, which will affect any customizations currently making use of the &amp;quot;TNEWSqlBridge&amp;quot; CLR procedures which are used to invoke SOAP methods from within a database procedure.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;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&amp;nbsp;each&amp;nbsp;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.)&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;has not yet&amp;nbsp;been implemented, but it does remain in scope for V16&amp;#39;s general release, and some preliminary design&amp;nbsp;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 for this feature to be&amp;nbsp;implemented and fleshed out before rebuilding customizations that currently use the CLR procedures for v16.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: tnew customization, tnew, v16&lt;/div&gt;
</description></item></channel></rss>