Ask Search:
Kevin KatoKevin Kato 

Email alert with feed tracking contents

Sales Manager in my org want to get email alert when change is made to certain fields of custom object. What he want to get is email with "'what' was changed from 'what' to 'what', for 'which' record" (e.g. 'expected revenue' changed from '1,000' to '2,000' for 'record A').

This data can be shown in Chatter using Feed Tracking (attached image). Is there a way to include this information in email alert?
chatter feed sample
I am open to not using Feed Tracking, if other way can give me the same result.
Best Answer chosen by Kevin Kato
Amnon KruviAmnon Kruvi
Hi Kevin,

You could use Field History Tracking instead of feed tracking, and create a report on the <Object> History object. Your sales manager can then subscribe to this report to receive regular updates.

You can find Field History Tracking on the setup page for that object, right above the list of custom fields.

All Answers

Amnon KruviAmnon Kruvi
Hi Kevin,

You could use Field History Tracking instead of feed tracking, and create a report on the <Object> History object. Your sales manager can then subscribe to this report to receive regular updates.

You can find Field History Tracking on the setup page for that object, right above the list of custom fields.
This was selected as the best answer
Kevin KatoKevin Kato
Thank you Amnon! I did not know about the Field History Tracking function. I will talk with the user as one option, but their current request is they get email alert when certain change is made. 

I managed to create a workflow rule to send email, when certain fields are changed. Email has a link of the record that was changed, but could not contain "what field was changed from what to what" in the email. I guess i cannot do this in configuration level and need to do little coding?
Amnon KruviAmnon Kruvi
All is not lost yet :)
If you need real-time email updates, there is a slightly more complicated solution you could take, which basically means creating your own 'tracking' object:
1. Create a new custom object, let's call it "Field Tracking"
2. Create the following custom fields: Old Value (Long Text), New Value (Long Text)
3. Create a process on your target object: Whenever field A changes, create a new Field Tracking record with the old and new values from your target object.
4. Create a workflow that sends an email whenever a new record is added to the Field Tracking object.

It's a bit of a long way around the problem, but it should work in real time.
Kevin KatoKevin Kato
Thanks Ammon, I will talk with the user and decide which way is the best.
As for the last option you propsed, my understanding is that if there are 2 fields  (e.g. A and B) that my user want to get alerted, I will need to create 4 custom fields (Old A, New A, Old B, and New B) and include all 4 fileds in the email template. Am I correct?
Amnon KruviAmnon Kruvi
You could choose to have 4 sets of fields, which would allow you to create one email with all 4 changes in the event all are made in one transaction.

If you choose to have just the one set, you could still create 4 records, and send 4 emails. It might get spammy, so only go with this approach if you need it for more than just emails (statistical analysis of how often these fields change, for example).

My admin colleagues recently implemented something similar, but if your team comes up with a better idea, please let me know so I can consider it myself next time. Good luck, regardless of which solution you go with!
Kevin KatoKevin Kato
thank you. will share if we have different option. 
Currently, we just set up workflow rule that will send email when one of the selected fields are changed. Those fields are checked in field tracking, so users are asked to open the link in the email and see "Chatter", and users can see what was changed. 
This is pretty agile solution and users will only get 1 email, but only problem is that users need to open salesforce to see what was changed. Users might get tired if email is so frequent ("how often these fields change", as you said.)
Amnon KruviAmnon Kruvi
In this case, the 4-field-set solution should work fine for you - it will send a single email as soon as the change happens. All you have to worry about is building the process to create these records - and to delete them once you no longer need them (in order to avoid storage problems).