Packagesettings Model
Overview
The packagesettings table is used to store configuration settings associated with a specific package. These settings could include various parameters that control how a package behaves, its features, and other application-specific configurations. Each entry in this table is linked to a particular package and organization, with the flexibility to store custom settings and line item details.
Fields
| Field | Type | Description | Required |
|---|---|---|---|
| id | string | Unique identifier for the package settings | ❌ |
| package_id | string | ID of the package this configuration applies to. Likely links to a package or pageversions table. | ✅ |
| org_id | string | Identifies the organization for which the configuration is defined. | ✅ |
| application_id | string | Specifies the application context, allowing app-specific settings. | ❌ |
| pack_id | any | Identifier for the package this setting applies to. | ❌ |
| settings | array | Stores the actual configuration settings, likely as a JSON or serialized key-value structure. | ❌ |
| created_at | date | Timestamp when the settings were created. | ❌ |
| modified_at | date | Timestamp when the settings were last modified. Useful for versioning and audit. | ❌ |
| line_item_id | any | Identifier linking the settings to a specific line item within the package.Possibly links to a purchase, feature, or module line item in billing or feature control systems. | ❌ |
Sample JSON
{
"id": "example_value",
"package_id": "example_value",
"org_id": "example_value",
"application_id": "example_value",
"pack_id": "example_value",
"settings": "example_value",
"created_at": "example_value",
"modified_at": "example_value",
"line_item_id": "example_value"
}