We have a requirement where we need to send a single consolidated list of items belonging to a user which get active on particular date.
So, for example Item 1, Item 2, Item 3 gets active. These entries are inserted as Events. Now, we need to send single notification to the user with the email as:
=========================
Dear User,
Your following items got active today:
Item 1
Item 2
Item 3
Thanks,
Customer Care
=========================
For this we set the DigestDelievery to true and the emails indeed were consolidated. But, what it did was that it send single email notification repeating the entire content for each item as follows:
=========================
Dear User,
Your following items got active today:
Item 1
Thanks,
Customer Care
Dear User,
Your following items got active today:
Item 2
Thanks,
Customer Care
Dear User,
Your following items got active today:
Item 3
Thanks,
Customer Care
=========================
Please let me know if we are missing any setting or any changes need to be made in the .xslt for this to work.
regards,
Rajiv
I assume you are using a built-in XSLT formatter.
Since I have no idea about how to use/configure XSLT, in my application I created a custom content formatter in C# (this is really easy), and over there (in the .cs class) I "manually" built the resulting HTML string and inserted my items in a loop. The result HTML string is then sent as the email body.
Advantages:
1. I have 1 message "header" and 1 "footer". What's in between, gets "populated" at runtime in a loop, whether it's just 1 item or many.
2. Maybe, it's just as easy when using XSLT, ... I just don't know. But the emails my customers get contain hyperlinks which bring them right to the web page(s) for those particular item(s). Your management will love this feature!
3. Although I did not have to use this in my project, but if you need this, you can easily fetch additional data from some other non-NS data sources and "plug" it into your email message. It's possible because in a custom content formatter (C# or VB.NET, - your choice) you can use whatever .NET techniques you need, such as ADO.NET, System.IO (if you need to read from, say, some XML files), and whatever else you might want to do: a custom content formatter is just a regular .NET assembly, and you can use it as such.
|||Hi Rajiv -From a SSNS perspective, it sounds like you have everything configured for digest delivery properly. Since it's not being formatted the way you wish, the issue is in the content formatter.
If you are using the built-in XSLT content formatter, try adjusting the
XSLTransform document.
Try placing the header and footer text directly in the XSLT document and the notification data in an <xsl:template> Match on "notification". You can then use teh <xsl:apply-templates> to call the notification section.
HTH...
Joe|||
Thanks for reply, I was able to resolve the issue as you have suggested.
regards,
Rajiv
