---
sourceDocument: Xanadu ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/servicenow-platform

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# View configurations, view templates, and configuration bundles

# View configurations, view templates, and configuration bundles for EVAM {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A view configuration combines conditions, database fields, and declarative actions with
an associated view template. You can also group view configurations together to create
configuration bundles.  
EVAM has pre-defined view configurations, view templates, and configuration bundles to make it easier to use the feature. The OOB configuration bundles include:

* Service Portal Search Bundle
* Service Portal bundle (sp_bundle)
{#use-configuration-bundle__ul_zhh_vlx_vnb}These bundles have view configurations attached that are anticipated to fit the business unit associated. You can also create or edit configuration bundles to meet your needs.

View configurations have an associated view template, tables and conditions, designated table
field with data, and associated declarative actions. You can look at the
demo_evam_dataset for examples of OOB configuration views. These view configurations are
ready to use and are meant to work with many use cases. You can also create or edit view
configurations to meet specific needs.  
The OOB view templates match an associated view configuration. The templates contain the JSON used to give the necessary information for the card display and use. For example, the Attachment Search Template contains the following:

    {
        "component": "sn-search-result-evam-card",
        "staticValues":  {
            "detailLabelType": {
                "translatable": false,
                "key": "inline"
            },
            "textHeaderLabelOne": {
                "translatable": true,
                "key": "Attachment"
            },
            "detailLabelOne": {
                "translatable": true,
                "key": "From:"
            }
        },
        "mappings": {
            "imageType": "doctype_image_type",
            "icon": "doctype_image",
            "imageURL":"doctype_image",
            "textHeaderLabelTwo": "doctype",
            "title": "ai_search_teaser_title",
            "summary": "ai_search_teaser_text",
            "detailValueOne":"parent_title"
        },
        "actionMappings": {
            "clickAction": "navigation",
            "footerLinkAction": "navigation_to_parent_record"
        }
    }

The JSON structure has the following sections: {#use-configuration-bundle__table_p1k_svl_xnb__entry__2}

| Template | Description |
|-|-|
| component | The card component name. |
| staticValues | The static text mapping to component properties. These values have the following properties: * translatable -- Determines whether the key text should be translated based on the users language.Can be either True or False. * key -- The value the property is set to. {#use-configuration-bundle__ul_yyy_q2m_xnb} |
| mappings | The mapping of the datasource field to the component properties. |
| actionMappings | The actions that you can associate to the card. |
[ ]

{#use-configuration-bundle__table_p1k_svl_xnb}These view templates are ready to use and are meant to work with many use cases. You can also create or edit view templates to meet specific needs.