Skip to main content

Glossary

Definitions of key terms and concepts used throughout Comind.

Core concepts​

  • Action - an operation that changes a record's state or data. Actions are defined in app code. Examples: approve, reject, assign, close.
  • App - a configurable data model with UI, defined as a TypeScript NPM package. Each app works like a database table with rich UI including forms, lists, and actions. Examples: TASK, TICKET, DEAL, WIKI.
  • Field - a data attribute on a record such as text, number, date, or lookup. Custom fields use the c_ prefix.
  • Form - the UI for viewing and editing a single record.
  • List - a saved configuration of filters, sort order, and columns for viewing multiple records.
  • List format - the visual representation of a list. Available formats include table, cards, boards, Gantt, calendar, charts, pivot, and Vega.
  • Record - a single data entry within an app. Each record has a unique slug such as CMW/TASK123. Records are displayed in forms for editing and in lists for browsing.
  • Workspace - an organizational unit - such as a project, department, or team - that contains apps and users.

Roles​

  • App developer - creates and customizes apps as TypeScript NPM packages.
  • System admin - a global administrator who can manage all workspaces and the app catalog.
  • User - anyone who logs in and works with data.
  • Workspace admin - manages users, apps, and permissions within a workspace.

App development​

  • Compile-time - the stage where TypeScript source is compiled into a schema object.
  • inheritFrom - a pattern where a child app extends a parent app, overriding only what it needs.
  • Low-code - creating apps as TypeScript NPM packages using the @comind/api SDK.
  • Plugin - a reusable package that adds capabilities to apps such as notifications, followers, or permissions.
  • Run-time - the stage where the compiled schema is configured with settings and served to users.
  • Schema - the compiled representation of an app, including its fields, actions, layouts, and settings.
  • Zero-code - creating apps visually in the web editor without writing code.

Platform​

  • ACL - access control list. Permissions are evaluated at four levels: workspace, app, record, and field.
  • Calc field - a calculated or virtual field whose value is derived from other fields or related records.
  • Faceted filtering - checkbox-based filters displayed alongside list views.
  • Group - a named collection of users used for permissions and access control.
  • Lookup - a field type that references a predefined set of values, similar to a dropdown.
  • METAMETA - the system-level workspace used for app deployment and configuration.
  • Rollup - an aggregation of values from child records such as sum or count.
  • Shadow - a denormalized copy of a field from a related record, kept in sync automatically.
  • Shell - the React-based application frame that hosts app UIs. Also referred to as UI-Shell.
  • Split view - a side-by-side display of a list and a record form.

Infrastructure​

  • Builder server - the service that compiles app source code into deployable schemas.
  • Processor - the background service that handles async operations such as calc fields, notifications, and indexing.