Glossary
The terms as they are used in the Pantarey interface and in this documentation. Each entry links to the page that covers the term in detail.
| Term | Meaning |
|---|---|
| Action button | Button below the form of a user task or start tile, such as “Approve” or “Reject”. The pressed value is then available in $$context.selectedAction. → User task |
| Application | Ready-made template from the Applications area: data schemas, processes, dashboards, sample data and a tour on one topic, added to the account with one click. → Applications |
| Assignment | Definition of who sees a task or start tile: a person, a group or everyone. → User task |
| Business label | Readable label of a process instance in the Process Explorer, built from placeholders such as $(customer). → Business label |
| Computed field | Attribute of a data schema whose value is calculated from other fields, with JSONata or JavaScript. → Computed fields |
| Counter | Sequential number per name, for example for invoice numbers, via $fn('nextId', 'name'). → Counters |
| Dashboard | Freely composed page made of widgets, built in the Dashboard Designer and assigned to people, groups or everyone. → Dashboards |
| Data schema | The structure of a kind of data with its attributes, form, validation rules, permissions and document name; created in the Data Designer. → Data and data schemas |
| Database | The area where records are displayed, created, edited, copied, converted and exported. → Database |
| Database element | Process element that reads, writes, updates, merges or deletes records. → Process elements |
| Deploy | Activating a working version as a new version of a process or dashboard, with a version description. → Deployment and versions |
| Document name | The display name of a record, built from fields and functions; / creates folders. → Preview field and document name |
| Dry run | Trial run of a process in the designer that checks expressions, paths and fields without calling services. → Dry run |
| Error boundary event | Event attached to a step that routes the process to its own path when an error occurs. → Time, errors and signals |
| External app | Start type where Pantarey regularly polls a provider for new data and starts one instance per hit. → External app |
| External user task | Task that a person without a Pantarey account completes via a link by email or Teams, for example an approval. → External user task |
| File object | The form in which Pantarey handles files everywhere: {referenceId, filename, contentType}. → Files |
| Gateway | Branch in the process; the conditions are JavaScript on the outgoing arrows, one of them is the default flow. → Process elements |
| Group | Set of users to which tasks, start tiles, dashboards and permissions are assigned. → Groups |
| Handlebars | Template language with {{field}} for PDF and email templates and the pages of external tasks. → Handlebars helpers |
| Inheritance | A data schema derived from another one takes over its attributes. → Inheritance and hierarchies |
| JSONata | Expression language for input and output expressions, validation rules, computed fields and data mappings. → JSONata in Pantarey |
| AI approval | Task in which a person confirms an action proposed by the assistant before it is executed. → Building with the assistant |
| AI assistant | External assistant (such as Claude or ChatGPT) that works in Pantarey via the MCP protocol with the user's permissions. → AI assistants |
| AI mode | Mode in the process and dashboard designers in which the assistant works on a copy that is applied or discarded. → AI mode |
| Account | A company's Pantarey account (technically a tenant) with its own users, data and processes; the Account area shows plan, usage and data export. → Account |
| Menu | Navigation for end users managed in the Dashboard Designer that bundles dashboards and start tiles. → Menus |
| Message | The data of a process instance that is passed from step to step and extended by results. → Data in the process |
| Permission | Rule on the data schema defining who may list, read, create, update, delete or query records, also for individual records. → Permissions and actions |
| Process | A flow modeled in the Process Designer (BPMN) that produces process instances after deployment. → Build processes |
| Process Explorer | Area for monitoring running and completed instances with actions such as continue or restart. → Monitor processes |
| Process instance | A running or completed execution of a process with its own message and business label. → Instances |
| Process owner | Person set in the process properties who receives an email when an instance fails. → Time, errors and signals |
| Record | A stored entry of a data schema, such as an invoice or a contact; technically also “data object”. → Database |
| Result path | Place in the message where the result of a step is stored; without a path the result replaces the whole message. → Result path |
| Role | Permission in the app, assigned under Users → Manage users → Permissions, for example “Manage process designer”. → Manage users |
| Secret | Confidential value such as a password, inserted in the process as {{secret:NAME}} and resolved only in service tasks. → Secrets |
| Service task | Process element that Pantarey executes without a user: create a PDF, send an email, read a file, query an AI. → Predefined services |
| Signal | Event thrown by a process that dashboards or other processes pick up. → Time, errors and signals |
| Start event | Element with which an instance begins: user start, schedule, webhook or external app. → Start events |
| Task | A step a person completes: a user task in the process, visible under Pending tasks. → Pending tasks |
| Template function | Function $fn('name', …) for texts and JSONata, such as formatting dates, assigning numbers, counting working days. → Template functions |
| Time limit | Deadline on a user task or external task; when it expires the instance is cancelled or continues with $$context.timedOut. → User task |
| Timer | Time-controlled element: timer start by schedule, intermediate event with waiting time, time limit on tasks. → Date and time |
| User start | Start event that appears as a tile under What would you like to do? and begins an instance with a form, text, immediate start or file upload. → Start events |
| User task | Process element that assigns a task with form and action buttons to a person or group. → User task |
| Validation rule | Condition on the data schema that must be met when saving, with its own error message. → Validation rules |
| Value | Centrally maintained value inserted in the Process Designer as {{value:name}}, such as a threshold or a template. → Values in the process |
| Webhook | Start type where an external system sends JSON by POST to an address and thus starts an instance. → Webhook |
| Widget | Building block of a dashboard, such as table, chart, Kanban or start process. → Dashboards |
| Work calendar | Setting per account defining which days are free (federal state, local holidays, company days off). Basis for counting working days. → Work calendar |
| Working version | The state of a process or dashboard that is edited in the designer. Only the deploy turns it into a numbered version. → Deployment and versions |
Next step
Frequently asked questions: answers to the most common questions from practice.