You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
msgid "Many condition settings in Zammad, no matter if in ticket scope or not, re-appear in several places of Zammad. For this reason we created a dedicated documentation section to avoid duplicate content."
msgid "Have a look at :doc:`/misc/object-conditions/index` to learn even more! 🎉"
7442
7446
msgstr ""
7443
7447
@@ -9666,6 +9670,206 @@ msgstr ""
9666
9670
msgid "Screenshot of “Triggers” page in admin panel"
9667
9671
msgstr ""
9668
9672
9673
+
#: ../manage/trigger/how-do-they-work.rst:2
9674
+
msgid "How Do Trigger Work"
9675
+
msgstr ""
9676
+
9677
+
#: ../manage/trigger/how-do-they-work.rst:4
9678
+
msgid "Triggers consist of three parts:"
9679
+
msgstr ""
9680
+
9681
+
#: ../manage/trigger/how-do-they-work.rst:6
9682
+
msgid "**Activators:** define \"when the question is asked?\""
9683
+
msgstr ""
9684
+
9685
+
#: ../manage/trigger/how-do-they-work.rst:7
9686
+
msgid "**Conditions:** answer the question \"when should this trigger fire?\""
9687
+
msgstr ""
9688
+
9689
+
#: ../manage/trigger/how-do-they-work.rst:8
9690
+
msgid "**Actions:** answer the question \"what should happen when it does?\""
9691
+
msgstr ""
9692
+
9693
+
#: ../manage/trigger/how-do-they-work.rst:10
9694
+
msgid "Triggers are evaluated in alphabetical order by **name.** In some situations, triggers might be the wrong choice, see :doc:`/manage/trigger/limitations` for more information."
9695
+
msgstr ""
9696
+
9697
+
#: ../manage/trigger/how-do-they-work.rst:14
9698
+
msgid "**🤓 Emails can adjust some behavior on their own**"
9699
+
msgstr ""
9700
+
9701
+
#: ../manage/trigger/how-do-they-work.rst:16
9702
+
msgid "See :doc:`/channels/email/email-headers` for more information."
msgid "An action based trigger always requires a ticket update to run. This can be an update by an agent or even internal system updates like updated SLA times. See the explanation below for more details."
msgid "Checks if any attribute from the condition was updated. If yes, the trigger runs. If the attributes from the condition weren't touched, the trigger doesn't run."
9737
+
msgstr ""
9738
+
9739
+
#: ../manage/trigger/how-do-they-work.rst:35
9740
+
msgid "**Example:** A trigger with a condition for priority **1 low** will run if the ticket was changed to **1 low**."
msgid "Checks if the current state of the ticket matches the condition. This means: the trigger always runs when the ticket is updated, no matter what was changed. This can lead to executing such a trigger more often."
9750
+
msgstr ""
9751
+
9752
+
#: ../manage/trigger/how-do-they-work.rst:43
9753
+
msgid "**Example:** A trigger with a condition for priority **1 low** will run if the ticket was moved to another group while priority was set **1 low**."
9754
+
msgstr ""
9755
+
9756
+
#: ../manage/trigger/how-do-they-work.rst:46
9757
+
msgid "If in doubt, use **Selective**. The **Always** action activator can lead to unexpected behavior, e.g. the trigger runs after internal system changes of the ticket, which aren't visible in the ticket history."
9758
+
msgstr ""
9759
+
9760
+
#: ../manage/trigger/how-do-they-work.rst:51
9761
+
msgid "Time Event"
9762
+
msgstr ""
9763
+
9764
+
#: ../manage/trigger/how-do-they-work.rst:53
9765
+
msgid "The execution is triggered at a specific time when a certain event is reached, e.g. ticket pending time."
9766
+
msgstr ""
9767
+
9768
+
#: ../manage/trigger/how-do-they-work.rst:56
9769
+
msgid "This activator simply checks if **conditions** match. This is the same behavior as action-based activator's \"always\" mode."
9770
+
msgstr ""
9771
+
9772
+
#: ../manage/trigger/how-do-they-work.rst:59
9773
+
msgid "When creating a trigger, choose activator here:"
msgid "When creating a trigger, define your conditions here:"
9783
+
msgstr ""
9784
+
9785
+
#: ../manage/trigger/how-do-they-work.rst:70
9786
+
msgid "Trigger conditions must match as configured for the trigger to fire."
9787
+
msgstr ""
9788
+
9789
+
#: ../manage/trigger/how-do-they-work.rst:77
9790
+
msgid "When creating a trigger, define your changes here:"
9791
+
msgstr ""
9792
+
9793
+
#: ../manage/trigger/how-do-they-work.rst:81
9794
+
msgid "Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/variables`, which can be used to build highly-customized message templates."
9795
+
msgstr ""
9796
+
9797
+
#: ../manage/trigger/how-do-they-work.rst:85
9798
+
msgid "A trigger can do the following things once its conditions have been met:"
9799
+
msgstr ""
9800
+
9801
+
#: ../manage/trigger/how-do-they-work.rst:96
9802
+
msgid "Modify the ticket"
9803
+
msgstr ""
9804
+
9805
+
#: ../manage/trigger/how-do-they-work.rst:88
9806
+
msgid "Examples: escalate its priority, close it, reassign it, rename it, add tags, subscribe and unsubscribe specific/all users, etc."
9807
+
msgstr ""
9808
+
9809
+
#: ../manage/trigger/how-do-they-work.rst:91
9810
+
msgid "Date & time attributes (like **Pending till**) can be specified in *absolute* or *relative* terms."
9811
+
msgstr ""
9812
+
9813
+
#: ../manage/trigger/how-do-they-work.rst:94
9814
+
msgid "You can also combine static text with placeholders for text fields. Remember that the placeholders' values have to be known during trigger runtime. Learn more about :doc:`/misc/variables`."
9815
+
msgstr ""
9816
+
9817
+
#: ../manage/trigger/how-do-they-work.rst:107
9818
+
msgid "Send an email or SMS"
9819
+
msgstr ""
9820
+
9821
+
#: ../manage/trigger/how-do-they-work.rst:99
9822
+
msgid "Either to the customer, the agent who owns the ticket, or every agent in the system."
9823
+
msgstr ""
9824
+
9825
+
#: ../manage/trigger/how-do-they-work.rst:102
9826
+
msgid "Sending emails allows you to include the attachments of the triggering article if required."
9827
+
msgstr ""
9828
+
9829
+
#: ../manage/trigger/how-do-they-work.rst:105
9830
+
msgid "In order to send emails with triggers, you need to configure an email address for the group, the trigger is working in. If you don't, Zammad will skip the trigger completely."
9831
+
msgstr ""
9832
+
9833
+
#: ../manage/trigger/how-do-they-work.rst:110
9834
+
msgid ":doc:`Fire a webhook </manage/webhook>`"
9835
+
msgstr ""
9836
+
9837
+
#: ../manage/trigger/how-do-they-work.rst:110
9838
+
msgid "Connect Zammad to another web service or application to give it live updates about new tickets."
9839
+
msgstr ""
9840
+
9841
+
#: ../manage/trigger/how-do-they-work.rst:114
9842
+
msgid "Add internal or public notes to the ticket"
9843
+
msgstr ""
9844
+
9845
+
#: ../manage/trigger/how-do-they-work.rst:113
9846
+
msgid "This allows you to help your agents with specific information if needed. (e.g. automated changes a trigger applied to the ticket)"
9847
+
msgstr ""
9848
+
9849
+
#: ../manage/trigger/how-do-they-work.rst:119
9850
+
msgid "Localization of Execution Changes"
9851
+
msgstr ""
9852
+
9853
+
#: ../manage/trigger/how-do-they-work.rst:121
9854
+
msgid "The system locale and timezone predefines a default format of date and timestamp replacement variables. These settings are customizable for triggers."
9855
+
msgstr ""
9856
+
9857
+
#: ../manage/trigger/how-do-they-work.rst:0
9858
+
msgid "Screenshot showing localization section of trigger dialog"
9859
+
msgstr ""
9860
+
9861
+
#: ../manage/trigger/how-do-they-work.rst:128
9862
+
msgid "Best practice is to create single separated localized triggers for each language/timezone and execute them based on user or organization attributes."
9863
+
msgstr ""
9864
+
9865
+
#: ../manage/trigger/how-do-they-work.rst:131
9866
+
msgid "The format and timezone of date and timestamp replacement variables is customizable by the use of the ``dt()`` method. Further on the ``t()`` method can be used to translated string replacement variables according to the selected locale language."
9867
+
msgstr ""
9868
+
9869
+
#: ../manage/trigger/how-do-they-work.rst:133
9870
+
msgid "For usage of the ``t()`` and ``dt()`` method, please follow the instructions in the :ref:`variables section <variable_localization>`."
9871
+
msgstr ""
9872
+
9669
9873
#: ../manage/trigger/learn-by-example.rst:2
9670
9874
msgid "Trigger Examples"
9671
9875
msgstr ""
@@ -10493,18 +10697,6 @@ msgstr ""
10493
10697
msgid "Next, choose a suitable activator type under **Activated by** field:"
msgid "This will execute the trigger on a specific action, e.g. user creating or updating a ticket, an email coming in."
10510
10702
msgstr ""
@@ -10513,18 +10705,10 @@ msgstr ""
10513
10705
msgid "If you choose **Action** activator, you can set one of the two options for **Action execution**, in order to influence how it evaluates configured conditions:"
msgid "This will check if any property used as a condition attribute was updated by the action. If the action behind the trigger was one other than update, it will simply check if the conditions match."
msgid "Zammad differentiates between selected and saved conditions. These can be combined wherever needed. You can find a description of the condition operators for core workflows in :doc:`/system/core-workflows/condition-operators`."
0 commit comments