Exploring Entity View Action Mapper

  • 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 Exploring Entity View Action Mapper

    The Entity View Action Mapper (EVAM) is a tool that enhances how various data sources are displayed in ServiceNow, allowing users to view information in card grids or list formats. It simplifies the integration of multiple data sources into a single view, eliminating the need for custom implementations.

    Show full answer Show less

    Key Features

    • Multiple Data Sources: EVAM can integrate multiple disparate data sources into a single list view, enabling efficient sorting and filtering.
    • View Templates: Users can define view templates that dictate how data is presented, allowing for customization based on specific conditions.
    • View Configurations: Create complex view configurations that combine conditions, database fields, and actions, which can be grouped into bundles.
    • User Interaction: EVAM allows users to trigger server scripts or client actions directly from the interface, enhancing interactivity.

    Key Outcomes

    EVAM benefits various user roles:

    • Service Desk Agents: Quickly manage incidents and tasks across multiple tables.
    • IT Support Staff: Monitor and manage IT assets and service requests more effectively.
    • Managers: Access key performance indicators and team workloads in a streamlined format.
    • Customer Service Representatives: Improve response times by efficiently interacting with customer data.
    • Business Analysts: Optimize processes by configuring views from multiple data sources.
    • Developers and Admins: Create tailored views to ensure relevant data is easily accessible.

    EVAM's workflow involves defining entities, mapping data to views, and allowing actions to be performed through mapped components, which ultimately enhances usability and data presentation.

    The Entity View Action Mapper (EVAM) is an application that standardizes how different data sources display in cards and lists.

    EVAM overview

    EVAM enables you to show information as a card grid view or as a list of information in a list view. Users can page through large data sets of search results and see different views based on filtering.

    Prior to EVAM, lists were restricted to a single type of data source. If there were more data sources, you would have to write a custom implementation. EVAM enables you ingest multiple lists from different data sources, and then configure specific views without the need for customization.
    Platform card displays

    Features of EVAM

    Use multiple data sources for a single list view
    EVAM can accept multiple disparate data sources and configure the data through sorting and filtering to return the data as a single list.
    Define view templates
    Map the data source output to a UX component view by using view templates. You can configure multiple view templates per data source based on a condition to customize how data displays for users.
    Create view configurations to combine conditions, database fields, and declarative actions
    Create a view configuration to combine conditions, database fields, and declarative actions with an associated view template. You can also group view configurations together to create configuration bundles.
    Enable user interactions to trigger actions
    EVAM enables user interactions to trigger a server script or UXF client action.

    EVAM users

    User Description
    Service desk agents Service desk agents need a streamlined way to view and manage incidents, requests, and tasks across different tables. EVAM allows them to filter, sort, and take action on records quickly.
    IT support staff IT teams use EVAM to monitor and manage IT assets, service requests, and incidents by consolidating information into a structured, actionable interface.
    Managers and team leads Supervisors overseeing teams or operations benefit from EVAM's ability to present key performance indicators and open tasks and team workloads in an easy-to-navigate format.
    Customer service representatives Customer support teams interact with cases, accounts, and customer information efficiently, improving response times and service quality through EVAM.
    Business analysts and process owners Analysts use EVAM to configure views that bring together data from multiple sources, enabling better decision-making and process optimization.
    Developers and admins Developers and system administrators configure EVAM to create custom views, ensuring the right data is surfaced to the right users for improved usability.

    EVAM workflow

    EVAM consists of the following:
    • Entity (data source) - The entity that has associated data that you intend to display. For example, a community post or a user.
    • View – A view is how a card displays data and actions.
    • Actions – An entity can have an action that performs on the card. For example, you can activate a user into your system.
    • Map – The mapping process maps the data source data to component properties that display on the card. You can also associate actions that trigger from the card view.
    Figure 1. EVAM workflow

    EVAM workflow overview
    1. Entity: examples include a community post or sys_user
    2. Mapping: fields found in an entity
    3. View/Action: locations or actions that entity fields are mapped to

    EVAM benefits

    Benefit Feature Users
    Allows users to 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. Define an EVAM view template Admins or evam_admins
    Use EVAM to take in different data sources, configure views, and show them in a card display view. Create a multi-data source list display in Entity View Action Mapper Admins or evam_admins
    Define the list of data sources to render. The EVAM definition is the main record for an EVAM configuration. Create an EVAM definition Admins or evam_admins
    Define the list of data sources to render. The EVAM definition is the main record for an EVAM configuration. Create an EVAM action definition Admins or evam_admins

    What to explore next

    To learn more about configuring and using EVAM, see: