• State Verified Answer
  • Replies 7 replies
  • Subscribers 1382 subscribers
  • Views 169 views
  • Users 0 members are here
Options
Related

TNEW New Order Interceptor

Bill Waugh
$organization

Hi Gang - This is probably a relatively simple answer, but I'm just getting started developing some interceptor plugins.  I have a functioning plugin that fires on an intercept of a POST to Txn/Orders that works great any time an order is created in the Tessitura client application or when I trigger it manually from the Web api client - but it seems that TNEW never creates a POST to Txn/Orders when a new order is created.  

The help documentation for the POST to Txn/Orders reads This resource is currently only for interceptor plugin use. This is called any time a new order is saved via the API or from the client application. Only OrderId is provided in the request content....
And the documentation for Web/Cart/{sessionKey}/Checkout has a line that reads  In order to facilitate the use of the interceptor capability, the checkout method now makes a POST call to Txn / Orders.By default this call does nothing unless a developer has added interceptor plug -in code to the exposure.

Am I doing it wrong? Does anyone know what verb/endpoint I can intercept any time a new order is created in TNEW?

Thanks,

Bill Waugh
Starlight Theatre
bill.waugh@kcstarlight.com

Parents Reply Children
  • 0 $organization in reply to Bill Waugh

    My apologies but I was speaking with out of date information. The common environment used to be to have two separate API instances, external and internal, but hosting has migrated away from this. There is really only a single (load-balanced) API instance now, with appropriate external and internal URL routing in place.

    In this case, RAMP and support should at least verify that the plugin is installed and registered as expected. You can also add logging to ensure that the Plugin code is indeed executing on a checkout.

  • 0 $organization in reply to Ryan Creps (Past Staff Member)

    Thanks for the follow up Ryan.   I'm pretty sure the plugin is installed/registered because it always fires from the application and it can be fired manually from the web API client (POST to Txn/Orders) using the same credentials that TNEW uses. (And it's listed in the plugins list if that means anything).  Haven't been able to get a response on the support ticket for the last 6 days, so I'm stuck.   Just out of curiosity - if I use the logger function of the plugin - would that write to the standard TNEW logs that I have access to in the TNEW admin or does that go to some other log?  Thanks, BW

  • +1 $organization in reply to Ryan Creps (Past Staff Member)

    It ended up being a slightly different issue with TNEW.   I'm paraphrasing - but I guess certain parts of TNEW still use the SOAP API and then access the REST API from within a SOAP API call.  The intercept still happens and the plugin fires - but the security context of the plugin gets a little messed up because it is called from a _TNSvc credential instead of your TNEW REST credential.   You really can't "do stuff" in the plugin with the _TNSvc credential.  Had to hard code in different credentials instead of being able to use input.UserName and input.UserGroup, etc as suggested in all the sample plugins.