Exploring Entity View Action Mapper
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 ServiceNow application designed to standardize how information from multiple data sources is displayed in card or list views. EVAM enables users to view large datasets with filtering and pagination, consolidating data from different sources into a single, configurable interface without custom development. This capability streamlines data presentation and interaction across various user roles.
Show less
Key Features
- Multi-Source List View: EVAM can ingest multiple disparate data sources and merge them into a single list view with sorting and filtering applied.
- View Templates: Allows mapping of data source outputs to user experience components through configurable view templates, with support for multiple templates per data source based on conditions to tailor data display.
- View Configurations: Combines conditions, database fields, and declarative actions linked with view templates, enabling grouping into configuration bundles for reusable setups.
- User Interaction Actions: Supports triggering server scripts or client actions directly from card views, enhancing interactivity.
Typical Users and Use Cases
- Service Desk Agents: Efficiently filter, sort, and act on incidents, requests, and tasks across tables.
- IT Support Staff: Monitor and manage IT assets and service requests in a consolidated interface.
- Managers and Team Leads: View key performance indicators and team workloads easily.
- Customer Service Representatives: Access and respond to customer cases and information quickly.
- Business Analysts and Process Owners: Combine data from multiple sources for improved decision-making.
- Developers and Administrators: Configure custom views to surface relevant data for users.
EVAM Workflow
- Entity: The data source (e.g., community post, user record).
- View: Defines how data and actions are displayed on cards.
- Actions: Operations that can be performed on an entity via the card (e.g., activating a user).
- Mapping: Links entity data fields to UI component properties and associates actions with the card view.
Benefits to ServiceNow Customers
- Allows configuration of multiple tailored view templates per data source, enhancing user experience by displaying relevant information based on conditions.
- Supports ingestion and unified display of multiple data sources in card or list formats without custom coding.
- Enables efficient user interactions through actionable cards, improving productivity for various roles.
- Simplifies maintenance and scalability of data views through configuration bundles and reusable components.
Next Steps
To effectively implement EVAM, ServiceNow customers should explore detailed configuration guides and best practices for managing entity views and actions. This will ensure the right data is presented to the right users in an optimized and interactive manner.
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.
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.
- Entity: examples include a community post or sys_user
- Mapping: fields found in an entity
- 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: