Convert legacy custom Discovery identifiers Custom identifiers created in a prior release must be converted to CMDB identifier rules after an upgrade to Geneva to use the new unified framework. Before you beginRole required: adminWhen you upgrade to Geneva, your scheduled discoveries can continue to use the identifiers they were configured to use, including any custom identifiers you have created. You can use the CMDB identifiers provided with the Geneva release for new Discoveries or continue to use the legacy identifiers. If you elect to use the CMDB identifiers and want to use a custom identifier you created in an earlier version, you can convert that legacy identifier to a new identifier rule manually. Note: To restrict Discovery to use only the CMDB identifiers, you can add a property to the sys_properties table and set it to hide legacy identifiers.This example uses the serial_number and serial_number_type attributes from the hardware identifier. Procedure Navigate to Discovery Definition > CI Identification > Identifiers. Open the record for the custom legacy identifier and note the table in the Applies to field. For example, the identifier might be on the Hardware [cmdb_ci_hardware] table. Determine if the script in the legacy identifier is configured to query another table for matches. In this example, the Serial Number Table & Class Name identifier is configured to query the Serial Number [cmdb_ci_serial_number] table for a matching serial number. In CMDB identifier rules, this is known as the Search on table. Figure 1. Table queried for matching attributes Locate the attributes the script uses as unique identifiers. In this example, the serial_number and serial_number_type fields are the unique identifiers on the Serial Number [cmdb_ci_serial_number] table. Figure 2. Unique identifiers Identify any filtering conditions the script applies to the attributes. In this example, serial numbers must be valid and the field cannot be blank. Figure 3. Attribute conditions Navigate to Configuration > Identification/Reconciliation > CI Identifiers and click New. Enter a descriptive name for the identifier, using the class name. For example, you might use Linux Server. Select the same table in the Applies to field that your custom legacy identifier specified. Submit the form. Open the new identifier record and click New in the Identifier Entries related list. Complete the form for the attributes from this query table. Remember to give your new rule a unique priority number to establish its parsing order. Table 1. Identifier entry fields Field Description Criterion attributes Attributes to use as unique identifiers. These are the values you located in step 4. Click the lock icon to add one or more attributes to the list. Optional condition Filter conditions for the attribute from the legacy identifier. These are the values you located in step 5. Search on table Table to query for the attribute value. This is the table you identified in step 3. Figure 4. Identifier entry form Click Submit. Create additional identifier entries for any other attributes from your custom legacy identifier.