How legacy metric types are migrated to sections in templates

  • Release version: Australia
  • Updated March 12, 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 How legacy metric types are migrated to sections in templates

    This documentation explains how legacy metric types in ServiceNow's Smart Assessment Engine application are migrated into the new assessment template structure. It details the mappings from old metric types, categories, and definitions to their corresponding sections, questions, and choices within the updated schema. This migration ensures continuity and consistency of assessment data when upgrading or implementing the Australia release version.

    Show full answer Show less

    Metric and Category Mappings

    • Metric Types: Legacy metric types are mapped to specific fields within the assessment template and context item tables—such as Name and Description fields in the snsmartasmttemplate table, and Table Name fields in the snsmartasmtcontextitem table.
    • Metric Categories: These are migrated to the Section table (snsmartasmtsection), mapping fields like Name, Description, and Order to maintain structure and display order in assessment templates.

    Metrics and Question Table Mappings

    • Legacy metrics are mapped to the Question table (snsmartasmtquestion) with key fields such as justification enablement, data type, guidance text, label, mandatory status, numerical limits, and order preserved.
    • All migrated questions default to a data type of Text. Numeric-scale metrics are assigned a Horizontal response layout for consistent user interface behavior.
    • Metric types are mapped to specific question types, for example:
      • Attachment metrics to Attachment questions
      • Likert scales to Radio buttons
      • Multiple selections to Check boxes
      • Yes/No metrics to Radio buttons

    Field and Definition Mappings

    • Fields such as Reference and Condition in legacy tables are migrated to their corresponding fields in the Question table to maintain data integrity and filtering capabilities.
    • Metric definitions are migrated to the Choice table (snsmartasmtresponseoption), with display labels and order preserved according to the original template-definition sequence.

    Assessment Template Specifics

    • Only assessment templates where the Allow image field is set to false are migrated, ensuring compatibility with the new structure.
    • Metrics of data type template are migrated as Radio button questions when Allow image is false at the template level.
    • Assessment template definitions are migrated as choices with display text and order maintained, ensuring a seamless transition of template options.

    Practical Implications for ServiceNow Customers

    Customers upgrading to or using the Australia release can expect their legacy assessment metrics to be accurately mapped to the new Smart Assessment Engine schema. This migration supports continuity of assessment data and functionality without manual reconfiguration. Understanding these mappings helps IT teams anticipate how existing metrics, categories, and templates will translate into the updated system, aiding in troubleshooting and customization post-migration.

    Legacy metric types are migrated to specific sections in the assessment templates in the Smart Assessment Engine application.

    How metric types are mapped

    This tables shows the mapping used to move the existing metric types to the section in the assessment templates.

    Table 1. Metric types for assessment type
    Existing metric type Mapped to
    Name (Translated text) (Max length 255) Name (Translated text) field in the Assessment Template table ((sn_smart_asmt_template) ).
    Description (Translated text) (Max length 1000) Description (Translated html) field in the Assessment Template table ((sn_smart_asmt_template) ).
    Table (Table Name) Table (Table Name) field in the Context Item table (sn_smart_asmt_context_item).

    How metric categories are mapped

    This tables shows the mapping used to move the existing metric categories to the section table in the assessment templates.

    Table 2. Metric categories are mapped to the Section table (sn_smart_asmt_section)
    Existing metric type Mapped to the Section table
    Name (Translated text) (Max length 255) Name (Translated text) field.
    Description (Translated text) (Max length 1000) Description (Translated text) field.
    Order (Integer) Order (Order Index) field.

    How metrics are mapped

    This tables shows the mapping used to move the existing metrics to the question table in the assessment templates.

    Table 3. Metrics are mapped to the Question table (sn_smart_asmt_question)
    Existing metric type Mapped to the Question table
    Allow additional information (True/False) Enable justification (True/False) field.
    Data type (String) (Max length 40) Based on the Data type field value, the appropriate question type reference is added to the Question table. Data type is string.
    Details (Translated html) (Max length 8000) Guidance statement (Translated html) field.
    Question (Translated text) (Max length 512) Label (Translated text) field.
    Mandatory (True/False) Is mandatory (True/False) field
    Max (Integer) Max number (Decimal) field
    Min (Integer) Minimum number (Decimal) field
    Order (Integer) Order (Order index)

    How metric types are migrated to question types

    After migration, all Question records are set as data type Text.

    After migration, all Question records whose source metric is template/Numeric-scale are set with a response layout of Horizontal.

    This tables shows the mapping used to move the existing metric types to the question types in the assessment templates.

    Table 4. Metric type mappings
    Existing metric type Mapped to
    Attachment Attachment
    Choice Drop-down list
    Date Date
    Date/Time Date/Time
    Likert scale Radio button
    Multiple selection Check box
    Numeric scale Radio button
    Reference Reference
    Yes/No Radio button

    How fields are mapped

    This tables shows the mapping used to move the existing fields to the question table in the assessment templates.

    Table 5. Fields are mapped to the Question table (sn_smart_asmt_question)
    Field in the existing table Mapped to the Question table
    Reference table Table field.
    Condition Filter condition field.

    How metric definitions are mapped

    This tables shows the mapping used to move the existing metric definitions to the choice table in the assessment templates.

    Table 6. Metric definitions are mapped to the Choice table (sn_smart_asmt_response_option)
    Metric definition in the existing table Mapped to the Choice table
    Display Text label field in the Choice table (sn_smart_asmt_response_option)
    Order Integer data type is mapped to the Order field in the Choice table that is based on the same ascending sequence of the template-definition records in the Value field that is associated with a particular template.

    How assessment metric templates are mapped

    Only templates where the Allow image field is set to false are migrated. No field mapping is done for this table.

    Metrics whose data type is template are migrated as questions of the type Radio button if the Allow image field is set to false at the template level.

    How assessment template definitions are mapped

    This tables shows the mapping used to move the existing template definitions to the choice table in the assessment templates.

    Table 7. Assessment template definitions are mapped to the Choice table
    Assessment template definition in the existing table Mapped to the Choice table (sn_smart_asmt_response_option)
    Display Text label field.
    Value Integer data type is mapped to the Order field in the Choice table, based on the same ascending sequence of the template-definition records in the Value field that is associated with a particular template.