Appian Certified Analyst cheat sheet

A process model is a diagram of nodes (activities, gateways, events, start/end points) connected by flows; each model is versioned, and running instances continue on the version they started on.

Exclusive gateway: exactly one outgoing path is taken, chosen by the first condition that evaluates true; a default path can be set to handle no-match cases.

Parallel gateway splits into all outgoing paths simultaneously and joins by waiting for every incoming token before continuing.

User input task pauses the flow until a user completes a form or task action; script task runs server-side expression logic without user interaction.

Timer events fire on a duration or date expression relative to the token's arrival; escalation and error events route tokens to alternate paths.

Subprocess node embeds a child process model; the parent waits for the subprocess to complete unless the subprocess is configured to run independently.

Process instance priority and deadlines drive task urgency; assignment can target users, groups, or expression-based dynamic assignees.

Node inputs and outputs map process variables; activity class determines the form or interface rendered to the user at runtime.

A record type defines a data structure with fields, relationships, and a data source; record types are the primary way Appian surfaces business data.

Record type sources include database tables/views, web services, process variables, and expression-backed (custom) sources; the source determines read and write capability.

A one-to-many relationship uses a foreign key on the child record; a many-to-many relationship requires a join record type linking both sides.

Record fields can be scalar (text, integer, date) or derived via expressions; record type references let a field point at another record.

Record-level security uses role-based access (viewer, editor, administrator) applied to users and groups; field-level security can hide individual fields.

A record type can be process-backed (data written via a process) or entity-backed (directly mapped to a database table) - entity-backed supports direct writes.

Record actions define create, update, and delete behavior; related actions surface child record operations from a parent record view.

Data sync keeps record data current by periodically or event-driven refreshing from the source; sync status and errors are visible in the designer.

The Appian environment tiers are development, test, and production; objects move between them via deployment packages, not by direct editing in production.

An application bundles related objects (process models, record types, interfaces, groups) and is the unit used for versioning and deployment.

Groups control access to folders and objects; membership can be static or rule-based, and nested groups inherit permissions from parents.

A role maps business responsibilities to groups and is used to assign permissions consistently across objects.

Knowledge centers and folders organize content; folder security cascades to contained objects unless overridden.

Environments have separate data stores; object UUIDs are preserved across deployments so references between objects remain intact.

A constant stores reusable values (text, integer, group, process) and can be referenced across expressions and objects.

Community and Tempo are end-user surfaces; Tempo presents tasks, records, reports, and actions to business users.

Deployment packages are built from an application and validated before import; validation reports missing dependencies and conflicts.

Object security is enforced by role-based permissions; administrators should review group membership and object-level access regularly.

Process model versioning means deployed changes create a new version; in-flight instances stay on their original version until completion.

Audit and monitoring: process instance history, task history, and admin console logs provide traceability of who did what and when.

Change management separates development from production; direct production edits bypass validation and are generally disallowed.

Data retention and process archival policies determine how long completed instances and their data remain queryable.

Deployment best practices include testing in a lower environment, comparing package contents, and importing in dependency order.

Application versioning and object UUID stability support safe promotion; deleting an object in production can break dependent references.

A plug-in extends Appian with custom Java functionality (custom functions, smart services, data stores) and is deployed as a JAR to the application server.

Connected systems define reusable integrations (REST, SOAP, or other) with authentication and endpoint configuration shared across integrations.

An integration object references a connected system and specifies the operation, request mapping, and response mapping.

Custom data types map external payload structures to Appian types so integration responses can be consumed in expressions and interfaces.

Expression functions include built-in functions plus plug-in-provided functions; custom functions are registered and callable like native ones.

Web service integrations support GET/POST/PUT/DELETE with headers, query parameters, and body; error handling maps HTTP status to process error paths.

Appian can expose its own process models and record types as web APIs (API objects) for external systems to call.

Smart services and custom data stores let plug-ins supply specialized behavior beyond out-of-the-box components.

A process model is a diagram of nodes (activities, gateways, events, start/end points) connected by flows; each model is versioned, and running instances continue on the version they started on.

Exclusive gateway: exactly one outgoing path is taken, chosen by the first condition that evaluates true; a default path can be set to handle no-match cases.

Parallel gateway splits into all outgoing paths simultaneously and joins by waiting for every incoming token before continuing.

User input task pauses the flow until a user completes a form or task action; script task runs server-side expression logic without user interaction.

Timer events fire on a duration or date expression relative to the token's arrival; escalation and error events route tokens to alternate paths.

Subprocess node embeds a child process model; the parent waits for the subprocess to complete unless the subprocess is configured to run independently.

Process instance priority and deadlines drive task urgency; assignment can target users, groups, or expression-based dynamic assignees.

Node inputs and outputs map process variables; activity class determines the form or interface rendered to the user at runtime.

A record type defines a data structure with fields, relationships, and a data source; record types are the primary way Appian surfaces business data.

Record type sources include database tables/views, web services, process variables, and expression-backed (custom) sources; the source determines read and write capability.

A one-to-many relationship uses a foreign key on the child record; a many-to-many relationship requires a join record type linking both sides.

Record fields can be scalar (text, integer, date) or derived via expressions; record type references let a field point at another record.

Record-level security uses role-based access (viewer, editor, administrator) applied to users and groups; field-level security can hide individual fields.

A record type can be process-backed (data written via a process) or entity-backed (directly mapped to a database table) - entity-backed supports direct writes.

Record actions define create, update, and delete behavior; related actions surface child record operations from a parent record view.

Data sync keeps record data current by periodically or event-driven refreshing from the source; sync status and errors are visible in the designer.

The Appian environment tiers are development, test, and production; objects move between them via deployment packages, not by direct editing in production.

An application bundles related objects (process models, record types, interfaces, groups) and is the unit used for versioning and deployment.

Groups control access to folders and objects; membership can be static or rule-based, and nested groups inherit permissions from parents.

A role maps business responsibilities to groups and is used to assign permissions consistently across objects.

Knowledge centers and folders organize content; folder security cascades to contained objects unless overridden.

Environments have separate data stores; object UUIDs are preserved across deployments so references between objects remain intact.

A constant stores reusable values (text, integer, group, process) and can be referenced across expressions and objects.

Community and Tempo are end-user surfaces; Tempo presents tasks, records, reports, and actions to business users.

Deployment packages are built from an application and validated before import; validation reports missing dependencies and conflicts.

Object security is enforced by role-based permissions; administrators should review group membership and object-level access regularly.

Process model versioning means deployed changes create a new version; in-flight instances stay on their original version until completion.

Audit and monitoring: process instance history, task history, and admin console logs provide traceability of who did what and when.

Change management separates development from production; direct production edits bypass validation and are generally disallowed.

Data retention and process archival policies determine how long completed instances and their data remain queryable.

Deployment best practices include testing in a lower environment, comparing package contents, and importing in dependency order.

Application versioning and object UUID stability support safe promotion; deleting an object in production can break dependent references.

A plug-in extends Appian with custom Java functionality (custom functions, smart services, data stores) and is deployed as a JAR to the application server.

Connected systems define reusable integrations (REST, SOAP, or other) with authentication and endpoint configuration shared across integrations.

An integration object references a connected system and specifies the operation, request mapping, and response mapping.

Custom data types map external payload structures to Appian types so integration responses can be consumed in expressions and interfaces.

Expression functions include built-in functions plus plug-in-provided functions; custom functions are registered and callable like native ones.

Web service integrations support GET/POST/PUT/DELETE with headers, query parameters, and body; error handling maps HTTP status to process error paths.

Appian can expose its own process models and record types as web APIs (API objects) for external systems to call.

Smart services and custom data stores let plug-ins supply specialized behavior beyond out-of-the-box components.