ObjectPackage Model

Overview

The objectpackage table stores metadata related to packages in the system. These packages contain different objects and components associated with an application. The table provides a structure for managing the package's attributes, relationships, functions, and deployment status.

Fields

Field	Type	Description	Required
id	string	Unique identifier for the object.Primary key for reference across the platform.	❌
name	string	Name of the object package. Used for display, search, or identification.	❌
bundle_id	any	ID linking to a parent or associated bundle. Groups multiple packages into a collection or release bundle.	❌
ref_id	any	Reference ID for linking to other objects or configurations. Used for linking or mapping to entities like templates, models, etc.	❌
type	string	The type/category of the object package. For categorization and filtering.	❌
status	string	Current status of the object. Used for Workflow control and UI display logic.	❌
bundleBuildId	string	ID referencing the build process of the parent bundle. Track deployments and CI/CD pipeline outputs.	❌
user_id	string	ID of the user who created or last modified this object. Used for Attribution and audit purposes.	❌
description	string	A short summary or description of what the object package is or does. It's mainly used for display, search, or quick context.	❌
line_item_type	string	Specifies what kind of item this object is within a package	❌
metadata	array	Stores additional attributes in a flexible, usually JSON, format. This could include tags, configuration settings, or any extended information.	❌
relations	array	Captures how this object package relates to others—like dependencies or parent-child links—likely stored in JSON or structured text.	❌
functions_code	any	This is the actual script or code that defines the object's behavior. In a low-code or programmable system, this could be the logic that gets executed.	❌
logging	array	Contains any logging configuration or logs related to this object package. Useful for debugging or monitoring.	❌
children	array	List of child objects linked to this object.This holds the identifiers or structure of child objects, enabling a hierarchy or nesting of components.	❌
deploy	string	Boolean flag indicating if the object is deployed or ready for deployment.	❌
standardLineItem	any	Boolean flag indicating if the object is a standard line item. Identifies whether this object package is a standard (often reused) element across multiple packages.	❌
created_at	date	Timestamp when the object was created.Used for tracking, sorting, and auditing.	❌
modified_at	date	Timestamp when the object was last modified. Also used for tracking changes and syncing.	❌
package_id	string	Identifier for the package associated with the object.Links the object package to a parent package, helping to group it logically with other objects for deployment or organization.	❌
application_id	string	Identifier linking the object to an application.Ties the object package to a specific application, supporting multi-application environments and tenant scoping.	❌

Sample JSON

{
  "id": "example_value",
  "name": "example_value",
  "bundle_id": "example_value",
  "ref_id": "example_value",
  "type": "example_value",
  "status": "example_value",
  "bundleBuildId": "example_value",
  "user_id": "example_value",
  "description": "example_value",
  "line_item_type": "example_value",
  "metadata": "example_value",
  "relations": "example_value",
  "functions_code": "example_value",
  "logging": "example_value",
  "children": "example_value",
  "deploy": "example_value",
  "standardLineItem": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "package_id": "example_value",
  "application_id": "example_value"
}