As is, your current workflow criteria formula would evaluate to true for the entire calendar year (Jan 1 - Dec 31) during which your contact is turning 71 years old.
So far, so good. This sounds like exactly what you're expecting to happen.
With workflow rules, however, you need to keep in mind that they aren't evaluated on a schedule. Workflow rules can be evaluated when a record is created, every time a record is updated, or when a record is updated to meet some criteria (and previously did not meet that criteria).
If you don't edit the contact record, the workflow won't be evaluated.
Using that workflow evaluation criteria, and having the workflow send an email alert, can result in your email being sent multiple times in a single day, for the entire year.
To me, the thought of getting the same email for an entire year is...not appealing, to put it mildly (even less so if it can happen multiple times per day). A more precise explanation of the context surrounding this email might help, but I'd personally be annoyed after about day 2 or 3 of this.
I'd strongly advise putting a rate-limiting mechanism in place. Creating a new Date
field on the Contact
object, let's call it turning_71_workflow_email_last_sent__c
, is almost all you'd need.
You can add and subtract with Date
and DateTime
fields in formulas, so to limit your workflow rule to sending out an email only every 3 days could be
AND(
TODAY() - turning_71_workflow_email_last_sent__c >= 3,
Year(TODAY()) - Year(Birthdate)= 71
)
You would likely want to include a workflow field update in the workflow actions, along with your email alert, to update turning_71_workflow_email_last_sent__c
Conclusion
Your proposed workflow evaluation formula will do what you expect it to, but I'm not sure if workflow is the tool that you should use in this case.
There are probably other factors that you should be taking into consideration as well.
Without additional explanation of what you're doing, I'm afraid I can't provide much more help.