---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Custom alert fields

# Custom alert fields {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can populate custom alert fields with data contained in Additional information field of the event.

Valuable data contained in Additional information fields of events can be useful, for example, for reporting. Alert fields are automatically populated from fields that have the same name in the event. This
behavior holds true for Additional information event fields and for Additional information fields that Event Rule adds. Therefore, to populate a custom alert field with the value in
Additional information fields, use the custom field name in the Additional information field. You can also use Event Rules for this purpose. Values in the Additional information field of an Event that are not in JSON key/value format are normalized to JSON format when the event is processed. For more
information, see [Configure an event rule to customize alert content](https://servicenow-prod.fluidtopics.net/y3wetDYMwXph7QgT~DFEhg "You can configure an event rule to customize alert content. You can customize the order of the fields and select which fields display. The fields in the left-hand work area of the Transform and Compose Alert Output section of an event rule are the fields that appear in the generated alert.").

The short description field of an alert is automatically written using the type, node,
and description of the alert. To prevent the short description field from being
over-written, open the sys_properties table, locate the
evt_mgmt.override_alert_short_description property, change the
value to <kbd class="ph userinput">false</kbd>, and then click Update.  
Depending on permissions, you may only be able to create fields with the user_ prefix. If so, use Event Rules to create an Additional information field with the same name. To prevent some fields to be copied to the alert field, use the evt_mgmt.alert_black_list_fields property and add the field names that must be excluded. By default, the fields that are not copied are:

* message_key
* category
* additional_info
* sys_updated_on
* sys_updated_by
* sys_created_by
* sys_created_on
* sys_mod_count
* sys_id
{#populate-custom-alert-fields__ul_epz_bd2_xw}