T
tcallen@dmsi.com
Guest
Our use case is that we have a batch job that runs daily and locates stale cases (as defined as a case's UpdatedAt field older than 2 days from the current date) then sends an email (via a call out to a case trigger) to the department head. However, when the batch job sends the email, it attaches the sent email to the case and thereby sets the case's UpdatedAt field to the current date and time. As a result, when the batch job runs next, this case is no longer seen as "stale". Which is not accurate. I realize there are workarounds (and we have pursued one such workaround), but I'd like to see an option added to "send email" trigger types that gives admins the ability to not have the UpdatedAt field changed upon sending an email.
Continue reading...
Continue reading...