---
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


---

# Create a Discovery process classification

# Create a Discovery process classification {#ariaid-title1}

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

A process classification allows Discovery to create a particular CI type from information gathered during the identification and exploration phases. {#t_CreateAProcessClassification__ph_short-desc}

## Before you begin

Role required: none

## About this task

When a process matches the classification criteria, Discovery uses the process classification record to create a CI. You can also have Discovery update existing CIs
or ignore certain processes by creating a [process
handler](https://servicenow-prod.fluidtopics.net/McZJhsBzsxBkjMOHJDCcOQ "Process handlers prevent the creation of duplicate CIs by filtering out parameters known to have inconsistent values before process classification occurs. You can create new classifiers or edit existing ones.").{#t_CreateAProcessClassification__ph_create-cis}  
Note:  
There is no support for dot-walk on the parent running the process command.

## Procedure

1. Navigate to AllDiscovery DefinitionCI ClassificationProcesses.
2. Click New.
3. Enter the classification fields (see table).  
   {#t_CreateAProcessClassification__table_ofm_py5_1q__entry__2}

   | Field | Input value |
   |-|-|
   | Table | Select the table where this classification generates CI records. This table must be an extension of the Applications \[cmdb_ci_appl\] table. |
   | Relation type | Select the CI relationship type for this classification. The relationship field is only available for Process and Scan Application classifications. Discovery process classifications typically use one of these relationship types: * Runs on::Runs: Defines the relationship of an application to the host on which it runs. This relationship is expressed from the perspective of the host and the application. For example: My database application runs on server001::server001 runs my database application. * Depends on::Used by: Defines the relationship of an application that communicates with another application. This relationship is expressed from the perspective of each application. For example: The Tomcat application depends on the MySQL database:: The MySQL database is used by Tomcat. * Virtualized by::Virtualizes: Defines the relationship of a virtual machine to its host. This relationship is expressed from the perspective of the virtual machine and of the host. For example: server001 is virtualized by Server ESX::Server ESX virtualizes server001. {#t_CreateAProcessClassification__ul_ojj_yy5_1q} |
   | Active | Select this option to enable the process classification record. Only active process classifications can create application CI records. |
   | Order | Enter the order in which Discovery should run this process classification when there are multiple classifications available for a table. Discovery runs process classifications from the lowest to highest order. |
   | Test with | Lists the host CI where an automatically generated process classification conditioncons were met. Use this field to test changes to the process classification to ensure that the updated classification behaves as expected. |
   | Condition | Use the condition builder to create the match and classification criteria for the process classification. This field replaces both the Match criteria field and Classification Criteria related list. The upgrade process converts all existing classification criteria into conditions. Note: Condition filters in process classifiers are case-sensitive. Note: Only these conditions work: * name * PID * PPID * command * parameters * listening_on_ports * connecting_to_ports * connecting_to * key_parameters * classify {#t_CreateAProcessClassification__ul_pw5_t4g_3mb} |
   | On classification script | Enter a script to run when the condition and classification criteria are met. Use this script to perform any special tasks after a device is classified. It is possible to use the `g_probe_parameters` hashmap from within a classification script to set probe parameters for any configured, triggered probes. For example, this code sets a `'node_port'` parameter to 16001 for all triggered probes. `g_probe_parameters['node_port'] = 16001;` See [On classification script objects for Discovery](https://servicenow-prod.fluidtopics.net/IKmMX1oJVjWuzD0~ta_9aQ "Use an On classification script in a process classifier to customize an application record.") for more examples and for a list of the objects you can use in this kind of script. |
   | Triggers probes | Select the exploration probes you want Discovery to launch. These probes gather detailed information about a classified CI. Discovery will not launch these probes when it is configured to stop after classification. If you want to use patterns for horizontal discovery, add the [Horizontal Pattern](https://servicenow-prod.fluidtopics.net/B9BrAmPVduyP_ToCMHpbFg "Discovery uses the Horizontal Pattern probe to launch patterns for horizontal discovery.") probe in the Probe column, and then specify your pattern in the Pattern column. Warning: Do not specify your pattern in the Probe column. You must choose the Horizontal Pattern probe which launches the specified pattern. |
   | Applications | Use this related list to view the application CIs that match this process classification. |
   | Test results | Use this related list to view the how Discovery classifies processes on the Test with host and build better classification conditions. |
   | Parameters | Use this related list to view the parameters associated with this process and build better classification conditions. See [Discovery classification parameters](https://servicenow-prod.fluidtopics.net/MUt~FEg8Q5OS2Uhy_tjoIg "These parameters are available for Discovery classifiers.") for a list of the parameters you can use. |
   | Versions | Use this related list to view previous versions of the process classification record. |
   [Table 1. Classification fields]

   {#t_CreateAProcessClassification__table_ofm_py5_1q}
4. Right-click the header bar and click Save.
5. Enter items from related lists.
6. Click Update.

## Example

Figure 1. An example process classification record

## What to do next

Run a discovery through the [Discovery
Schedule](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.") to search for applications. You can also [create or modify process
handlers](https://servicenow-prod.fluidtopics.net/McZJhsBzsxBkjMOHJDCcOQ "Process handlers prevent the creation of duplicate CIs by filtering out parameters known to have inconsistent values before process classification occurs. You can create new classifiers or edit existing ones.") that prevent the creation of duplicate CIs based on process classifiers if that is an issue for your environment.

*[\>]: and then