Timeline for Email alert to send only once to the owner
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2016 at 8:13 | vote | accept | user28452 | ||
| Nov 8, 2016 at 6:40 | comment | added | Santanu Boral | That's not a reason, then your field update will effect the same delay | |
| Nov 8, 2016 at 6:37 | comment | added | user28452 | I am still thinking on your suggestion because our system is global so it might be possible that batch execution time vs createdDate filter might cause potential delay to some users on getting the email alert. | |
| Nov 8, 2016 at 6:33 | comment | added | Santanu Boral | you can create a separate script for that which will run a single time | |
| Nov 8, 2016 at 6:31 | comment | added | Santanu Boral | That is your one time migration effort | |
| Nov 8, 2016 at 6:28 | comment | added | user28452 | Within 24 hours will not cover historical leads post deployment of the batch apex right? | |
| Nov 8, 2016 at 6:26 | comment | added | Santanu Boral | yes, check the lead creation date within 24 hours, so the next day those leads will not be picked up | |
| Nov 8, 2016 at 6:24 | history | edited | Santanu Boral | CC BY-SA 3.0 |
added 189 characters in body
|
| Nov 8, 2016 at 6:23 | comment | added | user28452 | Thanks for the response. The batch is scheduled to run once a day. So let's say the batch job ran today and sent Lead Record 1, Lead Record 2 to Owner 1. By tomorrow when the same batch executed Lead Record 1 & 2 should not be sent to Owner 1 and Owner 1 should get emails only if there are new leads other than 1 & 2. | |
| Nov 8, 2016 at 6:20 | history | answered | Santanu Boral | CC BY-SA 3.0 |