1

I've been asked to look into Time-based Workflows and, more specifically, how they react with changes to events.

Two things I'm still trying to uncover are;

1 - If an event is cancelled, will the email still trigger? (My assumptions say no, but I could be wrong). 2 - What is the built-in logic for a TBW when an event has triggered an email and after the email has been sent, the event is updated? Does this re-trigger the TBW to send an email again?

1 Answer 1

3

1 - If an event is cancelled, will the email still trigger? (My assumptions say no, but I could be wrong).

Maybe. If the record no longer meets the criteria, all pending workflow actions will be deleted. So your criteria should include something like "Event is not cancelled," otherwise the email would still be sent.

2 - What is the built-in logic for a TBW when an event has triggered an email and after the email has been sent, the event is updated? Does this re-trigger the TBW to send an email again?

Maybe. Because time-based workflow is a "rising edge" trigger, it will only trigger if the record no longer meets the criteria and then later meets it again. For example, if the criteria is "date is in the future", then the record will need to first be moved to a date in the past, then moved back forward. If the email was not already sent, the date would be automatically adjusted to the new delivery date.

1
  • Excellent, thank you! These are helpful for pointing me in the direction I'm looking to go. Unfortunately I'm not privy to what these requirements are going to be put towards, however they do satisfy knowing more about how to interact with time-based workflows. I also learned something more about SFDC for myself :)
    – MacSalty
    Commented Sep 1, 2017 at 18:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .