This is a helpful start and I think I understand it.
However, my situation is a little more complex and a little more unique than this.
I’ll keep the same “terms” that we’re using in this example for continuity.
Ok - so the filter that you’ve built, by watching the “Alert Me” view in Table 10, and filtering the action to run for “Not Working”, “Needs Review” or “Action Needed”, makes sense, but it doesn’t cover exactly what I need.
Essentially, in my example a status of “pending” is essentially the penultimate step in my process before “DONE”. Meaning, once a record gets to the “pending” state, my internal process that I’m tracking has an expectation that the next step is for that record to move into a “DONE” status.
If something changes this record’s process flow and then requires additional work to be done on that record - and the record does not progress to a “DONE” status, and it goes back into an “action needed” status, or “Not Working”, or “Needs Review”, that’s when I want to trigger an alert.
I’ll illustrate this.
Let’s say a record’s natural flow is being tracked by a field called “status”.
In a normal process from start to finish a record might have a status that follows these:
- Work Order Created
- Not Working
- Action Needed
- Needs Review
(Let’s say that if a record goes through our process and hits all of those states linearly, then that’s the normal flow and I don’t need an alert triggered).
The only time I want an alert triggered is if I get to step #6, where status = PENDING, and if something happens where instead of the task completing and being flipped to “DONE”, someone determines that a record requires more work.
So, if it goes from “Pending” backwards in the workflow to a state that is either:
3. Not Working
4. Action Needed
5. Needs Review
That’s when I’d like a trigger alert.
It’s essentially my way of saying “hey pay attention to this. Something went wrong and deviated from the normal work flow - let’s find out why”.