Glossary
Definitions of the core Nooxl Apps terms. The headword is the current UI term. Also known as lists older documentation wording or internal names, so readers coming from earlier docs or the API can map them.
note
Use the browser search (Ctrl + F) to jump to a term quickly.
Structure and hierarchy
The building blocks, from the broadest to the most specific: Instance → Tenant → Nooxl App → Model → Data label.
| Term | Meaning | Also known as |
|---|---|---|
| Instance | A Nooxl Apps installation reached through a unique URL (for example https://apps.nooxl.com). Holds any number of tenants. Instances do not interact, except for copying apps between them. | Server (informal) |
| Tenant | A workspace that hosts one or more Nooxl Apps and their users. Data can be exchanged between apps of the same tenant. | Account |
| Nooxl App | An application made up of one or more models. Roughly comparable to a program. | App, Universe |
| Model | An Excel spreadsheet turned into a database-backed view in the app. Keeps full Excel compatibility. | Template, Spreadsheet, Matrix |
| Work mode | The normal mode in which users view, edit, and save data in the app. | Workmode |
| Design mode | The mode (pencil ) in which designers create and customize apps, models, and sections. | Draft mode |
Data and labels
| Term | Meaning | Also known as |
|---|---|---|
| Data label category | A collection of similar labels, for example a category Scenarios or Users. | Catalog |
| Data label | A single entry within a data label category, for example Scenario 1. | Element, Catalog element |
| Data label collection | A named subset of labels from a category. A label can belong to any number of collections. Used for selections and permissions. | Condition |
| Dataset | A combination of one label from each category that forms the selection of a model. Each dataset stores its own values. | Data record |
| Dataset selection | The set of labels assigned to a model that defines which datasets exist. | Selection, MatrixSelection |
| Dataset history | The record of every view and change of a dataset, enabling tracking of who did what and when. | State, Status, Activity history |
Models and versioning
| Term | Meaning | Also known as |
|---|---|---|
| Template | A version of a model's uploaded spreadsheet, numbered like 1.0, 1.1, 2.0. | Release, File version, Template version, LogicRelease |
| Revision | The lifecycle state of a template version: checkout (minor/major copy), check-in, publish, unpublish, reopen. | Revision state |
| Nooxl Transformer | The assistant that turns an uploaded Excel file into a Nooxl model automatically. | Transformer |
| Model comparer | A tool to compare two datasets or model versions side by side. | Comparer |
| Cell style | The formatting applied to model cells; input cells use dedicated background colors (for example Enter.Light/Normal/Strong). | Model cell styles, Stylesgrid |
Sections (markups)
A section anchor marks one or more model cells and can be given Nooxl capabilities by adding one or more sections to it.
| Term | Meaning | Also known as |
|---|---|---|
| Section anchor | One or more marked cells in a model that can carry Nooxl capabilities. | Markup, Marking |
| Cell storage section | Stores and reads cell data in the database (read and/or write), including external reads and range vectors. | MarkupEntry, Database mark |
| Cell storage bindings | The connection between a model's cells and the cell storage that backs them. | Bind |
| Cell action section | Adds extended program logic to cells. | Function, MarkupFunction |
| Query section | Reads data from another source (for example another model or an external query) into cells. | MarkupBxlink, Database mark (external) |
| Tab view section | Defines what is shown in work mode, including showing/hiding and fixing rows and columns. | View, MarkupRegion, Tab |
| Image viewer section | Shows pictures and charts from the model in the app. | MarkupDocViewer |
| Automation section | Runs background processing of tasks (for example recalculation across datasets). | JobRanges, MarkupJob |
| Permissions section | Grants workflow-based permissions that change with a workflow status, beyond the static collaboration permissions. | Workflow, MarkupWorkflow |
Data integration
| Term | Meaning | Also known as |
|---|---|---|
| Data integration | Bringing external data into the app through data queries. | Bxlink, Data exchange |
| Data query | A defined query (with commands and parameters) that retrieves external data. | Bxlink link/command |
| Data export | Extracts of app data provided as Excel files for analytics (dimensions and fact tables). | Bidata |
Collaboration and roles
| Term | Meaning | Also known as |
|---|---|---|
| Navigation | The structure of menu items in the app's left navigation. | Operation |
| User profile | A user that can access the tenant and its apps. | User |
| Permission group | A reusable set of users that permissions can be assigned to, similar to a role. | Group |
| Permission | A right granted to a user or group on an object (app, model, dataset, data label, and more). App-level vs account-wide Global. | Authorization |
| Translations | Tenant-level translations of app-facing strings. | AccountTranslation |
| Account Owner | The user who created the tenant; holds all rights and cannot be deprived of admin rights. | — |
| Admin | A user with the same permissions as the account owner; can be granted and revoked. | — |
| User | A user who is neither account owner nor admin; rights come from standard or workflow permissions. | — |