Email Order Ack/Conf customization - where to start?

Hi Nick,

The SOAP API documentation - http://www.tessituranetwork.com/~/media/Documentation/Web%20API/API_Documentation_V12.ashx - addresses this in Appendix D. Essentially, the templates are ASPX pages with XSL style sheets. I built one using one of the samples as a starting point. You can also embed API calls to grab data that isn't already available. For example, I added a call to grab specifics of the payment methods used so we could include that in the order confirmation.

It likely won't answer all of your questions, but that appendix is a good place to start. I hope that helps!

Thanks,
David

Nick,

The SOAP Api Documentation is a good start .  You can search the forums on this topic there are a lot of good posts.   Here is one that I posted a few years agao with some somaple code.

http://www.tessituranetwork.com/community/forums/p/4269/14055.aspx

Jon

Sorry put incorrect link in here is a good post.

 

http://www.tessituranetwork.com/community/forums/p/11185/36224.aspx

In the past I usually just got a new session key before making calls to bring in data that is not part of the order details.
________________________________
From: Gawain Lavers
Sent: ‎1/‎5/‎2015 2:23 PM
To: Ballinger, Jon W
Subject: RE: [Tessitura Technical Forum] Email Order Ack/Conf customization - where to start?


Hey guys, quick related question: when the ASP code in the template runs, is it part of or does it have access to the session that called it? I.e. can I pull session variables into the output?
From: Gloria Ormsby
Sent: 1/5/2015 6:45:06 PM
The API documentation has a special section for confirmation emails. Appendix D.

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nick Reilingh
Sent: Monday, January 05, 2015 1:37 PM
To: Gloria Ormsby
Subject: [Tessitura Technical Forum] Email Order Ack/Conf customization - where to start?


Hello,

I'm interested in customizing the email order acknowledgements/confirmations, but I can't find a single lick of documentation on the subject beyond what's in the T_FORMAT_INFO table documentation.

I've got a couple of different languages under my belt, but have never written anything for ASP. Just an explanation of what language we're writing in, what context the file is being processed in (what resources to we have to work with, etc), and how to streamline the development process (I'm sure triggering repeated emails from the client is not the best way to go) would be extremely helpful.

(Maybe this would be something good to add to the developer wiki?)



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

________________________________

This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.

Thanks everyone! Whatever I was searching for didn't turn up that document, but it looks like that'll help for sure.

Just one little follow-up:

It looks like if the template file defines a subject line for the email, it will only be applied if there is no ORDER_EMAIL_SUBJECT_LINE in T_DEFAULTS. Is it safe to just remove that defaults entry so it doesn't override the template subject? (I'm trying to make the application behavior the same as TNEW's, and that Defaults entry only exists for Impresario, not Tessitura Web.)

Aha! Figured out the subject line thing. TNEW must be calling the send confirm email API method without specifying the subject argument, whereas the client application DOES specify the subject argument of that method.

Also discovered that simply leaving that T_DEFAULTS setting blank has the same effect as removing it entirely -- the API will not overwrite the subject defined in the template file.