Appian Records Deep Dive: Interview Questions & Expert Answers

Appian Records are a unified data layer combining a data source (database table, process model) with built-in UI, security, and process automation. Unlike a raw database table, a Record Type provides: a built-in List View and Summary View; Record Actions — buttons that launch processes; Record-level security through record-level filters; Related Records for automatic joins; and Search/filtering with a!queryRecordType. Records abstract the data layer into a consistent, reusable application object.

Entity-Backed Records use a database table (via a JPA Entity/Data Store) as their source — ideal for persistent business data like Employees or Orders. Process-Backed Records use active process instances as their source — each running process = one record. Process-backed records are a legacy pattern; for modern Appian development, entity-backed is the standard.

Synced Record Types cache database data into Appian's managed index for fast querying. Enable sync when you need low-latency record queries or are querying an external database frequently. Do not sync extremely large tables or frequently-changing data exceeding the sync refresh interval.

Record Actions are buttons on a Record Type's Summary/List View that trigger business processes. Types: (1) Related Action — process model requiring an existing record as context; (2) Start Action — creates a new record by starting a process; (3) Form-based Action — launches a SAIL interface directly using a!writeRecords for simple CRUDs.

Relationships are defined in Record Type configuration by specifying the Related Record Type, relationship type (One-to-Many, Many-to-One), and joining fields. Once defined, query related data using dot notation: recordType!Employee.fields.department.name. Always define relationships at the Record Type level for reusability.

Record-Level Security restricts visible records via a filter expression applied to every query — for example, filter where assignedUserId = loggedInUser(). This filter is transparent and cannot be bypassed by users. Object-level security controls who sees the Record Type; record-level security controls which rows are visible.

a!queryRecordType is the modern, type-safe API for querying Appian Record Types — it enforces record-level security automatically, traverses relationships via dot notation, and returns record data types. a!query queries Data Store Entities directly without automatic security enforcement. Always prefer a!queryRecordType for new development.

Use a!writeRecords() in a form's submit event — it accepts a recordType reference and CDT list, handling INSERT or UPDATE based on whether the primary key is set. For complex transactional workflows, use a process model with dedicated Write to Data Store Entity nodes instead.