Appian ACD301 study materials
Appian ACD301 study resources

Appian ACD301 flashcards

Appian ACD301 · Build recall with a focused review session.

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Record type
A design object that models a business entity, backed by a data source, with fields mapped to columns or relationships and its own security settings.
Reference field
A record type field that stores a pointer to another record type's primary key, implementing a one-to-many or many-to-one relationship.
Junction record type
A record type containing two reference fields, used to model a many-to-many relationship between two other record types.
Data store
The connection object in Appian that links record types to their underlying data source and must be synced before data can be queried.
Query record type
A read-only record type backed by a view or query that returns data without allowing writes to the underlying source.
Field-level security
A record type setting that restricts visibility of individual fields to specified groups, independent of record-level permissions.
a!queryRecordType
A SAIL function that retrieves record data with filters, paging, and sorting, returning a query result for use in interfaces.
XOR gateway
A process gateway that evaluates outgoing conditions and routes the process instance down exactly one matching path.
AND gateway
A process gateway that splits to all outgoing paths and, on join, waits for every incoming path to complete before continuing.
OR gateway
A process gateway that routes to one or more outgoing paths whose conditions evaluate to true, unlike XOR which picks exactly one.
User input task
A process node that pauses execution and presents a SAIL form to an assigned user or group, writing values to process variables.
Subprocess node
A process node that invokes another process model, either synchronously (blocking the parent) or asynchronously (running independently).
Timer event
A process node that delays execution for a duration or until a schedule, requiring the process to be in a wait state.
Error boundary event
An event attached to a process node that catches exceptions from that node and routes execution to an error-handling path.
Process variable
A variable scoped to a single process instance, holding data passed between nodes and updated by tasks or scripts.
Escalation
A user task setting that triggers an action such as reassignment or notification after a configured time threshold is exceeded.
a!localVariables
A SAIL function that declares interface-local variables, referenced as local!name, whose values can be updated with a!save.
a!save
A SAIL function that writes a value to a target variable or rule input, typically attached to a component's saveInto parameter.
saveInto
A component parameter that specifies which a!save calls execute when the user interacts with that component.
a!refreshVariable
A SAIL function that controls when a local variable recalculates, using options like refreshOnReferencedVar or refreshInterval.
a!gridField
A SAIL component that displays tabular data from a list of dictionaries or CDTs using a!gridColumn definitions for each column.
showWhen
A component parameter that conditionally renders the component based on a Boolean expression evaluated at runtime.
a!formLayout
The top-level SAIL layout component that wraps a form with a title, buttons, and contents for user input tasks.
a!buttonWidget
A SAIL component that renders a clickable button whose saveInto and value parameters trigger actions such as navigation or submission.
Application package
A ZIP export of an Appian application containing selected objects and their dependencies, used to move changes between environments.
Group-based security
Appian's permission model where users inherit permissions through group membership rather than being granted access individually.
Initiator permission
A process model permission that grants a user or group the right to start new instances of that process.
Object version
A snapshot created each time an object is saved, allowing comparison and reversion to prior states during development.
Constant
A named, reusable value stored as an application object, often used to hold environment-specific settings across deployments.
Publishing an application
The action that makes design-mode changes visible to end users; unpublished changes remain invisible until published.
Admin Console
The administrative interface for managing users, groups, and system-level settings separate from application design objects.
Deployment dependencies
Objects required by a deployed object that must be included in the package for the import to succeed in the target environment.