---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Manage upgrades

# Managing principal class marking during upgrade {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Make sure that existing Hardware Asset Management (HAM) CI classes are included as principal classes in Data Foundations during upgrade, without requiring manual configuration.

Upgrading to a version of CMDB success advisor that introduces the Data Foundations principal class concept can result in CI classes being automatically marked as principal classes when existing HAM model category selections are present.

In CMDB success advisor, each HAM model category maps to one or more CI classes.

For example, if you selected the Computers model category, the cmdb_ci_computer class was included. Before the upgrade, these classes were used only for HAM data quality tracking.

After you upgrade to a version that includes Data Foundations, CMDB success advisor automatically marks those same CI classes as principal classes. This gives you a starting point for Data Foundations without requiring manual configuration.

## Upgrade impact {#cmdb-sa-df-upgrade__section_ns4_wxr_k3c}

The following table shows how principal classes from HAM model categories are applied across key features in Data Foundations after upgrade.
{#cmdb-sa-df-upgrade__table_cbg_wxr_k3c__entry__2}

| Feature | Impact after upgrade |
|-|-|
| Principal classes list | Your Data Foundations principal classes list is already populated with CI classes from your HAM model category selections. |
| CI picker on task records | On incidents, problems, and changes, the CI picker shows only CIs from your principal classes. |
| Data Foundations dashboard | Your Data Foundations advisor dashboard may already display data using the HAM derived principal classes as the initial scope. |
[Tabelle : 1. Principal class updates by feature]

{#cmdb-sa-df-upgrade__table_cbg_wxr_k3c}

## Recommended actions {#cmdb-sa-df-upgrade__section_bpm_pyr_k3c}

1. Go to CMDB success advisor landing page, and on the Data Foundations card, select Edit principal classes to review automatically marked classes.

   See [Manage Data Foundations advisor scope in CMDB success advisor](https://servicenow-prod.fluidtopics.net/wtNWaVR7ZaneOQeHiG69nw "Manage the scope of your advisor for Data Foundations by editing principal classes in CMDB success advisor to support your targeted Data Foundations outcomes.").
2. Confirm that the marked classes align with your Data Foundations advisor scope. Remove any unwanted classes and add others as needed (up to 50 principal classes).
3. If CI picker filtering affects users, adjust behavior using the system properties for CMDB success advisor.

   See [Principal class tracking in CMDB success advisor](https://servicenow-prod.fluidtopics.net/XEZ2dhZg8n8RoBoXOUW1Jw#cmdb-sa-principal-class__section_pky_rf2_k3c).

{#cmdb-sa-df-upgrade__ol_cpm_pyr_k3c}  
Hinweis:  
Automatic principal class marking happens only once during upgrade. Later changes to HAM model categories do not update the principal classes list automatically. Similarly, principal class changes made without using CMDB success advisor, for example through CI Class Manager, are not reflected in the Data Foundations advisor scope automatically.