Business Data Dictionary
Business-focused documentation explaining the purpose and usage of each table and field in Axiom Genesis.
Tenant & User Management
app_tenants
Purpose: Defines organizations/companies using the platform. Each tenant is completely isolated from others.
Business Context: A tenant represents a customer organization. All data within the platform is segregated by tenant to ensure privacy and security.
| Field | Business Purpose |
|---|---|
tnt_tenant_code | Unique identifier used in URLs and API calls (e.g., "acme-corp") |
tnt_tenant_name | Display name shown in UI (e.g., "Acme Corporation") |
tnt_app_settings | Tenant-specific configuration including theme colors, enabled features, and usage limits |
tnt_status | Whether the tenant is active (1), temporarily disabled (0), or archived (-1) |
Relationships:
- Parent of all tenant-specific data
- Referenced by
{table}_tenant_idin every table
app_users
Purpose: Stores user accounts that can log into the platform.
Business Context: Users belong to a tenant and are assigned roles that determine their permissions.
| Field | Business Purpose |
|---|---|
usr_email_id | Login identifier and contact email |
usr_first_name, usr_last_name | User's display name |
usr_app_settings | Personal preferences (theme, language, notification settings) |
usr_status | Whether user can login (1=Active, 0=Suspended) |
Relationships:
- Belongs to one tenant via
usr_tenant_id - Can have multiple roles via role assignment table
Status Values:
| Value | Meaning | User Experience |
|---|---|---|
| 1 | Active | Can login and access system |
| 0 | Inactive | Cannot login, account suspended |
app_roles
Purpose: Defines permission sets that can be assigned to users.
Business Context: Roles control what features and data users can access. A tenant can have custom roles beyond system defaults.
| Field | Business Purpose |
|---|---|
rol_code | Identifier used in code and configuration (e.g., "admin", "viewer") |
rol_permissions | JSON array of permitted actions (e.g., ["read:users", "write:users"]) |
rol_tenant_id | NULL for system roles, tenant_id for custom roles |
Common System Roles:
| Code | Purpose |
|---|---|
super_admin | Full system access |
tenant_admin | Full tenant access |
user | Standard user access |
viewer | Read-only access |
Object & Configuration
app_object_registries
Purpose: Defines entity metadata - what tables exist and how to interact with them.
Business Context: The registry enables a metadata-driven architecture where new entities can be added through configuration rather than code changes.
| Field | Business Purpose |
|---|---|
obj_code | Entity identifier used in APIs (e.g., "users", "projects") |
obj_type_code | Whether entity is a TABLE, VIEW, or FUNCTION |
obj_connection_code | Which database contains this entity's data |
obj_payload | Field definitions, relationships, and validation rules |
obj_payload_object_name | Actual database table name (e.g., "app_users") |
obj_payload_column_prefix | Column naming prefix (e.g., "usr_") |
Use Cases:
- Frontend reads registry to build forms dynamically
- API uses registry to validate requests
- DataView uses registry for grid column definitions
app_object_profiles
Purpose: Defines field-level security and data transformation rules.
Business Context: Profiles enable fine-grained access control - different users see different fields based on their role.
| Field | Business Purpose |
|---|---|
prf_code | Profile identifier used in API URLs |
prf_obj_code | Which entity this profile applies to |
prf_mode_code | Access mode (FULL, READ, WRITE, EXECUTE) |
prf_policy | Security rules for projection, masking, and filtering |
Policy Examples:
| Policy Type | Example | Result |
|---|---|---|
| Projection (exclude) | ["password_hash", "salt"] | Hide sensitive fields |
| Masking | {"email": "partial"} | Show "j***@example.com" |
| Row Filter | {"department": "@user.department"} | Only see own department |
app_value_set
Purpose: Stores dropdown/picklist values for reuse across the application.
Business Context: Centralizes enum values so they can be updated in one place and reflected everywhere.
| Field | Business Purpose |
|---|---|
vst_code | Value set identifier (e.g., "status_codes", "priority_levels") |
vst_values | Array of value objects with value, label, and display order |
Example Value Sets:
| Code | Values |
|---|---|
status_codes | Active, Inactive, Archived |
priority_levels | Low, Medium, High, Critical |
task_types | Bug, Feature, Enhancement, Task |
UI/UX Configuration
app_page_configs
Purpose: Stores page/form layouts created in Page Designer.
Business Context: Enables no-code form building - business users can create and modify forms without developer involvement.
| Field | Business Purpose |
|---|---|
pgc_code | Page identifier for URL routing |
pgc_type | Page type: form, dashboard, report, or content |
pgc_obj_code | Which entity this page displays/edits |
pgc_config | Complete page layout including fields, sections, and actions |
pgc_version | Version number for change tracking |
Page Types:
| Type | Purpose | Example |
|---|---|---|
form | Data entry | User registration form |
dashboard | Data visualization | Sales KPI dashboard |
report | Formatted output | Invoice template |
content | Static/dynamic content | Help documentation |
app_dataview_configs
Purpose: Stores data grid configurations for list/table views.
Business Context: Enables configurable data grids with filtering, sorting, and row actions.
| Field | Business Purpose |
|---|---|
dvc_code | DataView identifier for navigation |
dvc_obj_code | Which entity to display |
dvc_config | Column definitions, filters, row actions, and styling |
Configuration Options:
- Column visibility and order
- Default sorting and filtering
- Row actions (view, edit, delete, custom)
- Bulk actions
- Export options
app_navigation_configs
Purpose: Defines the menu structure and navigation items.
Business Context: Controls what appears in the sidebar menu and where navigation leads.
| Field | Business Purpose |
|---|---|
nvc_code | Navigation item identifier |
nvc_description | Menu item label shown to users |
nvc_target_type | What type of target: DATAVIEW, PAGE, SECTION, document_renderer |
nvc_target_code | Which configuration to load when clicked |
nvc_parent_code | Parent menu item for hierarchy |
nvc_icon | Icon to display in menu |
nvc_display_order | Sort order within parent |
Target Types:
| Type | Behavior |
|---|---|
DATAVIEW | Opens data grid |
PAGE | Opens form/page |
SECTION | Expandable menu group |
document_renderer | Opens document viewer |
DASHBOARD | Opens dashboard |
Workflow Engine
app_workflow_configs
Purpose: Stores workflow definitions created in Workflow Designer.
Business Context: Enables visual workflow design for automating business processes.
| Field | Business Purpose |
|---|---|
wfc_code | Workflow identifier |
wfc_name | Display name |
wfc_config | Workflow graph: nodes, edges, triggers, variables |
wfc_version | Version number (immutable after publish) |
wfc_status | 1=Published, 0=Draft |
Workflow Components:
- Triggers: What starts the workflow (manual, scheduled, event)
- Nodes: Actions to perform (API call, approval, notification)
- Edges: Connections between nodes with conditions
- Variables: Data passed between nodes
wft_instances
Purpose: Tracks running workflow executions.
Business Context: Every time a workflow runs, an instance is created to track its progress and state.
| Field | Business Purpose |
|---|---|
wfi_instance_code | Unique execution identifier |
wfi_status | Current state of execution |
wfi_current_node | Which node is currently executing |
wfi_input_data | Data provided when workflow started |
wfi_output_data | Results produced by workflow |
wfi_error_message | Error details if workflow failed |
Status Values:
| Status | Meaning |
|---|---|
pending | Queued, waiting to start |
running | Currently executing |
paused | Waiting for external input (approval) |
completed | Successfully finished |
failed | Error occurred |
cancelled | Manually stopped |
wft_logs
Purpose: Records detailed execution logs for debugging and audit.
Business Context: Provides visibility into what happened during workflow execution.
| Field | Business Purpose |
|---|---|
wfl_instance_id | Which instance this log belongs to |
wfl_node_id | Which node generated this log |
wfl_message | Human-readable log message |
wfl_level | Severity: INFO, WARN, ERROR, DEBUG |
wfl_data | Additional structured data |
Collaboration
apt_projects
Purpose: Organizes work into project containers.
Business Context: Projects can represent document collections, work initiatives, or any grouping of related items.
| Field | Business Purpose |
|---|---|
prj_code | Project identifier |
prj_name | Display name |
prj_slug | URL-friendly version for routing |
prj_doc_config | Document tree structure for documentation projects |
Project Uses:
- Document management (knowledge bases, wikis)
- Task tracking
- File organization
- Team collaboration spaces
apt_files
Purpose: Stores metadata for uploaded files.
Business Context: Tracks files uploaded to the system, with actual file content stored in blob storage.
| Field | Business Purpose |
|---|---|
fst_project_id | Which project owns this file |
fst_filename | Original uploaded filename |
fst_mime_type | File type (image/png, application/pdf, etc.) |
fst_size_bytes | File size for quota tracking |
fst_blob_url | URL to retrieve file from storage |
Enum Reference
Status Codes (Universal)
| Value | Name | Description |
|---|---|---|
1 | Active | Normal operational state |
0 | Inactive | Temporarily disabled |
-1 | Archived | Historical, read-only |
Workflow Instance Status
| Value | Name | Next States |
|---|---|---|
pending | Pending | running, cancelled |
running | Running | paused, completed, failed, cancelled |
paused | Paused | running, cancelled |
completed | Completed | (terminal) |
failed | Failed | (terminal) |
cancelled | Cancelled | (terminal) |
Page Types
| Value | Name | Use Case |
|---|---|---|
form | Form | Data entry/editing |
dashboard | Dashboard | Visualizations |
report | Report | Formatted output |
content | Content | Static pages |
Navigation Target Types
| Value | Name | Opens |
|---|---|---|
DATAVIEW | Data View | Data grid |
PAGE | Page | Form/page |
SECTION | Section | Menu group |
document_renderer | Document | Document viewer |
DASHBOARD | Dashboard | Dashboard page |
See Also
- Technical Dictionary - Column specifications
- Copilot Instructions - Development conventions