I want to add the order number (as in ORDER-123) to the subject of my order confirmation email. I see that tokens in the email subject have been around for a while:
Change log for uCommerce 1.5.1.0
NEW: EmailService can insert dynamic data in subject and for template, e.g. "Confirmation for order number {orderNumber}." combined with Send() which takes a dictionary parameter.
But the {orderNumber} parameter is actually returning the OrderGuid, which isn't very helpful to the user, who sees: Confirmation of order 0acd4856-130e-49ec-974b-8312ceb335a2.
Here is the code that does the email send in the SendEmailTask class:
I did see that article. As I pointed out, it looks like this functionality was built into uCommerce in version 1.5, but I can't find much documentation.
I would prefer to use the feature OOTB if it is available. If it is not, then I would just rewrite the pipeline task that sends the confirmation email - but as I mentioned, I would prefer to not have to write any code, as it looks like it is already built into the system.
You'll have to call the email service yourself to add an additional parameter. I do agree that orderNumber should hold the actual order number rather than the guid (it's passed in a second parameter anyway).
Adding additional parameters to email templates for email subject.
I want to add the order number (as in ORDER-123) to the subject of my order confirmation email. I see that tokens in the email subject have been around for a while:
Change log for uCommerce 1.5.1.0
NEW: EmailService can insert dynamic data in subject and for template, e.g. "Confirmation for order number {orderNumber}." combined with Send() which takes a dictionary parameter.
Maybe you can find help in this article http://blogs.thesitedoctor.co.uk/tim/2011/04/08/Taking+UCommerce+Emails+To+The+Next+Level+And+Include+The+Order+Id+In+The+Subject+Multiple+Recipients+And+Google+Click+Tracking.aspx
Thanks Kim,
I did see that article. As I pointed out, it looks like this functionality was built into uCommerce in version 1.5, but I can't find much documentation.
I would prefer to use the feature OOTB if it is available. If it is not, then I would just rewrite the pipeline task that sends the confirmation email - but as I mentioned, I would prefer to not have to write any code, as it looks like it is already built into the system.
Cheers,
Daniel
Hi Daniel,
You'll have to call the email service yourself to add an additional parameter. I do agree that orderNumber should hold the actual order number rather than the guid (it's passed in a second parameter anyway).
I'll put it on the bug tracker.
Sorry about the inconvenience.
is working on a reply...