Triggers that refer to nonexistent entities
RespondidaWhile going over our triggers to identify unnecessary triggers, I ran across some with conditions that checked nonexistent custom fields, or actions that assigned to nonexistent groups.I would like clarification on how this affects the triggers:
-If a trigger has an ALL condition that refers to a nonexistent entity, presumably the trigger would never fire?
-If a trigger has an ANY condition that refers to a nonexistent entity, then the trigger could fire if at least one of the other ANY conditions were true?
-If a trigger has an action that refers to a nonexistent entity, can the trigger still fire, and if so, then would it perform any action that refers to a valid entity?
-
Someone from Zendesk can probably correct me but I believe I read in their developer documentation that non-existent conditions are completely ignored as if they weren't there. We've also experienced this to be true.
So if a non-existent entity appeared in:
- ALL: the trigger will fire if all other conditions were met
- ANY: the trigger will fire if at least one other condition is met
- ACTIONS: All valid actions are performed if conditions are met
-
Hi Pan
Your recollection aligns with mine, but I'm looking for the specific documentation to support this. I'll update here when I find the answer to this.
UPDATE: I've done a quick bit of testing and it appears that an invalid trigger condition does prevent a trigger from running. This feels like something our system should handle more gracefully, so I'm going to be raising a bug report to our Developers. I'll be happy to report back when I hear back on this one.
Iniciar sesión para dejar un comentario.
2 Comentarios