Source string Read only

7/100
Context English State
Click on the *Create New Escalation Type Bundle* button in the left sidebar.
Fill in the required fields.
Click on the *Create* button.
You will be redirected to *Edit Escalation Type Bundle* screen to edit the escalation type bundle details.
Create New Escalation Type Bundle Screen
To edit an escalation type bundle:
Click on an escalation type bundle in the list of escalation types bundles or you are already redirected here from *Create New Escalation Type Bundle* screen.
Modify the fields and the escalation type bundle details.
Edit Escalation Type Bundle Screen
To delete an escalation type bundle:
Click on the trash icon in the *Delete* column.
Click on the *OK* button in the confirmation dialog.
Delete Escalation Type Bundle Screen
Escalation Type Bundle Settings
The following settings are available when adding or editing this resource. The fields marked with an asterisk are mandatory.
Name \*
The name of this resource. Any type of characters can be entered to this field including uppercase letters and spaces. The name will be displayed in the overview table.
Comment
Add additional information to this resource. It is recommended to always fill this field as a description of the resource with a full sentence for better clarity, because the comment will be also displayed in the overview table.
Description
Longer text can be added here to describe the escalation type bundle.
Customers
Select a customer from the drop-down list. If one or more customers are selected, the bundle will only take effect on tickets which are assigned to one of the selected customers.
Priorities
Select a priority from the drop-down list. If one or more priorities are selected, the bundle will only take effect on tickets which matches one of the selected priorities.
Services
Select a service from the drop-down list. If one or more services are selected, the bundle will only take effect on tickets which matches one of the selected services.
Execution order \*
The execution order takes place, when at least two bundles could start based on the types and the attributes of the ticket. Only one bundle can be used though. The execution order will change the priority of the bundle, so that the bundle with higher priority will be used.
Validity \*
Set the validity of this resource. Each resource can be used in OTRS only, if this field is set to *valid*. Setting this field to *invalid* or *invalid-temporarily* will disable the use of the resource.
ComponentTranslation
This translation Translated OTRS 7/Feature Add-ons Manual Name \*
The following strings have the same context and source.
Translated OTRS 7/OTRS::ITSM Manual Name \*
Translated OTRS 7/Administration Manual Name \*
Translated OTRS 7/User Manual Name \*

Loading…

User avatar None

New source string

OTRS 7 / Feature Add-ons ManualEnglish

New source string a year ago
Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Flags
read-only
Source string location
../../content/advanced-escalations/admin/ticket-settings/escalation-type-bundle.rst:61 ../../content/advanced-escalations/admin/ticket-settings/escalation-types.rst:68 ../../content/calendar-resource-planning/agent/calendar/manage-teams.rst:83 ../../content/dynamic-field-database/admin/processes-automation/dynamic-fields.rst:35 ../../content/dynamic-sender-addresses/admin/communication-notifications/sender-address-mapping.rst:71 ../../content/ticket-forms/admin/ticket-settings/dynamic-ticket-templates.rst:62 ../../content/ticket-invoker/admin/processes-automation/web-services.rst:107 ../../content/ticket-workflow/admin/ticket-settings/ticket-workflows.rst:128 ../../content/ticket-workflow/admin/ticket-settings/ticket-workflows.rst:148
String age
a year ago
Source string age
a year ago
Translation file
locale/content.pot, string 373