Appian Certified Analyst flashcards
Appian Certified Analyst · Build recall with a focused review session.
33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Exclusive gateway
- A process node that evaluates outgoing conditions in order and routes each token down exactly one path, optionally using a default path when no condition matches.
- Parallel gateway
- A process node that creates a token on every outgoing path when splitting and waits for all incoming tokens before continuing when joining.
- User input task
- A process activity that pauses execution and presents a form or task to an assigned user, resuming only after the user submits an action.
- Script task
- A process activity that executes server-side expression logic automatically without user interaction, useful for data transformation or system calls.
- Timer event
- A process event that fires after a specified duration or at a specified date relative to token arrival, commonly used for deadlines and reminders.
- Subprocess
- An activity that runs a separate child process model; the parent typically waits for the child to finish before proceeding down the flow.
- Process model versioning
- Each deployment of a changed process model creates a new version; already-running instances stay on the version they started on until completion.
- Record type
- A design object defining a data structure with fields, relationships, and a data source, used as the primary way Appian surfaces business data.
- Entity-backed record type
- A record type mapped directly to a database table or view, allowing direct read and write operations without routing through a process.
- Process-backed record type
- A record type whose data is written through a process model rather than directly, giving control over validation and side effects.
- One-to-many relationship
- A record relationship where a child record stores a foreign key pointing to one parent record; one parent can have many children.
- Many-to-many relationship
- A record relationship implemented with a join record type that links records on both sides, since neither side can hold a single foreign key.
- Record-level security
- Role-based access control applied to a record type, granting viewer, editor, or administrator rights to specified users and groups.
- Data sync
- The mechanism that refreshes record data from its source on a schedule or event, keeping record views current and reporting sync errors.
- Record action
- A configured operation on a record type, such as create, update, or delete, that defines how users modify record data.
- Application object
- A container that bundles related process models, record types, interfaces, and groups, and serves as the unit for versioning and deployment.
- Group
- A collection of users used for access control; membership can be static or rule-based, and nested groups inherit permissions from parent groups.
- Role
- A governance object mapping a business responsibility to one or more groups, used to assign permissions consistently across many objects.
- Constant
- A named, reusable value such as text, integer, group, or process reference that can be shared across expressions and design objects.
- Environment tiers
- Separate development, test, and production environments; objects are promoted between them using deployment packages rather than direct production edits.
- Folder security
- Access rules applied to a folder that cascade to contained objects unless a child object overrides them with its own permissions.
- Tempo
- The end-user surface in Appian where business users see their tasks, records, reports, and available actions.
- Deployment package
- A bundle of application objects built for promotion between environments; it is validated before import to detect missing dependencies and conflicts.
- In-flight instance
- A process instance that is still running; it remains on its original process model version even after a newer version is deployed.
- Change management
- The practice of separating development from production and promoting validated packages, so untested direct production edits are avoided.
- Object UUID stability
- Object identifiers are preserved across deployments, so references between objects remain intact when a package is imported into another environment.
- Process instance history
- A record of completed and active process steps, task assignments, and timestamps used for auditing and tracing who did what and when.
- Data retention policy
- Rules governing how long completed process instances and their associated data remain stored and queryable before archival or deletion.
- Plug-in
- A Java-based extension deployed as a JAR to the application server that can add custom functions, smart services, or data stores to Appian.
- Connected system
- A reusable integration configuration holding endpoint and authentication details, shared by multiple integration objects that call the same external system.
- Integration object
- A design object that references a connected system and defines the specific operation, request mapping, and response mapping for an external call.
- Custom data type
- A structure mapping an external payload's fields to Appian types, allowing integration responses to be consumed in expressions and interfaces.
- Web API object
- An Appian object that exposes process models or record types as callable endpoints so external systems can invoke Appian functionality.