Work with the Entity View Action Mapper for UI Builder
Summarize
Summary of Work with the Entity View Action Mapper for UI Builder
The Entity View Action Mapper (EVAM) in UI Builder allows you to standardize the display of various data sources in your components, whether in card grid or list format. This functionality enhances how users interact with data, enabling a seamless switch between views.
Show less
Key Features
- Entity: Represents the data source, such as community posts or user information.
- View: Defines how the data and associated actions are presented on cards.
- Actions: Actions can be performed directly from the card, such as activating a user.
- Map: Links data sources to generic fields displayed on the cards, allowing for action triggers.
EVAM data sources can be added and bound to components to enhance data presentation and user interaction.
Key Outcomes
By utilizing EVAM, ServiceNow customers can effectively:
- Standardize the display of data across different components, improving user experience.
- Implement toggle switches for users to easily switch between card and list views.
- Configure various parameters such as page size, page number, and filters to tailor the data displayed to user needs.
Ultimately, this results in a more organized and user-friendly interface for interacting with data within ServiceNow applications.
With UI Builder, you can use the Entity View Action Mapper (EVAM) application to standardize how the data sources in your components are displayed in your cards and lists.
EVAM Overview
Entity View Action Mapper (EVAM) is an application that standardizes how different data sources are displayed in cards and lists. UI Builder uses EVAM data sources to show information in a component as a card grid view or as a list of information. You can add a toggle to your component to let users switch between card grid and list views.
- Entity (data source). Associated data that you intend to display, such as a community post or a user.
- View. How a card displays data and actions.
- Actions. Action that it performs on the card. For example, you can activate a user into your system.
- Map. A process that maps the data source to generic fields that are displayed on the card. You can also associate actions that trigger from the card view.
EVAM data sources
| EVAM data source | Description |
|---|---|
| EVAM Data Resource | Add an EVAM definition and other information about the data source.
To add an event handler for when that data fetch is initiated, succeeded, or failed, select Events. In the Now Code Editor section, which is next to the Configuration pane, preview the EVAM definition script. |
| Fetch EVAM Data | To add an EVAM definition and other information about the data source, select Configuration.
To add an event handler for when that data fetch is initiated, succeeded, or failed, select Events. Preview the EVAM definition script in the Now Code Editor to the right of the Configuration pane. |
| Fetch EVAM Metadata | To select when to evaluate the EVAM data resource and add an EVAM definition, select Configuration.
To add an event handler for when that data fetch is initiated, succeeded, or failed, select Events. Preview the EVAM definition script in the Now Code Editor to the right of the Configuration pane. |
| Search EVAM Data Resource | To add an EVAM definition, and other information about the data source, select Configuration.
To add an event handler for when that data fetch is initiated, succeeded, or failed, select Events. Preview the EVAM definition script in the Now Code Editor to the right of the Configuration pane. |