Glossary¶
One term per concept. When a term has a plainer everyday word, that word is given as well. The terms are listed alphabetically.
Older terms
Earlier material uses other words for some of these ideas. They still work as links here, and each points to the current term.
| Older term | Current term |
|---|---|
| Application model | Intended Design |
| Compiler, generator | Engine |
| Implementation strategy, strategy | Target |
| zAppDev Mamba | the language |
| Knowledge graph | Connected graph |
| Meta graph | Shape of an Intended Design |
| The six layers | The six views; layer now means database, server or interface |
A¶
- Access token
- A credential that lets an AI agent connect to the MCP server of one application. It is scoped to that application, can have an expiry date and can be revoked. See MCP server.
- Action
- A piece of code in the language on a form that runs when something happens, such as a click, or when the form opens. An action marked as an entry point is also a URL that renders the form. Also called a controller action. See Controller.
- API adapter
- A model that describes an external system your application calls: its operations and the structures it exchanges. See API Adapters.
- Application model
- Older term for the Intended Design.
- Association
- A relationship between two classes of a business object. It states the multiplicity on each side, which side can navigate to the other, and what happens on delete. See Associations.
- Attribute
- A named, typed piece of data of a class, such as Name of type string. A class has an Id attribute as its key. Attributes can be persisted, which means they are stored in the database. See Class.
- Automation flow
- A model that runs steps of work, on a schedule or on an event. Each step runs code in the language. Also called a workflow in older material. See Automation flows.
B¶
- Build
- The step that validates the Intended Design, runs the engine and the target, builds the result and deploys it to your test environment, where it gets its own address. Run opens that address. See The engine.
- Business exception
- An error you raise on purpose, with
BusinessException.Create(...), when a rule is broken and the user should be told. See Exceptions. - Business object
- A model made of related classes, enumerations and the associations between them. Classes hold attributes and operations written in the language. See Business Objects.
C¶
- Class
- The definition of a kind of thing in a business object, such as Product, with its attributes, associations and operations. A persisted class is stored in the database. See Class.
- Code map
- A file that links every generated method back to the Intended Design operation it came from, line by line, so a stack trace leads to the Intended Design. See The engine.
- Collection
- An ordered list of values of one type, written
Collection[T]. Query results are collections. See Types and variables. - Compiler
- Older term for the engine.
- Composition
- An association in which a class owns its children, such as an order and its lines. Saving the parent saves the children, and deleting the parent deletes them.
- Configuration
- The application-level model: roles, permissions, settings, security and the target. See Configuration.
- Console
- The panel at the bottom of Studio with the build output, validation results, symbols, the debugger and the application logs. See Console.
- Control
- A building block of a form, such as a label, a text box, a button, a table or a chart. You drag controls from the Toolbox. See Controls.
- Controller
- The part of a form that holds its actions, written in the language. See Controller.
D¶
- Data contract
- A structure that defines the request or response of a service operation. See Data Contracts.
- Data mapping
- A model that maps one structure onto another and generates the conversion code. Also called a data transformation in older material. See Data mappings.
- Dataset
- A definition of how a form gets data from a source, such as a class and its Get all operation. Controls such as lists bind to a dataset, which handles filtering, sorting and paging. See Model.
- Default page
- The form and action an application opens at its address, or for cases such as a page not found. Set in the application's configuration. See Hello World, part one.
- Deployment
- A numbered version of the application, produced in production build mode and delivered to a file system or an FTP server. See Deploying Applications.
- Domain
- The prefix for business object types in the language, as in
Domain.Product. Also the name of the folder in the Project Explorer that holds business objects.
E¶
- Editor
- Studio's tool for working on one kind of model, such as the Forms editor or the Business objects editor. Not to be confused with the code editors for the language, JavaScript and CSS. See Editors.
- Element
- A single node in the Intended Design, such as a class, a form, an operation or a role.
- Entry point
- A controller action marked so that it renders a form and can be opened from a browser. Its route is made from the form and action names, such as HomePage/Index.
- Engine
- The part of zAppDev that checks the whole Intended Design, optimises it, and hands it to a target that produces the application. Older material calls it the compiler or the generator. See The engine.
- Enumeration
- A data type made of a set of named values. See Enumeration.
F¶
- Form
- A model that defines a user interface. It is a web form (a page), a master page (a layout shared by pages) or a partial view (a reusable part). See Form Editor.
- Form container
- The placeholder in a master page where each page is rendered. Every master page needs one.
I¶
- Implementation strategy
- Formal name of a target.
- Intended Design
- The complete, connected description of one application: the structure you draw in Studio and the behaviour you write in the language. It is checked as a whole, and every other artefact, including the code, is produced from it. Older material calls it the application model. See Intended Design.
K¶
- Connected graph
- The Intended Design seen as connected elements and relationships, which you can ask questions such as what would break if a class changes. Older material calls it the knowledge graph.
- Knowledge graph
- Older term for the connected graph.
L¶
- Lambda
- A small function written
x => expression. It is how you filter, sort and transform collections and how you tellFindwhat to look for. See A tour of the language. - Layer
- One of the three physical levels of an application: database, server and interface. Not to be confused with the six views.
- Library
- A set of ready-made classes and methods built into the language, such as
AppLiborCommonLib. See Libraries. - Localization
- Text and values that change with the language of the user. You define resources with a value per language and use them as
LocalResources.Key. See Localization.
M¶
- Mamba (zAppDev Mamba)
- The name of the typed, C#-like language for the logic of an application. The overview pages call it simply the language, and the language reference uses its name. See Mamba.
- Master page
- A form that gives other forms a common layout, such as a header and a menu. Every form has one, except partial views. See Master Page.
- MCP (Model Context Protocol)
- A standard that lets AI agents use an application through tools. Every zAppDev application has its own MCP server. See AI and MCP.
- Meta graph
- Older term for the shape of an Intended Design.
- Model
- One part of the Intended Design, named by its kind: a business object, a form, a service, an API adapter, an automation flow, a data mapping, a report, a theme, a unit test or the configuration. Studio groups the models of an application by kind in the Project Explorer, and each kind has its own editor.
O¶
- Operation
- A method of a class, or an endpoint of a service or an API adapter, with its logic written in the language where it has logic.
P¶
- Partial view
- A reusable part of a form that other forms include. It does not need a master page. See Partial View.
- Pattern
- A ready-made building block of the Intended Design, such as the List control or an association that states what happens on delete, which you choose by name. See Choose a pattern, don't invent one.
- Permission
- A named access flag. Actions and operations can require it, and roles hold it. See Permissions.
- Persisted
- Stored in the database. A persisted class has a table, and a persisted attribute has a column.
- Project Explorer
- The tree on the left of Studio that lists the models of the open application, grouped by type. See Project Explorer.
- Properties
- The panel on the right of Studio that shows the settings of the selected item, such as a control or an attribute.
R¶
- Report
- A model that designs a printable or exportable document. See Reports.
- Resource
- A named piece of localized text. See Localization.
- Role
- A named group of permissions that users belong to. See Roles.
S¶
- Service
- A model that exposes your application to others, as REST or MCP, with operations and data contracts. See Services.
- Shape of an Intended Design
- The types of element zAppDev knows and the named relationships allowed between them. It is the shape every Intended Design follows. Older material calls it the meta graph.
- Shadow class
- A read-only copy, in one business object, of a class or enumeration defined in another. It lets you see the definition and use it in an association. See Shadow Class.
- Studio
- The browser-based workspace where you describe, test and build applications. See Studio.
T¶
- Taskbar
- The vertical bar on the left edge of Studio with the main commands: new item, validate, build, run, tools and help. See Taskbar.
- Template
- A starting point for a new application, such as Empty or Web application, or for a new item, such as a form or a business object.
- Target
- A program that encodes the patterns, architecture, libraries and security of one stack, such as .NET with Angular. Its formal name is implementation strategy. You choose it in the Configuration editor, where it is labelled Implementation Strategy. See Targets.
- Theme
- The design tokens and styles that give an application its look, in light and dark variations. See Theme Editor.
- Toolbox
- The panel on the right of the form editor that lists the controls you can drag onto a form.
U¶
- Unit test
- A model of test operations and helpers, written in the language and run in Studio. See Unit tests.
V¶
- Validation
- The check of the whole Intended Design that runs before a build and on demand. It finds broken relationships and wrong types, not wrong business rules. See Validation.
- Version control
- Git-based history of the Intended Design, with update, commit and diffs from Studio. See Version Control.
- View
- One of the six ways an Intended Design describes an application: Intent, Domain, Logic, UX/UI, Integration and Data. See The approach.
- View model
- The data a form holds while it is open, defined in the form's Model panel and read in the language as
Model. See Model.
W¶
- Workspace
- Your own cloud environment in Studio. It holds your applications and users, and has a subscription plan, for example Personal or Enterprise. See Subscription.
Z¶
- zAI
- The AI assistant inside Studio that reads the Intended Design through tools and proposes changes. See zAI.