Appian ACD101 key terms

A design object that defines a business entity, its fields, data source, relationships, and security. It provides a consistent way to query and display data across interfaces and processes.

A named attribute on a record type that maps to a column or expression in the underlying data source. Fields define what data users can view, filter, and edit.

A configured link between two record types, such as one-to-many, that lets users navigate and query related data. Relationships use matching field values as keys.

A reusable data structure defined in Appian that groups related fields, often used to model process or record data. CDTs can be mapped to database tables and used in expressions.

A mapping between a CDT and a database table that Appian uses to read and write data. It supports create, update, and delete operations from processes.

Role-based permissions that control who can view, create, update, or delete records and related data. Security can be applied at the record type and field levels.

A reusable diagram that defines the steps, decisions, and assignments for a business process. Each run of a process model creates a process instance.

A single execution of a process model, created when the process starts. It carries process variables and moves through activities until completion or cancellation.

A process activity that pauses the process and presents a form to a user or group. The assigned user completes the task, which resumes the process.

A process-model symbol that controls branching and merging of flows. Exclusive gateways choose one path; parallel gateways split or join multiple paths.

A named value stored in a process instance that carries data between activities. Variables can hold text, numbers, dates, CDTs, or other Appian types.

A defined input to a process model that is supplied when the process starts. Parameters initialize process variables and make a process reusable.

The configuration that determines who receives a user input task, such as a user, group, or expression. It may include deadlines and escalation.

A process activity that starts another process model as a child and optionally waits for it to finish. It supports reuse and modular design.

A reusable process activity that performs a predefined action, such as sending an email or writing to a data store. Smart services often integrate Appian with external systems or data.

A SAIL definition that renders a screen or form in Appian. Interfaces combine components, layouts, variables, and expressions to display data and capture input.

Appian's Self-Assembling Interface Layer, a declarative language for building user interfaces with functions. It generates the UI from expressions rather than manual HTML.

A reusable UI element in SAIL, such as a text box, grid, button, or card. Components are configured with parameters and placed inside layouts.

A SAIL structure that arranges components on a page, such as columns, panes, or a form layout. Layouts control spacing and visual grouping.

A SAIL parameter that specifies which variable or record field receives a component's value when it changes. It links user input to process or interface data.

A variable defined inside an interface or expression with a!localVariables. It holds temporary values for calculations or display during a single evaluation.

A SAIL interface designed to collect user input, often used in user input tasks. Forms include fields, validation, and buttons for submission.

A reusable expression stored as an object that returns a value. Rules accept inputs and can be called from other expressions, interfaces, or processes.

A typed parameter declared on an expression rule or interface that receives a value when the rule is called. It makes the rule reusable with different data.

A built-in operation in Appian's expression language, such as a!concat, a!queryRecordType, or a!forEach. Functions return values and are used throughout expressions.

A built-in function that loops over a list and evaluates an expression for each item, returning a new list. It is commonly used to build dynamic UI and data.

An Appian function, a!queryRecordType, that retrieves records using filters, fields, and paging. It returns a data subset for interfaces, expressions, or processes.

The practice of checking for missing or empty values using functions such as a!isNullOrEmpty. It prevents errors and controls display when data is absent.

A named, reusable value stored as an application object, such as a text, number, or list. Constants simplify maintenance because one change updates every reference.

A central Appian administration area for managing users, groups, security, system settings, and monitoring. Administrators use it to configure the environment.

A collection of users used to assign permissions and work. Groups can be nested and can represent departments, teams, or functional roles.

A named set of permissions in Appian that can be granted to users or groups on an object. Roles define what actions are allowed, such as viewer or administrator.

Permissions applied to an individual Appian design object, such as a process model, interface, or record type. Security roles determine who can view, edit, or administer the object.

The process of verifying a user's identity before granting access to Appian. It can use Appian accounts, SSO, or other identity providers.

The process of determining what an authenticated user is allowed to do. Appian enforces authorization through roles, groups, and object security.

A container that groups related Appian objects, such as process models, interfaces, and record types, into one manageable unit. Applications support versioning and deployment.

The process of moving Appian application objects from one environment to another, such as development to production. It uses packages and preserves object dependencies.

A file that bundles Appian objects and their dependencies for import into another environment. Packages are used to deploy applications between environments.

A separate Appian instance used for a stage of the software lifecycle, such as development, testing, or production. Deployments move objects between environments.

A numbered snapshot of an application or object that records changes over time. Versioning helps track releases and roll back or compare deployments.