Events Model

Overview

The events table defines system-wide or application-specific events that can be triggered based on user actions, workflows, or external system integrations. These events can be linked to business logic, feature execution, screen rendering, roles, and process files, enabling event-driven architecture in a low-code or modular backend platform.

Fields

Field	Type	Description	Required
id	string	Unique identifier for the event.	❌
title	string	Name or title of the event.Used in UIs or logs to identify the event	✅
executeTask	any	Specifies the backend task or function to execute when the event is triggered.	❌
methodType	any	Defines the method of execution, such as HTTP methods(GET,POST) or custom internal methods.	❌
selectedpkg	any	Indicates the package or module associated with this event.	❌
featureData	any	Contains additional data or configurations related to the event's feature, possibly in JSON format.	❌
eventId	string	Identifier for linking the event to other records.	✅
description	string	Detailed explanation of the event.Helps with documentation or debugging.	❌
override	any	Boolean or flag indicating whether the event overrides another event.Useful for modifying inherited or default behavior.	❌
application_id	string	ID of the associated application.Used in multi-app platforms.	❌
object_type	string	Type of object related to the event	❌
object_id	string	ID of the related object. Used to link this event to a record or asset.	❌
eventType	string	Type/category of the event. Used for categorization and filtering.	❌
eventName	string	Specific name of the event.Used in code or templates to reference the event.	❌
selectedPackage	string	Associated package for the event.Ties into modular packaging or deployment logic.	❌
inputJsonFile	string	JSON file containing event-related input data. Used for pre-loaded configurations or testing.	❌
selectedProcessFile	string	Associated process file for execution.Could contain a workflow or automation.	❌
feature	any	Feature related to this event.Used to integrate with feature toggles or modules.	❌
org_id	string	Organization identifier linked to this event. Important in multi-tenant setups.	❌
predecessorEvent	string	ID of a preceding event, if applicable.Used for chaining events or defining sequences.	❌
roles	array	User roles associated with the event. Enforces role-based access control.	❌
created_at	date	Timestamp when the event was created.	❌
modified_at	date	Timestamp when the event was last modified.	❌
children	array	Child events linked to this event.Used for hierarchical or composite event structures	❌
selectedScreen	array	Screen associated with the event.	❌
parent	string	Parent event, if this is a sub-event.Supports nesting or inheritance.	❌
template_id	string	Identifier of the event template, if applicable.	❌
executionType	string	Specifies how the event is executed	❌

Sample JSON

{
  "id": "example_value",
  "title": "example_value",
  "executeTask": "example_value",
  "methodType": "example_value",
  "selectedpkg": "example_value",
  "featureData": "example_value",
  "eventId": "example_value",
  "description": "example_value",
  "override": "example_value",
  "application_id": "example_value",
  "object_type": "example_value",
  "object_id": "example_value",
  "eventType": "example_value",
  "eventName": "example_value",
  "selectedPackage": "example_value",
  "inputJsonFile": "example_value",
  "selectedProcessFile": "example_value",
  "feature": "example_value",
  "org_id": "example_value",
  "predecessorEvent": "example_value",
  "roles": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "children": "example_value",
  "selectedScreen": "example_value",
  "parent": "example_value",
  "template_id": "example_value",
  "executionType": "example_value"
}