EventMappings Model

Overview

The eventmappings table stores configuration data that maps application-level events to business logic, custom actions, screens, packages, or tasks. It enables dynamic event-driven behavior by linking user or system-generated events to the appropriate backend actions or front-end navigation.Defining what should happen when a particular business object or screen triggers an event.

Fields

Field	Type	Description	Required
id	string	Unique identifier for each event mapping entry.	❌
application_id	string	Identifier for the associated application.Used in multi-application environments.	❌
application_item_id	string	Refers to a specific application component or module where the event is applicable	❌
event_id	string	Identifier for the associated event.Maps to the events table (eventId column).	❌
eventId	string	eventId field	❌
screen_name	string	Screen or interface where the event occurs. Helps determine where the event should be triggered in the frontend.	❌
business_object_id	string	Identifier for the business object linked to the event.	❌
actiontype	any	Describes the kind of action triggered (e.g., submit, delete, approve).	❌
business_object	any	The main object model related to this event mapping	❌
event	any	Name or type of the event being triggered (e.g., onClick, onLoad, onSubmit).	❌
event_action	string	The specific action to perform when the event occurs (e.g., redirect, save, executeWorkflow).	❌
eventobject	any	A serialized or structured object that represents the event metadata or configuration	❌
mapping_id	any	Optional reference ID linking this mapping to another mapping set, version, or configuration group.	❌
assignedpackage	any	The package/module to which this mapping is linked or assigned (may be JSON or plain text).	❌
executiontype	any	How the event is to be executed: sync, async, queued, etc.	❌
customAction	string	A custom-defined action name, typically handled in code or through dynamic rules	❌
custompage	string	Custom page or route to navigate to or render when the event is triggered.	❌
executeTask	any	Describes the backend task or job that should be executed (can be function name, workflow, etc.).	❌
methodType	any	HTTP method or internal action method type (GET, POST, PUT, etc., or internal, external).	❌
selectedpkg	any	A specific package selected or applicable for the event context.	❌
file	any	Name or path of the file associated with this mapping (used in custom events or file-based configs).	❌
active	boolean	Boolean or flag indicating if the event mapping is active.	❌
created_at	date	Timestamp when the event mapping was created.	❌
modified_at	date	Timestamp when the event mapping was last modified.	❌
event_connector	any	Connection or integration point for the event.Might define conditional flows, connectors, or integrations.	❌

Sample JSON

{
  "id": "example_value",
  "application_id": "example_value",
  "application_item_id": "example_value",
  "event_id": "example_value",
  "eventId": "example_value",
  "screen_name": "example_value",
  "business_object_id": "example_value",
  "actiontype": "example_value",
  "business_object": "example_value",
  "event": "example_value",
  "event_action": "example_value",
  "eventobject": "example_value",
  "mapping_id": "example_value",
  "assignedpackage": "example_value",
  "executiontype": "example_value",
  "customAction": "example_value",
  "custompage": "example_value",
  "executeTask": "example_value",
  "methodType": "example_value",
  "selectedpkg": "example_value",
  "file": "example_value",
  "active": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "event_connector": "example_value"
}