Principal classes in CMDB success advisor

  • Release version: Zurich
  • Updated June 24, 2026
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Principal classes in CMDB success advisor

    Principal classes in CMDB Success Advisor represent the Configuration Item (CI) classes that your organization considers business-critical. These classes define the scope of the Data Foundations advisor, ensuring your CMDB stays focused and accurate by prioritizing key CI classes. Selecting the right principal classes helps you manage data quality effectively and aligns CMDB insights with your organization’s critical infrastructure.

    Show full answer Show less

    Principal Class Selection and Management

    • CMDB Success Advisor analyzes historical incident, problem, and change (IPC) task data to recommend relevant CI classes for principal designation.
    • You select principal classes from a grouped, recommended list during Data Foundations scope setup, and the system automatically sets them as principal when saved.
    • Continuous monitoring of data quality is available through the Data Foundations advisor dashboard.
    • Managing principal classes directly within CMDB Success Advisor ensures synchronization and dashboard accuracy.

    Customization and Tracking

    With the sncmdbadmin role, you can tailor principal class recommendations using system properties that control:

    • The time range of task history scanned for recommendations (default 180 days).
    • The maximum number of recommended principal classes shown (default 20).
    • Inclusion of custom CI classes not in the predefined scope via a specific property.
    • Optional creation of a property to show a predefined set of common CI classes when no task history exists.

    Synchronization Behavior

    • Data Foundations advisor maintains its own record of principal classes; changes made outside the advisor (via CI Class Manager or elsewhere) do not automatically update the dashboard scope.
    • When principal classes are added or removed outside CMDB Success Advisor, manual updates within the advisor are needed to keep the scope accurate.
    • An out-of-sync notification alerts you to discrepancies when opening the dashboard.

    Impact on CI Filtering and Platform Behavior

    • When configuring advisor scopes, selected principal classes are set in the platform’s CMDB Class Information table.
    • If both Data Foundations and HAM advisors are active, HAM scope is applied first, then Data Foundations.
    • Principal class settings influence ServiceNow AI Platform behavior by filtering Configuration Item fields on task records to show only relevant CIs.
    • The system property com.snc.task.principalclassfilter controls which task types apply this CI filtering; task tables can be excluded from filtering here if necessary.
    • Avoid manually clearing the Principal Class checkbox on CI classes to fix filtering issues, as this disrupts advisor functionality.

    By properly designating and managing principal classes within CMDB Success Advisor, you ensure your CMDB remains aligned with business priorities, data quality is maintained, and task record interactions are optimized for relevant Configuration Items.

    Principal classes are CI classes that your organization treats as business-critical. In CMDB success advisor, the CI classes you select define the Data Foundations advisor scope.

    Selecting the right principal classes keeps your CMDB focused and accurate.

    Principal class selection

    CMDB success advisor processes your instance's history and ranks CI classes by relevance before you set up your Data Foundations advisor scope.

    For information on selecting principal classes, see the Guidance on designating principal classes in the CMDB [KB2707240] article in the Now Support Knowledge Base.

    You can manage the most important CI classes with CMDB success advisor by:

    • Selecting CI classes from the grouped, recommended list in the Data Foundations scope setup. Classes are set as principal automatically when you save.
    • Using intelligent recommendations based on the past incident, problem, and change (IPC) activity on your instance.
    • Monitoring data quality continuously through the Data Foundations advisor dashboard.

    Principal class tracking in CMDB success advisor

    Use the following system properties to customize how CMDB success advisor recommends and manages principal classes. With the sn_cmdb_admin role, you can adjust these properties to control the scope and quality of principal class recommendations.

    Table 1. System properties in CMDB success advisor for principal classes
    Property Purpose
    sn_cmdb_advisor.principal_class_suggestion_period Number of days of task history CMDB success advisor scans when generating class recommendations.

    Default value: 180 days

    sn_cmdb_advisor.suggested_principal_classes_limit Maximum number of recommendations shown in the Recommended group.

    Default value: 20

    sn_cmdb_advisor.principal_class_others

    Comma-separated list of custom CI classes to include in the Others group of the Manage principal classes selection.

    Note:
    Use this property when the custom CI classes aren't available in the predefined Data Foundations advisor scope setup list.
    sn_cmdb_advisor.principal_class_recommendation_criteria Keyword value (PREDEFINED) that displays a standard set of commonly managed CI classes as recommendations on instances with no prior task activity.

    This property does not exist by default and must be created manually.

    The sn_cmdb_advisor.principal_class_recommendation_criteria property is optional. Create it on instances with no prior task activity where task-based recommendations produce no results. Setting the value to PREDEFINED displays a standard set of commonly managed CI classes as recommendations. For instructions, see Create the principal class recommendation criteria property.

    Principal class synchronization

    The Data Foundations advisor stores its own record of which CI classes are in scope. The advisor does not automatically reflect changes to principal class designations made through CI Class Manager or made directly in the instance. A comparison runs when you open the dashboard to identify any discrepancies.

    The following behaviors apply when principal class changes are made outside the advisor:

    • When you set a class as principal outside CMDB success advisor, the class is set as principal on the instance. This applies after the Data Foundations advisor dashboard scope is configured. However, it isn't automatically added to the Data Foundations advisor dashboard scope.
    • When you remove the principal designation from a class outside the advisor, the class remains in the Data Foundations advisor dashboard scope until you remove it manually.

    To keep the Data Foundations advisor dashboard scope accurate, make all principal class updates directly in CMDB success advisor by selecting Manage principal classes on the Data Foundations advisor dashboard. For more information, see Manage Data Foundations advisor scope in CMDB success advisor.

    If other tools or processes change principal classes outside the advisor, an out-of-sync notification appears when you open the Data Foundations advisor dashboard. For more information, see Principal class sync in Data Foundations advisor.

    CI filtering based on principal classes

    When you configure a Data Foundations or HAM advisor scope through auto-setup or manual setup, CMDB success advisor automatically sets the selected CI classes as principal class in the platform CMDB Class Information [cmdb_class_info] table.

    If both products are configured on the same instance, HAM scope is applied first, followed by Data Foundations. If principal classes already exist on the instance, CMDB success advisor preserves those principal classes and adds to the existing selection.

    Principal classes affect ServiceNow AI Platform behavior beyond CMDB success advisor. After a CI class is set as principal, the platform can filter the Configuration Item field on task records so that only CIs that belong to principal classes are available.

    Note:
    CMDB success advisor requires principal classes to define advisor scope and function correctly. The system property com.snc.task.principal_class_filter determines which task types apply the Configuration Item filter. If only a limited set of CIs are seen on task forms such as incidents or change requests, remove the affected task table from the com.snc.task.principal_class_filter system property. Don't clear the Principal Class checkbox on CI classes in the CMDB Class Information [cmdb_class_info] table to resolve task form filtering issues. This change disables principal class filtering for that task type while allowing CMDB success advisor to continue operating correctly. For more information, see Principal Class.