---
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


---

# Create a multi-data source list display

# Create a multi-data source list display in Entity View Action Mapper {#ariaid-title1}

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

Use EVAM to take in different datasources, configure views, and show them in a card display view.

## Vorbereitungen

Role required: admin or evam_admin

## Warum und wann dieser Vorgang ausgeführt wird

A typical scenario is showing user requests and incidents in a single display view. A user might want to see requests that can be made from a catalog, such as a computer order. They also might want to see open or closed
incidents. These items come from different data sources, but need to display through a consistent standard that can be easily configured.  
This tutorial runs through creating an EVAM definition with two data sources, a configuration bundle for each data source which contains two view configurations, and associated actions and view templates. Many tasks are repeated, instead of repeating each step, the following table lists the unique configurations and definitions:{#tutorial-create-evam__table_qsy_x2w_xnb__entry__6}

| EVAM definition | Data source \[Table\] | Configuration bundle | Action | Configuration view | View template |
|-|-|-|-|-|-|
| User Requests | Catalog Requests \[Requested Item\] | Catalog Request Bundle | Navigation | Open Requests | Open Request Template |
| User Requests | Catalog Requests \[Requested Item\] | Catalog Request Bundle | Navigation | Closed Requests | Closed Request Template |
| User Requests | Incidents Submitted \[Incidents\] | Incidents Submitted Bundle | Navigation | Open Incidents | Open Incidents Template |
| User Requests | Incidents Submitted \[Incidents\] | Incidents Submitted Bundle | Navigation | Closed Incidents | Closed Incidents Template |
[ ]

{#tutorial-create-evam__table_qsy_x2w_xnb}

## Prozedur

1. [Create an EVAM definition for user
   requests](https://servicenow-prod.fluidtopics.net/SF9lIXmKQferJbzAX6ivEw "Define the list of data sources to render. The Entity View Action Mapper (EVAM) definition is the main record for an EVAM configuration.").  
   An EVAM definition houses data sources, configuration bundles with associated view configurations, data filters, actions, and templates. After you initially submit your EVAM definition, you will see the related lists to add data sources, configuration bundles, and data filters.   

2. [Define data sources for your EVAM definition](https://servicenow-prod.fluidtopics.net/jQ0vkipedzlOZ3~GqZMm9A "The data source is an entity that has associated data that you intend to display. For example, a community post or a user.").  
   Create and link each data source to the User Request definition. The initial data source is for catalog requests. You can also make one for incidents submitted.  

3. [Create and link a view
   configuration bundle](https://servicenow-prod.fluidtopics.net/6D066NiwH_xSk8Ke84jBIQ "Create a view configuration to combine conditions, database fields, and declarative actions with an associated view template using the Entity View Action Mapper (EVAM).").  
   You should create two configuration bundles, a catalog request bundle and an incidents submitted bundle.  

4. [Create an action definition](https://servicenow-prod.fluidtopics.net/VG8ueKWZnRzYeuG0mwvK9Q "You can associate a declarative action with a view template. The Entity View Action Mapper (EVAM) also enables user interactions to trigger a server script or UXF client action.").  
   You can use the create and link related list.   

5. [Create view templates](https://servicenow-prod.fluidtopics.net/_SQiS8id9YfwLQF1UokEsw "You can configure multiple view templates per data source based on conditions to customize how data displays for users. The view template maps fields from the view configuration to component.") for requested items and associate with the view configuration.  
   Here is the template info for the Requested Items Template:

       {
       	"component": "now-card-evam-record",
       	"staticValues": {
       		"highlightedHeaderIcon": {
       			"key": "clock-outline"
       		},
       		"highlightedHeaderBkgColor": {
       			"key": "positive"
       		},
       		"imageType": {
       			"key": "image"
               },
       		"detailLabelOne": {
       			"translatable": true,
       			"key": "created"
       		},
       		"detailLabelTwo": {
       			"translatable": true,
       			"key": "number"
               }
       	},
       	"mappings": {
       		"highlightedHeaderLabel": "state",
       		"titleLabel": "cat_item.name",
       		"imageURL": "cat_item.picture",
       		"subtitle": "cat_item.short_description",
       		"detailValueOne": "sys_created_on",
       		"detailValueTwo": "number"
       	},
       	"actionMappings": {
       		"clickAction": "navigation"
       	}
       }

6. Repeat steps 3-5 to add another view configuration for closed requests.  
   You created a configuration bundle with one view configuration. Add another configuration called Closed requests. This view configuration references the same data source \[requested item\], but uses different conditions to show ().
7. Associate view templates to view configurations, select Update.
8. View your finished product.  

   <br />