Resources
Learn how dynamic Resources form the bedrock of custom data modeling, AI retrieval pipelines, and automated workflow execution.
What is a Resource?
At its core, a Resource represents a dynamic business object. Traditional software systems enforce rigid, pre-defined database schemas that force your operations to conform to fixed relational structures. In contrast, our platform uses an adaptable Entity-Attribute-Value (EAV) paradigm designed to mold itself around your operational reality.
Whether you are tracking software development projects, IT support tickets, employee directories, server audit logs, customer relationships, or inventory items, a Resource provides the blueprint for storing and processing your domain data seamlessly.
Creating a Resource
Step-by-step guide to defining Resources, Sections, and Fields.
Working with Items
Capture records, filter and sort tables, and find anything with semantic search.
Terminology Mapping
If you are familiar with standard database design or traditional EAV architectures, here is how our nomenclature translates:
| EAV Concept | Platform Term | Description |
|---|---|---|
| Entity | Resource | The overarching class or definition of a domain object (e.g., Project, Ticket). |
| Entry / Record | Resource Item | An individual instance or record created under a Resource (e.g., Project #104). |
| Attribute | Resource Field | A defined property or metadata element belonging to a Resource (e.g., Status, Log Date). |
| Value | Resource Value | The actual payload data assigned to a Field within a specific Item (e.g., "In Progress"). |
Core Characteristics of Resources
Unlimited Domain Versatility
Because Resources are decoupled from physical database table definitions, you can model any conceptual entity required by your organization without requesting database migrations or developer support.
IT & Engineering
Model support tickets, infrastructure deployment logs, incident reports, or software release milestones.
Human Operations
Maintain employee profiles, onboarding checklists, performance reviews, and equipment distribution lists.
Client Relations
Manage enterprise accounts, active sales deals, communication logs, and customer success pipelines.
Supply & Logistics
Track serial numbers, warehouse inventory, shipment statuses, and purchase orders.
Custom Field Definitions & Typing
Each Resource supports a customizable schema built out of Resource Fields. Fields are strongly typed to ensure accurate data capture and validation:
| Type | What it stores |
|---|---|
String | Free-form text - names, emails, descriptions, IDs. |
Number | Numeric values - costs, quantities, durations. |
Boolean | Flags such as isTicketSolved, isBillable, or requiresApproval. |
Date | Timestamps and dates - log dates, SLA breach targets, resolution times. |
SingleSelect | One value chosen from a predefined option list (lifecycle states, priorities). |
MultiSelect | Multiple values from a predefined option list (tags, categories). |
SingleLookup | A reference to exactly one item of another Resource (e.g. Ticket → Client). |
MultiLookup | References to many items of another Resource (e.g. Project → Team members). |
Point | A geographic coordinate (latitude/longitude). |
Polygon | A closed geographic area drawn on a map. |
LineString | A geographic path or route drawn on a map. |
Fields can additionally be marked as required or unique (uniqueness is enforced per Resource, so duplicate values are rejected at save time).
See Creating a Resource for the full walkthrough of defining Sections and Fields.
UI Field Groups
To keep complex forms legible and well-structured, Resource Fields can be assigned to Resource Sections.
Contains core identity fields such as Title, Requester Email, Created Date, and Priority Level.
Note
Resource Sections are purely organizational constructs on the front-end interface - they do not pollute the underlying data model or complicate backend queries.
Workflow Engine Interoperability
Resource Values are natively represented as JSON primitives (strings, numbers, booleans, objects, and arrays). This architectural choice eliminates structural impedance mismatches when passing data through automation layers.
Because field values are serializable JSON, they seamlessly inject into execution contexts, expression engines, and conditional branching nodes.
Workflow Integration
To learn how Resource Items trigger automated processes, execute code steps, or transform data, visit the dedicated Workflow Engine Documentation.
AI Knowledge Indexing & Vector RAG
Every Resource Item - including its structured values and metadata - is automatically indexed, vectorized, and stored in a vector database background pipeline.
This automatic embedding pipeline ensures that conversational AI assistants and autonomous workflows can query and reason over dynamic Resource Items with full context awareness:
- Natural Language Context Retrieval: Ask the AI assistant questions such as "Show me all unsolved tickets regarding server downtime from last week" or "Summarize project expenditures for Client X".
- Real-time Synchronization: When a Resource Field is updated, the vector index automatically syncs to guarantee accurate model context.
Document Libraries & Asset Attachment
Resources extend beyond flat structured fields. Every Resource Item possesses an integrated Document Library where users can attach arbitrary media and documents.
Multi-Format Ingestion
Attach relevant assets directly to a Resource Item, including PDFs, Word documents (.docx), Excel spreadsheets (.xlsx), plain text files, and images.
Automated Text Extraction
Uploaded documents pass through specialized extraction pipelines that ingest plain text, tabular data, and optical text representations.
Unified RAG Pipeline
Extracted text chunks are vectorized alongside the Resource Item's standard fields. When querying an AI chat agent, relevant passages from attached PDFs or spreadsheet rows are retrieved directly into the context window.
Business Philosophy: Software That Adapts to You
Traditional enterprise software forces organizations to restructure their internal language and processes to fit rigid vendor tables. If a tool only supports "Projects" and "Tasks," companies struggle when trying to represent custom domain workflows like "Regulatory Filings" or "Equipment Calibrations."
Our dynamic EAV structure flips this dynamic:
- Your Reality Comes First: You define the terminology, fields, structure, and categorization that reflect your actual operations.
- Zero Schema Migration Overhead: Adding a field or altering a Resource takes seconds, without downtime or schema lock-in.
- Future-Proof Extensibility: As your business evolves, your data structures evolve alongside you - fully powered by native workflows and contextual AI retrieval from day one.