AEP key terms

A design object that defines a structured set of business data, its fields, relationships, and the actions available on it. It is the foundation for data storage and user-facing record views in an application.

A mapping between an Appian record type and a physical table in a relational database. It defines how data is read from and written to the underlying source.

An individual attribute defined on a record type, such as text, number, or date. Fields map to columns in the data store and are used in forms, queries, and expressions.

A configured association between two record types, such as one-to-many or many-to-many. Relationships let users navigate related data and enable related-record queries and grids.

A field type that stores a link to a record in another record type rather than a plain value. It powers relationships and related-record navigation.

The configured connection an application uses to reach a database or service, such as a JDBC data source. Record types and queries rely on a data source to retrieve and persist data.

A saved, reusable query definition against a data store entity that supports filters, sorting, and paging. It lets interfaces and processes retrieve record data consistently without rewriting logic.

A reusable user-experience definition built from components such as layouts, grids, and inputs. Interfaces render forms and dashboards and can be embedded in processes or other interfaces.

Appian's declarative language for defining user interfaces as a tree of components. Developers describe what to show, and the platform renders it across devices.

A single building block in an interface, such as a text field, button, grid, or card layout. Components are configured with parameters and combined to compose a screen.

A reusable expression or logic definition that returns a value or interface fragment. Rules centralize calculations, validation, and display logic so they can be shared across objects.

A formula written in Appian's expression language that evaluates to a value, such as text, a list, or a boolean. Expressions drive conditions, defaults, and computed fields.

A variable defined inside an interface or expression to hold intermediate values during evaluation. It simplifies complex logic and keeps expressions readable without affecting process data.

A user-facing interface used to collect or display information, typically attached to a user input task. Forms validate input and pass submitted values back to the process.

A diagram that defines an automated workflow as a sequence of connected nodes, such as tasks, gateways, and events. It coordinates who does what and in what order.

A named value that carries data through a process instance, shared across nodes and tasks. Variables can be initialized, updated, and passed to interfaces and integrations.

A process node that pauses execution and assigns work to a user or group through a form. The process resumes when the task is completed or the deadline passes.

A process node that performs automated work without human involvement, such as calling an integration or running a script. It executes immediately when reached.

A process node that branches or merges the flow based on conditions or events. It determines which path an instance follows next.

Any single element in a process model, including events, tasks, and gateways. Nodes are connected by flows that define execution order.

The configuration that determines who receives a user task, such as a user, group, or expression. Assignments control work routing and visibility in task lists.

A configured connection to an external system, such as a REST or SOAP service, used to send or retrieve data. Integrations are called from processes, interfaces, and expressions.

A reusable definition of how to authenticate and connect to an external service, holding shared credentials and endpoint settings. Integrations reference connected systems to avoid duplicating configuration.

An interface exposed over a network, typically using REST or SOAP, that allows systems to exchange data. Appian can both consume external web services and expose its own.

A style of web service using HTTP methods and resource-oriented URLs to exchange data, usually in JSON. Appian integrations commonly call REST APIs to read and write external data.

The process of verifying a user's or system's identity before granting access. Appian supports methods such as username and password, SAML, and OAuth for users and integrations.

The rules that determine what an authenticated user is allowed to see or do. In Appian it is enforced through object security roles and record-level access controls.

A collection of users managed together for assignment and security purposes. Groups can be nested and are commonly used to grant access to applications and records.

A named set of permissions applied to an object, such as viewer, editor, or administrator. Roles map groups or users to the actions they may perform on that object.

Access rules that filter which individual records a user can view or modify, often based on their group membership or data values. It supplements object-level permissions.

A container that groups related objects such as record types, interfaces, and process models for a business solution. Applications are the unit deployed and managed across environments.

Any named design artifact in Appian, such as a record type, interface, process model, or integration. Objects have security, versioning, and dependency relationships.

The process of moving an application and its objects from one environment to another, such as from test to production. Deployments package objects and resolve dependencies.

A separate Appian instance used for a stage of the lifecycle, such as development, testing, or production. Objects are promoted between environments through deployment packages.

A saved automated check that verifies an expression, rule, or process produces expected results. Test cases support regression testing before deployment.

A single running execution of a process model, with its own variable values and task history. Instances can be monitored, paused, or cancelled by administrators.

The administrative area where administrators manage users, groups, security settings, and system health. It centralizes configuration that applies across applications.

A tool that displays application and system log entries to help diagnose errors and monitor behavior. Administrators use it to trace failures in processes and integrations.