Appian Certified Analyst key terms

A reusable diagram that defines the sequence of steps, gateways, and events for a business process. It is the blueprint analysts design and later instantiate as running process instances.

A single running execution of a process model, created when the model is started. It tracks its own state, variables, and task history independently of other instances of the same model.

A named data field owned by a process instance and used to carry values between nodes. Variables can be scoped to the process or to individual nodes and are read or written by activities.

A single element placed on a process model diagram, such as a task, gateway, event, or subprocess. Nodes are connected by flows to define the order of execution.

A process model node that controls how flow moves through the diagram by splitting or merging paths. Common types include exclusive gateways that choose one path and parallel gateways that activate all paths.

A process activity that pauses execution and generates a form for a human to complete. The process resumes only after the assigned user submits the form, and the submitted values are stored in process variables.

The rule that determines which users or groups receive a task and are allowed to act on it. Assignments can be static, based on process data, or driven by a group membership expression.

A process node that starts another process model and waits for it to finish, or launches it asynchronously. It lets analysts reuse common logic without duplicating nodes in every model.

A design object that models a business entity and maps it to a data source, such as a database table or web service. It defines fields, relationships, and actions used throughout the application.

A single row or instance of a record type, representing one business entity such as a customer or order. Records are created, read, updated, and deleted through the record type's configured data source.

A named attribute on a record type that corresponds to a column or property in the underlying data source. Fields define the data type and can be used in expressions, forms, and queries.

A defined link between two record types that describes how their records associate, such as one-to-many or many-to-many. Relationships enable users to navigate from one record to related records.

A configurable operation on a record type, such as create, update, or delete, that defines how users can change record data. Actions control which fields are editable and what validation applies.

A configuration that tells the platform how to connect to and query an external data source for one or more record types. It holds connection details and the mappings used to read and write records.

A saved request that retrieves records from a record type using filters, sorting, and paging. Queries are used to populate grids, charts, and other components without loading all records at once.

A container that groups related design objects, such as process models, record types, and interfaces, into a deployable unit. Applications are versioned and moved between environments as a whole.

Any reusable artifact created in the application designer, such as a process model, interface, record type, or rule. Design objects have names, versions, and dependencies tracked by the platform.

A design object that defines a user-facing screen or layout, built from components and bound to data. Interfaces are used in forms, dashboards, and record views.

A type of interface presented to a user during a task or action, containing fields and controls for data entry. Forms are linked to process activities or record actions and validate input before submission.

A named collection of users used to manage access and task assignment. Groups can contain other groups and are referenced when configuring security or routing work to teams.

A named set of permissions that controls what actions a user or group can perform on an application or object. Roles are granted to groups and evaluated when users access features.

A separate deployment of the platform, such as development, test, or production, where applications run. Objects are promoted between environments through deployment packages.

The process of moving an application and its dependent objects from one environment to another. Deployments can be packaged, inspected, and rolled back to keep environments consistent.

A specific allowance to view, edit, or administer an object or feature, granted through roles or direct assignment. Permissions are checked by the platform whenever a user attempts an action.

A chronological record of security-relevant events, such as logins, permission changes, and administrative actions. Analysts use it to investigate incidents and demonstrate compliance.

A rule that specifies how long different categories of data are kept and when they are archived or deleted. It supports privacy requirements and keeps process and record data manageable.

A control that prevents one person from completing all parts of a sensitive transaction, reducing fraud and error risk. It is enforced by assigning conflicting tasks to different groups or roles.

A connection between the application and an external system, used to exchange data or trigger remote actions. Integrations are configured with endpoints, authentication, and request mappings.

A reusable configuration that stores connection details for an external service, such as a URL and credentials. Integrations reference a connected system so authentication is managed in one place.

A standard way for systems to exchange data over a network, typically using HTTP and structured messages such as JSON or XML. Integrations often call web services to read or write remote data.

A reusable design object that returns a value computed from inputs and built-in functions. Analysts use expression rules to centralize logic and avoid duplicating formulas across interfaces and processes.

A defined interface that lets other software call the application's functions or data programmatically. APIs are used for integrations, mobile access, and automating actions from external systems.