---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Configure inline validation

# Configure inline validation for string fields {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Configure guidance text to display in string fields with format requirements such as account ID, SSN, or SIN. Use regular expression inline validation to display an error message if the input doesn't meet format
requirements.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Guidance text helps you enter data correctly into string fields with format requirements such as account ID, SSN, or SIN. Inline validation uses a regular expression (regex) pattern to enforce format requirements. If the
input doesn't match the required format, an error message displays.  
The process for configuring string fields with guidance text and inline validation requires two steps:

1. Create a regex pattern for a required input format.
2. Map the regex pattern and add guidance text to a string field.
{#format-regex-pattern-string-fields__ol_f11_vnf_k3c}

## Procedimento

1. Create a regex pattern for a required input format.
   1. Navigate to <kbd class="ph userinput">sys_ui_regex.list</kbd>.  
      The entire list of regex tables from the Regex Tables \[sys_ui_regex\] table opens.
   2. Select New.  
      A new Regex Table record opens.
   3. Complete the following fields:  

      Name
      :   Create a descriptive name for the regex pattern. For example, if you're creating a regex pattern for an account number, enter <kbd class="ph userinput">Account Number</kbd>.

      Regex pattern
      :   Enter the regex pattern that defines the required input format. This field is required. For example, you might use `^\d{10}$` to require a 10-digit number.
   4. Select Submit.
   {#format-regex-pattern-string-fields__substeps_uxc_1mg_bgc}
2. Map the regex pattern and add guidance text to a string field.
   1. Navigate to <kbd class="ph userinput">sys_ui_field_regex_mapping.list</kbd>.  
      The entire list of mapping tables from the Field Regex Mapping Tables \[sys_ui_field_regex_mapping\] table opens.
   2. Select New.  
      A new Field Regex Mapping Table record opens.
   3. Complete the following fields:  

      Table
      :   Select the table that contains the string field you want to apply validation and guidance to.

      Field name
      :   Select the string field from the list.

      Placeholder Text
      :   Enter sample text to display in the field as an example of the required format.

      Field message
      :   Enter guidance text that explains the format requirement or gives additional instructions.

      Field message type
      :   Select the type of guidance text to indicate whether it's a suggestion, information, warning, positive message, or critical.

      Order
      :   Enter a number to set the display priority of the guidance text. Lower numbers appear first.

      Active
      :   Select this check box to enable the validation and guidance text.

      Inherited
      :   Select this check box to apply the validation and guidance text to child tables with the same field.
   4. From the Input Validation Rules section, complete the following fields:  

      Regex Pattern
      :   Select the regex pattern that matches the required format.

      Input Format
      :   Use the Input Format Guide to enter an input format.  
          {#format-regex-pattern-string-fields__table_esy_ggz_m3c__entry__2}

          | Symbols | Input Format |
          |-|-|
          | <kbd class="ph userinput">0</kbd> | Accepts any digit (0-9) |
          | <kbd class="ph userinput">a</kbd> | Accepts any letter (A-Z or a-z) |
          | <kbd class="ph userinput">*</kbd> | Accepts any characters, letters, digits, or symbols. |
          | <kbd class="ph userinput">[]</kbd> | Makes input optional |
          | <kbd class="ph userinput">{}</kbd> | Includes a fixed part in an unmasked value |
          | <kbd class="ph userinput">`</kbd> | Prevents symbols from shifting back |
          | <kbd class="ph userinput">\\</kbd> | Shows a symbol as-is For example, <kbd class="ph userinput">\\0</kbd> requires the number zero as 0. |
          [Tabela 1. Input Format GuideUse the following symbols to define how users should enter data in the field.]

          {#format-regex-pattern-string-fields__table_esy_ggz_m3c}

          For example, to accept a phone number in the format +91-12345-67890, enter the input format as <kbd class="ph userinput">{+91-}00000-00000</kbd>.

          To accept an ID in the format EMP-1234, enter the
          input format as <kbd class="ph userinput">{EMP-}0000</kbd>
   5. Select Submit.
   {#format-regex-pattern-string-fields__substeps_gts_jng_bgc}
{#format-regex-pattern-string-fields__steps_g11_vnf_k3c}