Appian ACD101 study plan
Appian ACD101 · Give each week a clear focus.
8 weeks · About 6 hours per week
Data Modeling and Records
Map each of the five exam domains to its official weight and write a one-line summary of what each covers
Create a record type backed by a database table and add at least five fields of differing types
Configure a one-to-many relationship between two record types and explain which side holds the foreign key
Describe in writing the difference between a record type, a record field, and a record instance
Your checkpoint
A working two-record-type data model in a personal Appian environment, plus a one-page glossary covering record type, field, relationship, and data source
Data Modeling and Records & Expressions and Rules
Write at least ten expressions using if(), null handling, and text/date functions, and predict the output before running each
Query a record type with a!queryRecordType and filter results using a comparison and a logical operator
Apply a validation or calculated field at the record level and verify it with test data
Explain the difference between an expression rule, a constant, and an inline expression, and when to prefer each
Your checkpoint
A saved expression rule that queries a record type with at least two filters and returns a formatted text summary, tested against three data scenarios
Process Modeling
Build a process model with a start event, a user input task, an exclusive gateway, and an end event
Assign a task to a group and demonstrate how the task appears in the task list for a member of that group
Add a script task that writes a value back to a record and confirm the value changes after running the process
Trace a single instance through the process model and document each node it visits
Your checkpoint
A runnable process model that routes a request down two different paths based on a form value, with the routing decisions documented
Process Modeling & Expressions and Rules
Pass process variables into a user input task form and back out again, verifying values with the process instance history
Use an expression in a gateway condition rather than a hard-coded literal
Configure an error-handling path on at least one node and trigger it deliberately
Distinguish query-style expressions from rule-style expressions and pick the right one for two given scenarios
Your checkpoint
A process model with expression-driven branching and a tested error path, plus notes on the variable scope at each node
User Interface Design
Build an interface with a form layout, a text field, a dropdown, and a submit button
Bind each input to a rule input and confirm the values are readable in a process task
Lay out a grid or card view that renders a list of record data
Explain how interface components map to the sections of a SAIL form definition
Your checkpoint
A two-screen user interface: a list view of record data and a detail/edit form that submits back to a process
User Interface Design & Expressions and Rules
Add client-side validation that blocks submission when a required field is empty
Make one section of the form appear conditionally based on another field's value
Refactor repeated inline expressions on the interface into a named expression rule and confirm behavior is unchanged
Debug a failing interface by reading the expression error message and correcting the cause
Your checkpoint
An interface with conditional visibility and validation, plus a short write-up of the error messages encountered and how each was resolved
Administration, Security, and Deployment
Create a group, add users to it, and grant that group access to a record type and a process model
Explain the difference between object security and process model security, and set both for one application
Export an application into a package file and import it into a second environment, verifying the objects arrive intact
Identify which object types appear in the administration console and what each is used for
Your checkpoint
A deployment package exported and re-imported with a written checklist of the security settings applied to each object type
Data Modeling and Records & Process Modeling & User Interface Design & Expressions and Rules & Administration, Security, and Deployment
Answer a timed set of practice questions from all five domains and log the domain of every miss
Re-study the two weakest domains using the logged misses as the syllabus
Re-derive the record-to-process-to-interface flow end to end without notes
Write a one-page cheat sheet of the ten facts you were most likely to forget
Your checkpoint
A scored practice run with a per-domain error log and a one-page final review sheet
Milestones
Week 2: Two related record types exist and at least one expression rule successfully queries and filters them
Week 4: A process model completes end to end with expression-based branching and a tested error path
Week 6: An interface built on record data submits back into a process with working validation and conditional visibility
Week 8: Practice score is above 80 percent overall with no single domain below 70 percent