Recent searches
No recent searches

Dave Easey
Joined May 13, 2021
·
Last activity Oct 16, 2021
Following
0
Followers
0
Total activity
3
Votes
0
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Dave Easey
Dave Easey commented,
Hi Jim,
I think the point of my question is not clear.
1) This article suggests to add both Create and Update to the Any conditions.
So the trigger will fire if the ticket was created or updated.
2) In the other 'Understanding when triggers run and fire' article you say that 'A trigger will fire and update the ticket if its conditions are met during the cycle. '
From 2) if the trigger definition is comment added or check box checked (the examples in this thread) then the trigger will fire based on this condition.
From 2) it does not seem to be necessary to and Create and Update to the Any conditions for the trigger to fire.
Is this correct or am I missing something?
View comment · Posted Mar 17, 2021 · Dave Easey
0
Followers
1
Vote
0
Comments
Dave Easey commented,
I'm confused about the suggestion to add both Create and Update to the Any conditions.
What is the difference between doing that any not including either of them?
Isn't the purpose of this condition to restrict to one or the other of Create or Update? If a trigger should run in both cases then there would seem to be no need to add the condition.
From another support article:
Understanding when triggers run and fire
Every time a ticket is created or updated, all of your triggers run in a cycle against that ticket in the order the triggers are listed. A trigger will fire and update the ticket if its conditions are met during the cycle. A cycle is the entire process of a ticket being checked against all your triggers.
View comment · Posted Mar 01, 2021 · Dave Easey
0
Followers
1
Vote
0
Comments