---
sourceDocument: Yokohama ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-administration

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create a skipped record rule

# Create a skipped record rule {#ariaid-title1}

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

Create skipped record rules based on your set conditions to define your customizations after an upgrade.

## Before you begin

Role required: admin

## Procedure

1. Navigate to Skipped Rules using one of the following ways.  
   {#um-create-skipped-record-rule__table_onw_2nr_hdc__entry__2}

   | Option | Navigation |
   |-|-|
   | Using left navigation | Navigate to AllAdmin CenterUpgrade ManagementSkipped Rules. |
   | Using Admin tab option | Navigate to AdminUpgrade ManagementSkipped Rules. |
   [ ]

   {#um-create-skipped-record-rule__table_onw_2nr_hdc}  
   A list of available rules shows up.  
   Note:  
   By default, a few inactive sample rules have been provided. You can set it to active if you want to use the sample rules.
2. Select New to create a new skipped record rule.  
   The Upgrade Skipped Record Rules form shows up.  
   Note:  
   The new rules are active by default. You can make them inactive if you don't want to use them.
3. Fill in the fields on the form.  
   {#um-create-skipped-record-rule__table_lhx_vd3_1nb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the rule. |
   | Order | Order in which the rule runs. Note: The order number automatically increments from the last rule order created. |
   | Active | Option to activate the rule. |
   | Conditions | Conditions as to when the rules are implemented on the skipped records. Note: These conditions are only for skipped records that are not being reviewed. If you set the disposition condition to anything other than the skipped records, that condition doesn't work. |
   | Action | Option to choose one of the four following actions: * Keep My Modifications (Always Retain) * Revert and Keep Inactive * Assign Skipped Records to User * Assign Tags to Skipped Records {#um-create-skipped-record-rule__ul_qsd_hrs_kxb} Note: Based on the selected action, a message shows up with more information. |
   | Comment | Add a comment on the conditions being set. |
   [ ]

   {#um-create-skipped-record-rule__table_lhx_vd3_1nb}
4. Select Submit.  
   The new rule appears on the list of available rules.
{#um-create-skipped-record-rule__steps_jhw_v1l_hdc}

## What to do next

You can now run the skipped record rules either automatically during an upgrade or can run on demand on the skipped records. See [Execute a skipped record rule](https://www.servicenow.com/docs/IDCooT4SD4EAZOunX~c6EA#um-execute-skipped-record-rule "Run skipped record rules based on your set conditions to resolve skipped records in an upgrade. The rules either execute automatically during an upgrade or can run on demand after an upgrade.") for more information.
**Related tasks**   

* [Execute a skipped record rule](https://www.servicenow.com/docs/IDCooT4SD4EAZOunX~c6EA#um-execute-skipped-record-rule "Run skipped record rules based on your set conditions to resolve skipped records in an upgrade. The rules either execute automatically during an upgrade or can run on demand after an upgrade.")

*[\>]: and then