Entity View Action Mapper Evam

The Entity View Action Mapper (EVAM) allows you to map specific actions to entity views, enabling customized behavior and streamlined work-flows. Learn how to define, configure, and apply mappings to enhance user interactions with data in the platform.

Define the list of data sources to render. The Entity View Action Mapper (EVAM) definition is the main record for an EVAM configuration.

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.

The data source is an entity that has associated data that you intend to display. For example, a community post or a user.

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.

Create a view configuration to combine conditions, database fields, and declarative actions with an associated view template using the Entity View Action Mapper (EVAM).

The Entity View Action Mapper (EVAM) in ServiceNow supports domain separation. This means you can configure EVAM to separate data, processes, and administrative tasks into logical groupings called domains, ensuring that users have access only to the data pertinent to their specific domain.

Reference topics provide information about the Entity View Action Mapper (EVAM).

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

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

Optimize data presentation and interaction by defining data sources, creating Entity View Action Mapper (EVAM) configuration bundles, and setting up EVAM view templates to structure and display entity data effectively.

Learn about the roles needed to configure and manage the Entity View Action Mapper (EVAM).

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

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 using the Entity View Action Mapper (EVAM).