I am working on a solution to catch records that may not have been submitted for approval. I have a text field that is read only (except for system admins) that has a default value of "Not Submitted." In the approval process, I have field updates that update the field to "Pending" when submitted for approval and then "approved" or "rejected" depending on the outcome.
I want a rule that evaluates about 8 hours after the record has been created if it has been submitted for approval and if not, sends an email alert.
I already posted in the forum about this but didn't really get an answer. Right now how I have it set up, it's not firing. I thought at first it was because the rule criteria is "Approval Status equals "Not Submitted." Initially upon record creation, all records will have that status. So it automatically goes into the workflow queue. However, someone linked me to a place in the help section where it says if the record no longer meets criteria it's removed from the queue-this isn't happening. Even after records are submitted for approval and the field is updated, it stays in the queue and sends an email that the record hasn't been submitted. Below are some screen shots:
Here's the workflow rule and email alert (I know the workflow rule picture is too small-it shows "evaluate when created and anytime it's edited to meet criteria" and the rule criteria is "Approval Status = Not Submitted"). The rule IS active.
Here is a picture of the record I tested before submitting for approval. I have the approval status set as default to "Not Submitted." The field updates on the approval process update the field to "Pending", "Approved" or "Rejected" once the approval process is initiated.
It may be hard to see but the "Approval Status" field on the right side says "Not Submitted"
Then, it goes into the workflow queue:
Then, I submit for approval and the status changes to pending:
I still received an email 8 hours later.
Any ideas? I imagine this is operator error and I've set this up wrong somehow, but any thoughts are appreciated. Thanks!
5 Antworten
I'm wondering whether this is related to the Not Submitted -> Pending field update being done as part of an approvals process rather than as a manual edit or a workflow action.
Can you go into the field update on your approval process configuration and ensure that the 'Re-evaluate workflow rules after field change' checkbox is checked?
I suspect that's unchecked, in which case the field is being updated but we're not enforcing your workflow rule to be re-evaluated, so the record stays in the queue.
Let us know how you get on!
