Appian ACD201 key terms

A design object that defines a reusable data structure, mapping to a database table or web service, and grouping fields, relationships, and security for use across applications.

A configuration that connects an Appian environment to an external relational database, letting record types read and write data stored outside the Appian engine.

A mapping inside a data store that ties a record type to a specific table or view in the connected database, including column-to-field correspondence.

A defined association between two record types, such as one-to-many, that lets queries traverse linked data and powers related-record displays and filters.

A condition applied when retrieving records, expressed through expressions on fields and relationships, that limits which rows are returned to a query or user filter.

A diagram of nodes and flows describing a business workflow, including the sequence of user tasks, automated steps, gateways, and events that drive a process instance.

A single running execution of a process model, carrying its own variable values, task assignments, and progress state from start node to completion.

A named value stored within a process instance, typed and scoped, used to pass data between activities and to persist state across user and automated steps.

The category assigned to a process node that determines its behavior, such as user input task, service task, gateway, timer event, or subprocess.

A process node that branches or merges flow based on conditions or events, directing each instance down one or more outgoing paths.

A process activity that generates a task for a person or group, presenting a form and pausing the process until the task is submitted or reassigned.

A work item assigned to a user or group that appears in their task list and, when completed, advances the related process instance.

A process node that launches a separate process model, either synchronously or asynchronously, so common logic can be reused across multiple parent workflows.

A process node that delays or triggers flow at a specified time or interval, enabling scheduled escalation, reminders, or time-based branching.

A reusable user interface design object built from layouts and components, rendered to users in tasks, sites, or records and bound to local variables and rules.

The interface presented to a user when completing a task, typically containing input components whose values are written back to process variables on submission.

A container component that arranges child components on a page, controlling spacing, columns, cards, and sections without defining business logic.

A single configurable UI element such as a text field, button, grid, or chart, whose properties and bindings determine what the user sees and can do.

A variable scoped to a single interface that holds temporary UI state, such as input values or selections, without persisting to the process or database.

A reusable expression saved as a design object that returns a value, such as text, a list, or a query result, and can be called wherever an expression is allowed.

A formula written in Appian's expression language that computes a value from functions, variables, and literals, used throughout interfaces, processes, and queries.

A design object that defines a call to an external system, specifying the endpoint, request mapping, authentication, and how the response maps back into Appian data.

A reusable configuration holding connection details and credentials for an external service, shared by integrations so authentication is defined once and reused.

A standards-based interface, commonly REST or SOAP, exposed over HTTP that Appian can call to exchange data with external applications.

The saved Appian artifact produced from an integration, containing the configured request, response handling, and error behavior for calling an external endpoint.

A named collection of users used to grant access and assign work in bulk, forming the primary unit for permission and task routing decisions.

A named set of permissions that can be granted to users or groups on an application or folder, simplifying repeated access assignments.

The per-object access settings that specify which users and groups may view, modify, or administer a design object or its data.

Settings controlling who may start, view, or administer a process model and its running instances, separate from the security of its underlying data.

A container design object that groups related record types, interfaces, processes, and integrations, and is the unit typically packaged and deployed between environments.

The act of moving application objects and their dependencies from one environment to another, such as from a development site to a test or production site.

A bundled set of application objects and dependencies prepared for migration, inspected for completeness before being imported into a target environment.

A distinct Appian installation or site, such as development, test, or production, each holding its own data, users, and deployed applications.

The administrative area where administrators manage users, groups, security settings, system health, and logging for an Appian environment.

A diagnostic view reporting the status of engine components, queues, and services so administrators can detect performance problems or failures.

How quickly and reliably an application responds under load, influenced by query design, process complexity, indexing, and environment resource allocation.