Has anyone played around/created a HTML template for pre-show emails? We want to keep this in tess so a record of the email lives in the constituency record vs using outlook/ect.
Nick Reilingh said:Recently I've done some work with post-order emails for virtual events ("how to watch"-type emails for video-on-demand, for example)
Nick,
you hit it on the head with the comment above. This is what sparked this need to move away from WF and onto a tess html email for this information based email that is NOT a marketing/sales email.
Do you have a Html template you could share with me regarding this sentence? “Recently I've done some work with post-order emails for virtual events ("how to watch"-type emails for video-on-demand, for example)
glad to see another org looking into the same project!
-Stephen
Happy to share my template code, but I don't think it would be all that helpful. So far, the way I've chosen to implement these has actually been to let our comms team write their copy in a WordFly template, using the existing implementation of our design language that we would use in marketing emails. I devised a process to "export" the WordFly HTML in a format that is suitable for use in a Tessitura HTML template, and then I smack some C#/Razor code up at the top to generate the dynamic content fields referenced inside the template. (This means on the WordFly template side, I'm actually using Razor's @-syntax as "merge fields" instead of the typical WordFly template merge field syntax. The @-syntax gets passed through unmangled, and is interpreted as part of the Razor template when it is rendered by Tessitura.)
The dynamic content in question isn't really anything more than an "add to calendar" button and some special date parsing for one particular performance where single-attendee timeslots are implemented as different price zones inside of a performance. We're using separate templates for each production. (Nowhere near the amount of dynamism that I have in my WordFly preshow email process.) So, the only things it really demonstrates are some specific applications of the .NET DateTime and TimeZone APIs, how to construct a URL query string per the API of the vendor I am using for calendar integration, and one specific filtering of the Tessitura OrderProductView data model per the Tessitura API spec. Likely too much "give a man a very strange looking fish" and not enough "teach a man to fish" given the rest of the process I'm using.
I could probably be persuaded to give a talk or screencast on the WordFly->Tessitura template export process if there is significant interest...
Hi Alicia, looping you into this thread to see if this will be helpful for our night of email instructions.