Maintenance: Changed text about restart handling (#590 system docs)

Author: ralf401

locale/admin-docs.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad Admin Documentation pre-release\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-11-29 15:26+0100\n"
+"POT-Creation-Date: 2024-12-17 13:20+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
@@ -382,7 +382,7 @@ msgstr ""
 
 #: ../channels/email/accounts/account-setup.rst:110
 #: ../misc/object-conditions/basics.rst:193
-#: ../system/objects.rst:154
+#: ../system/objects.rst:152
 #: ../system/objects/types.rst:157
 msgid "Type"
 msgstr ""
@@ -986,8 +986,8 @@ msgstr ""
 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15
 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15
 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18
-#: ../system/objects.rst:162
-#: ../system/objects.rst:246
+#: ../system/objects.rst:160
+#: ../system/objects.rst:244
 msgid "Note"
 msgstr ""
 
@@ -2634,8 +2634,8 @@ msgstr ""
 #: ../manage/scheduler.rst:39
 #: ../manage/slas/how-do-they-work.rst:26
 #: ../manage/templates.rst:33
-#: ../system/objects.rst:130
-#: ../system/objects.rst:234
+#: ../system/objects.rst:128
+#: ../system/objects.rst:232
 msgid "Name"
 msgstr ""
 
@@ -2669,8 +2669,8 @@ msgstr ""
 #: ../manage/scheduler.rst:111
 #: ../manage/templates.rst:43
 #: ../manage/webhook/add.rst:123
-#: ../system/objects.rst:169
-#: ../system/objects.rst:248
+#: ../system/objects.rst:167
+#: ../system/objects.rst:246
 msgid "Active"
 msgstr ""
 
@@ -20914,234 +20914,222 @@ msgid "Updating Database After Adding or Editing Attributes"
 msgstr ""
 
 #: ../system/objects.rst:58
-msgid "When adding or changing attributes, Zammad will not apply the changes instantly, but instead shows you the changed attributes first. If you're ready to go, just click on \"Update database\" to apply the changes to Zammad. If you made a mistake or just want to discard your changes, click \"Discard changes\"."
+msgid "When adding or changing attributes, Zammad will not apply the changes instantly, but instead shows you the changed attributes first. If you're ready to go, just click on \"Update Database\" to apply the changes to Zammad. If you made a mistake or just want to discard your changes, click \"Discard changes\"."
 msgstr ""
 
 #: ../system/objects.rst:64
-msgid "After applying the changes with \"Update Database\", a restart of Zammad is **mandatory**. If you don't perform it, you may experience unexpected behavior or even errors. You may want to do this kind of configuration during maintenance windows."
+msgid "After applying the changes with \"Update Database\", a restart of Zammad is **mandatory**. In most cases, the restart of the service works out of the box (see :docs:`console commands </admin/console/zammad-settings.html>` for more information). However, if your system is configured differently and you don't perform the restart, you may experience unexpected behavior or even errors. You may want to do this kind of configuration during maintenance windows."
 msgstr ""
 
-#: ../system/objects.rst:72
+#: ../system/objects.rst:76
 msgid "Changes on objects require you to update the database to apply these changes."
 msgstr ""
 
-#: ../system/objects.rst:75
-msgid "**🤓 Service restarts can be automated**"
-msgstr ""
-
-#: ../system/objects.rst:0
-msgid "Hosted environments automatically restart for you."
-msgstr ""
-
-#: ../system/objects.rst:0
-msgid "If you're using a self-hosted installation you can use :docs:`environment variables </appendix/configure-env-vars.html>`"
-msgstr ""
-
-#: ../system/objects.rst:82
+#: ../system/objects.rst:80
 msgid "System Attributes"
 msgstr ""
 
-#: ../system/objects.rst:84
+#: ../system/objects.rst:82
 msgid "Zammad comes with pre-configured attributes. Some of them can't be edited via UI (or at all). This is required for proper operation of Zammad and not a bug."
 msgstr ""
 
-#: ../system/objects.rst:90
+#: ../system/objects.rst:88
 msgid "Ticket State"
 msgstr ""
 
-#: ../system/objects.rst:92
+#: ../system/objects.rst:90
 msgid "If the pre-configured states aren't enough for you or you want to change them, you can do so by clicking on the cogwheel icon in the state row in the ticket tab. But you should be careful when changing pre-configured states. This can lead to unwanted behavior in some cases."
 msgstr ""
 
 #: ../system/objects.rst:None
 msgid "Screenshot showing highlighted ticket state attribute"
 msgstr ""
 
-#: ../system/objects.rst:122
+#: ../system/objects.rst:120
 msgid "Handling of states"
 msgstr ""
 
-#: ../system/objects.rst:102
+#: ../system/objects.rst:100
 msgid "In the state configuration screen, you can add new states, disable states or change states."
 msgstr ""
 
 #: ../system/objects.rst:0
 msgid "Screenshot showing table of default ticket states"
 msgstr ""
 
-#: ../system/objects.rst:110
+#: ../system/objects.rst:108
 msgid "To add a new state, click on the \"New Ticket State\" button in the top right corner. To change an existing state, simply click on the affected state. This opens an edit dialog."
 msgstr ""
 
-#: ../system/objects.rst:114
+#: ../system/objects.rst:112
 msgid "You can also clone a state or set them to \"Default for new tickets\" or \"Default for follow-ups\" by clicking on the ⁝ action button and select the desired function."
 msgstr ""
 
-#: ../system/objects.rst:118
+#: ../system/objects.rst:116
 msgid "*Default for new tickets* means that this state is used for every newly created ticket."
 msgstr ""
 
-#: ../system/objects.rst:121
+#: ../system/objects.rst:119
 msgid "*Default for follow-ups* means that this state is used if the ticket is re-opened after it was closed."
 msgstr ""
 
-#: ../system/objects.rst:171
+#: ../system/objects.rst:169
 msgid "Ticket state in detail"
 msgstr ""
 
-#: ../system/objects.rst:125
+#: ../system/objects.rst:123
 msgid "Below you can find a description for each field and option. Please head over to the :ref:`example <example-state>` to see the edit dialog."
 msgstr ""
 
-#: ../system/objects.rst:129
+#: ../system/objects.rst:127
 msgid "This is the name of the state and what you and your agents are seeing when choosing a state somewhere (e.g. in tickets, trigger configuration)."
 msgstr ""
 
-#: ../system/objects.rst:137
+#: ../system/objects.rst:135
 msgid "There are different state types you can choose from. By default, Zammad comes with one state per state type."
 msgstr ""
 
-#: ../system/objects.rst:140
+#: ../system/objects.rst:138
 msgid "**new**: for states for tickets that are new and it hasn't been worked on them"
 msgstr ""
 
-#: ../system/objects.rst:142
+#: ../system/objects.rst:140
 msgid "**open**: for states for tickets that are in progress and agents are working on them"
 msgstr ""
 
-#: ../system/objects.rst:144
+#: ../system/objects.rst:142
 msgid "**merged**: for states for tickets that are merged with other tickets"
 msgstr ""
 
-#: ../system/objects.rst:145
+#: ../system/objects.rst:143
 msgid "**pending reminder**: for states for tickets that are in progress and you want to set a reminder. (default example: *pending reminder*)"
 msgstr ""
 
-#: ../system/objects.rst:147
+#: ../system/objects.rst:145
 msgid "**pending action**: for states for tickets that are waiting for a specified time and then change their state (default example: *pending close*)"
 msgstr ""
 
-#: ../system/objects.rst:150
+#: ../system/objects.rst:148
 msgid "**closed**: for states for tickets that are finished and do not need to be processed further"
 msgstr ""
 
-#: ../system/objects.rst:153
+#: ../system/objects.rst:151
 msgid "⚠️ Choosing the correct state type is important! If you are in doubt, have a look on the default states and their types!"
 msgstr ""
 
-#: ../system/objects.rst:158
+#: ../system/objects.rst:156
 msgid "Ignore escalation"
 msgstr ""
 
-#: ../system/objects.rst:157
+#: ../system/objects.rst:155
 msgid "Here you can define whether tickets of this state will count to escalation time or not."
 msgstr ""
 
-#: ../system/objects.rst:161
+#: ../system/objects.rst:159
 msgid "You can create a note for the state to inform other admins about the state. This has no effect on tickets."
 msgstr ""
 
-#: ../system/objects.rst:165
+#: ../system/objects.rst:163
 msgid "Set the state to *active* or *inactive*."
 msgstr ""
 
-#: ../system/objects.rst:167
+#: ../system/objects.rst:165
 msgid "it is technically possible to set all states to inactive. To keep Zammad working in such a case, the inactive flag of one of the states is ignored."
 msgstr ""
 
-#: ../system/objects.rst:194
+#: ../system/objects.rst:192
 msgid "Ticket state example"
 msgstr ""
 
-#: ../system/objects.rst:174
+#: ../system/objects.rst:172
 msgid "Let's assume we want to create a new state which indicates that the ticket has to wait for a response of a third party (e.g. service contractor or manufacturer) and we want to to be able to set a reminder."
 msgstr ""
 
-#: ../system/objects.rst:178
+#: ../system/objects.rst:176
 msgid "First we give the new state a proper name. In this example we call it \"waiting for manufacturer\"."
 msgstr ""
 
-#: ../system/objects.rst:181
+#: ../system/objects.rst:179
 msgid "As state type we choose \"pending reminder\". This indicates that the ticket is still open and we can set a reminder. This reminder can be useful if our manufacturer sometimes isn't responding or we want to remind him to give us an answer."
 msgstr ""
 
-#: ../system/objects.rst:186
+#: ../system/objects.rst:184
 msgid "We choose \"no\" for \"ignore escalation\" because we want to escalate the tickets even if we are waiting on the manufacturer's feedback."
 msgstr ""
 
-#: ../system/objects.rst:189
+#: ../system/objects.rst:187
 msgid "The **result** in the creation dialog will look like this:"
 msgstr ""
 
 #: ../system/objects.rst:0
 msgid "Screenshot showing ticket state creation dialog with example"
 msgstr ""
 
-#: ../system/objects.rst:199
+#: ../system/objects.rst:197
 msgid "Ticket Priority"
 msgstr ""
 
-#: ../system/objects.rst:201
+#: ../system/objects.rst:199
 msgid "If the pre-configured priorities aren't enough for you or you want to change them, you can do so by clicking on the cogwheel icon in the priority row in the ticket tab:"
 msgstr ""
 
 #: ../system/objects.rst:None
 msgid "Screenshot showing highlighted ticket priority attribute"
 msgstr ""
 
-#: ../system/objects.rst:226
+#: ../system/objects.rst:224
 msgid "Handling of priorities"
 msgstr ""
 
-#: ../system/objects.rst:210
+#: ../system/objects.rst:208
 msgid "In the priority configuration screen, you can add new priorities, disable priorities or change priorities."
 msgstr ""
 
 #: ../system/objects.rst:0
 msgid "Screenshot showing table of default ticket priorities"
 msgstr ""
 
-#: ../system/objects.rst:218
+#: ../system/objects.rst:216
 msgid "To add a new priority, click on the \"New Priority\" button in the top right corner. To change an existing priority, simply click on the affected priority. This opens an edit dialog."
 msgstr ""
 
-#: ../system/objects.rst:222
+#: ../system/objects.rst:220
 msgid "You can also clone a priority or set them to \"Default for new tickets\" by clicking on the ⁝ action button and select the desired function."
 msgstr ""
 
-#: ../system/objects.rst:225
+#: ../system/objects.rst:223
 msgid "*Default for new tickets* means that this priority is used for every newly created ticket."
 msgstr ""
 
-#: ../system/objects.rst:248
+#: ../system/objects.rst:246
 msgid "Priorities in detail"
 msgstr ""
 
-#: ../system/objects.rst:229
+#: ../system/objects.rst:227
 msgid "Below you can find a description for each field and option."
 msgstr ""
 
-#: ../system/objects.rst:232
+#: ../system/objects.rst:230
 msgid "This is the name of the priority and what you and your agents are seeing when choosing a priority somewhere (e.g. in tickets, trigger configuration)."
 msgstr ""
 
-#: ../system/objects.rst:242
+#: ../system/objects.rst:240
 msgid "Highlight color"
 msgstr ""
 
-#: ../system/objects.rst:237
+#: ../system/objects.rst:235
 msgid "Switch between *Low priority* (light blue), *High priority* (red) and - (default). This affects the displayed color for ticket titles in overviews."
 msgstr ""
 
-#: ../system/objects.rst:241
+#: ../system/objects.rst:239
 msgid "The color options are currently limited to the mentioned options."
 msgstr ""
 
-#: ../system/objects.rst:245
+#: ../system/objects.rst:243
 msgid "You can create a note for the priority to inform other admins about the priority. This has no effect on tickets."
 msgstr ""
 
-#: ../system/objects.rst:249
+#: ../system/objects.rst:247
 msgid "Set the priority to *active* or *inactive*."
 msgstr ""
 

system/objects.rst

@@ -57,27 +57,25 @@ Updating Database After Adding or Editing Attributes
 
 When adding or changing attributes, Zammad will not apply the changes instantly,
 but instead shows you the changed attributes first.
-If you're ready to go, just click on "Update database" to apply the changes
+If you're ready to go, just click on "Update Database" to apply the changes
 to Zammad. If you made a mistake or just want to discard your changes, click
 "Discard changes".
 
 After applying the changes with "Update Database", a restart of Zammad
-is **mandatory**. If you don't perform it, you may experience unexpected
-behavior or even errors. You may want to do this kind of configuration
-during maintenance windows.
+is **mandatory**. In most cases, the restart of the service works
+out of the box (see
+:docs:`console commands </admin/console/zammad-settings.html>` for more
+information).
+However, if your system is configured differently and you don't perform the
+restart, you may experience unexpected behavior or even errors. You may want
+to do this kind of configuration during maintenance windows.
 
 .. figure:: /images/system/objects/update-database.png
    :align: center
 
    Changes on objects require you to update the database
    to apply these changes.
 
-.. tip:: **🤓 Service restarts can be automated**
-
-   | Hosted environments automatically restart for you.
-   | If you're using a self-hosted installation you can use
-      :docs:`environment variables </appendix/configure-env-vars.html>`
-
 System Attributes
 -----------------