Using custom data in an email confirmation

Okay, new question:

Is there a way to define separate "From"/"BCC" addresses for different email acks? Currently everything comes from our box office email (because until now, the box office have been the only ones using the functionality), but for the financial aid acknowledgements we want them to come from a different address. I see that in 12.5 there is TR_RECEIPT_SETTINGS, and it seems like maybe it's what I want, but that also seems to be designed to be used only with TRBO?

Any other insights?

Thanks!

-p.

Patrick Schley
Academy Services Manager
First Stage 

I brought this problem to Jon Ballinger at the Conference during the "Hackathon" section, and he knocked out a proof of concept for doing it using interceptors.

I'd love to see the sample code for that. The only way I have found to do this natively is to add a separate parent table with its own settings, which is not a very practical way for managing this.

Unknown said:

Is there a way to define separate "From"/"BCC" addresses for different email acks? 

If you assemble your e-mail ack in SQL, this becomes a trivial case statement. We choose between multiple From/CC/BCC values, depending on order content.

I'll just add a new snippet of code into this thread, one that may read a little easier than some of the previous code snippets (which were also helpful to me).

We are using the latest TNEW out-o-the-box and needed a way to add into the order confirmation, the name/address/etc.. of the person that, via TNEW, our customer purchased a gift membership for.

So basically, it was just another customer service tidbit (non-line item related) that we wanted to throw into the email.

First was the creation of the stored procedure to pull the giftee membership info out of the CSI data that came in on the TNEW order. The stored procedure takes an order_no, and returns a single row with heading "recipient_info", containing the concatenated name and address information of the giftee. I'll add that later if someone wants it.

Next was to make the web api call and dump the SProc data into the order confirmation template, concatenating it with Contrib_DynEmailContent. Since we will always have a "Thank you..." message for contributions, I chose to add it into the bit of code that dumps out the dynamic email content for products of type "contribution". Also, I plugged in the "t" (var t = new Tessitura.WebAPI.Tessitura();) and session info (OrderData.SessionKey) via how they were first defined earlier in the email confirmation template code.

if (ced.Contrib_DynEmailContent.Length > 0) {

dynContent += ced.Contrib_DynEmailContent + "<BR/><BR/>";

//mnhs: begin

DataSet result2 = t.ExecuteLocalProcedure(OrderData.SessionKey, 52, "@order_no=" + OrderData.OrderNumber);

for (int i = 0; i < result2.Tables[0].Rows.Count; ++i) {

string giftMembershipInfo = result2.Tables[0].Rows[0]["recipient_info"].ToString();

dynContent += "<h3>Your Gift Membership Information</h3><table><tr>";

dynContent += "<td width='10px'></td><td>" + giftMembershipInfo + "</td></td>";

dynContent += "</tr></table>";

}

//mnhs: end

}

The 'for loop' was added because, even though there will only be a single row returned, i wanted the code ignored if someone bought a standard membership (not a gift membership).

This dropped the following lines into the standard TNEW order confirmation email if a Gift Membership was purchased:

Your Gift Membership Information

     Joe Bob Briggs 135 Rose ct nw andover, MN (1) 55304   

I'll just add a new snippet of code into this thread, one that may read a little easier than some of the previous code snippets (which were also helpful to me).

We are using the latest TNEW out-o-the-box and needed a way to add into the order confirmation, the name/address/etc.. of the person that, via TNEW, our customer purchased a gift membership for.

So basically, it was just another customer service tidbit (non-line item related) that we wanted to throw into the email.

First was the creation of the stored procedure to pull the giftee membership info out of the CSI data that came in on the TNEW order. The stored procedure takes an order_no, and returns a single row with heading "recipient_info", containing the concatenated name and address information of the giftee. I'll add that later if someone wants it.

Next was to make the web api call and dump the SProc data into the order confirmation template, concatenating it with Contrib_DynEmailContent. Since we will always have a "Thank you..." message for contributions, I chose to add it into the bit of code that dumps out the dynamic email content for products of type "contribution". Also, I plugged in the "t" (var t = new Tessitura.WebAPI.Tessitura();) and session info (OrderData.SessionKey) via how they were first defined earlier in the email confirmation template code.

if (ced.Contrib_DynEmailContent.Length > 0) {

dynContent += ced.Contrib_DynEmailContent + "<BR/><BR/>";

//mnhs: begin

DataSet result2 = t.ExecuteLocalProcedure(OrderData.SessionKey, 52, "@order_no=" + OrderData.OrderNumber);

for (int i = 0; i < result2.Tables[0].Rows.Count; ++i) {

string giftMembershipInfo = result2.Tables[0].Rows[0]["recipient_info"].ToString();

dynContent += "<h3>Your Gift Membership Information</h3><table><tr>";

dynContent += "<td width='10px'></td><td>" + giftMembershipInfo + "</td></td>";

dynContent += "</tr></table>";

}

//mnhs: end

}

The 'for loop' was added because, even though there will only be a single row returned, i wanted the code ignored if someone bought a standard membership (not a gift membership).

This dropped the following lines into the standard TNEW order confirmation email if a Gift Membership was purchased:

Your Gift Membership Information

     Joe Bob Briggs 135 Rose ct nw andover, MN (1) 55304