Glossary Draft for review
Glossary of business application terms
Short definitions of the terms used across DynamicForm and in business application projects: workflow, integration, security and data. Each term has its own link.
- 4-eyes / 6-eyes approval
- Four-eyes means a person makes a change and a separate person approves it; six-eyes adds a second, different approver. The maker cannot approve their own change, no person approves twice and the final approver publishes.
- Action button
- A button on a screen or workflow step that performs one action, such as Submit, Approve or Send back.
- API
- A defined way for one system to request data or actions from another.
- API key
- A secret value sent with each request to identify the calling system.
- Assumption
- A setting used before the exact answer has been confirmed, such as a default or an interpretation of an answer. The record includes why it was chosen, its risk, supporting evidence and how it will be checked.
- Attestation (Beta)
- A signed statement using fixed wording, with a named signer, evidence and a validity period.
- Base entity
- The database table a screen saves its data into.
- Basic authentication
- A security method that sends a user name and password with each request.
- Bearer token
- A token sent with each request to prove the caller is allowed to make it.
- Bureau pull
- A request to a credit bureau for an applicant's credit report and score.
- Callback
- A reply that a provider sends later when its work is complete. The receiver checks a signature, token or permitted network address, and processes repeated copies only once.
- Circuit breaker
- A control that stops further calls to a provider that is failing. It prevents the application from continuing to send requests to an unavailable service.
- Conditional rule
- A rule that shows, hides, requires or locks a field depending on other answers.
- Configuration
- The saved description of screens, workflows, menus, roles and integrations that the platform runs.
- Configuration document
- A full or summary PDF built from stored application configuration. It includes sources, screens, diagrams, rules, permissions, assumptions and open questions.
- Cost class
- A design-time label for a rule's processing cost: Light, Moderate or Heavy. Heavy rules need explicit, recorded acceptance.
- Data classification
- A field's information category, such as Personal, Financial or Card. In the compliance workspace (Beta), AI suggests classifications and a person confirms them.
- Decision step
- A workflow step that chooses the next route from the case data.
- Dedupe
- A check that finds whether an applicant or record already exists.
- Escalation
- Passing an overdue case to a more senior person.
- Failover
- Switching a request to another provider when the configured failure conditions are met. Your team chooses the routing rules and which providers can serve as backups.
- Gap Report
- A report that separates confirmed information from assumptions and missing details. It shows the evidence behind each finding and highlights conflicts or security issues that need review.
- HMAC signing
- A security method where each request carries a signature the provider can verify.
- Integration
- A configured connection that lets your application exchange information with an outside service. It defines how to sign in, which fields to send, how to use the reply and what to do when the call fails.
- Integration Flow
- A saved process that connects several service calls. It can choose a path based on a reply, wait for a result, run calls in parallel or carry out actions that undo earlier work.
- Integration Spec
- The specification that describes how a connection should work. It brings together the service actions, sign-in method, field matching and checks so your team can review the setup.
- JWT
- JSON Web Token: a signed token that carries identity and permissions between systems.
- Legal hold
- A requirement to preserve records within retention handling, keeping them available while the hold applies.
- Logical operation
- A business service defined independently of the provider that performs it. Replies from different providers are mapped into the same fields so screens and workflows can use them consistently.
- Low-code
- Building applications mainly by configuring rather than writing code.
- Maker-checker
- A control where one person enters or changes data and a second person approves it.
- Master table
- A reference table, such as cities or products, that other records point to by code.
- Mock set
- A prepared request and reply using invented data. It lets your team test a particular result, such as success or timeout, without calling the real provider.
- Mutual TLS
- A security method where both sides of a connection prove their identity with certificates.
- Number series
- A configured sequence for record numbers, with branch counters and yearly, monthly or financial-year resets. Assigned numbers cannot be edited or reused.
- OAuth 2.0
- A way to obtain an access token, a temporary pass that allows a connection to use a service. DynamicForm supports client credentials, password and refresh-token flows; your technical colleague selects the flow required by the provider.
- Offline capture
- Filling forms on a phone without signal; entries are stored and sent when the signal returns.
- OTP
- One-time password: a short code sent by SMS or email to confirm a person or an action.
- Parallel checks
- Workflow steps that start together; the case continues when all are done.
- Probe
- A small test used to check an assumption and save the result as evidence. It runs only against a mock or sandbox and requires your approval, never against production.
- Provider group
- A set of providers that can supply the same business service. Rules determine which provider gets a request, when to switch to a backup and when to return to the original provider.
- RAD platform
- A rapid application development platform for building business applications by configuring them.
- Redis
- An in-memory data store; DynamicForm uses it to serve dashboards, work lists and menus quickly.
- Render engine
- The part of the platform that draws a saved screen design in the browser or the phone app.
- Repeating section
- A section of a screen that can be added several times, such as co-applicants or addresses.
- Requirement document
- A written description of what a system must do, often split into stages and steps.
- Role
- A named set of permissions that decides what a person can see and do.
- Send-back
- Returning a case to an earlier workflow step, with the reason attached.
- Standard outcome
- A shared description of how a service call ended, such as Success, Timeout or Result pending. Provider-specific codes are translated into one of 11 outcomes so screens and workflows can respond consistently.
- TAT
- Turnaround time: the time allowed for a step or a whole case.
- Third normal form
- A way of organising database tables so each fact is stored once, in the right place.
- Work list
- A searchable list of records behind a menu item, such as My cases or Pending approvals.
- Workflow
- The defined path a case takes through steps, people and decisions.
Build your first app free
All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.
Explore DynamicForm
Updated 16 November 2026