

Custom Ticket Fields, while incredibly useful, are not equally available as conditions across business rules and views. This article will help show you what custom field type and conditions you can use in business rules and views and how.
This article contains the following sections:
Permitted business rules and view conditions
The table below provides a reference for the different business rules and views conditions and their permitted custom field type.
|
Custom Field Type |
Trigger |
Automation Conditions |
SLA |
View |
|
Drop-down Field |
|
|
|
|
|
Multi- Field |
|
|
|
|
|
Text |
|
Not Available | Not Available | Not Available |
|
Multi-line Text |
|
Not Available | Not Available | Not Available |
| Numeric |
|
Not Available | Not Available | Not Available |
| Decimal |
|
Not Available | Not Available | Not Available |
| Checkbox |
|
|
|
|
| Date |
|
|
|
|
| Regular Expression |
|
Not Available | Not Available | Not Available |
About custom ticket fields in business rules and views
This section will provide more information on individual custom ticket fields and their availability with business rules and views.
Drop-down fields
Custom drop-down field options are available for use across all views and business rules. Drop-down field options have a finite amount of predefined value options. For more information on drop-down ticket fields, see Best Practices for altering Ticket Fields
When using drop-down fields within conditions, the field will appear as follows:

Multi-select fields
Multi-select fields provide the option to choose multiple values from a list. This can then leverage the values set for the field equally across all business rules and views. You can either select to check for the presence of any value for the field or more granularly for specific values. Below you will find two examples:

If you would prefer to check for the presence of a specific value for the multi-select field, field values may be selected as individual conditions:

Text, multi-line text, numeric, and decimal fields
Custom text fields, multi-line text fields, numeric and decimal fields are only available for use as an option with triggers. It is only possible to check whether the value is present or not present. The actual content of these fields cannot be matched with any string or specific words.
When using these types of fields within conditions, they will appear as follows:

Checkboxes
Checkboxes are available across all business rules and views. For use in automations and views, you will need to ensure that your checkbox includes a tag. If your checkbox does not add a tag when checked, checkboxes will not appear as an option for use in automations and views.

When using a checkbox within conditions, they will appear as follows:

Comments
0 comments
Please sign in to leave a comment.