Process Automation
What to know
Process Automation on Appian centers on process models: the diagram of nodes (start/end events, user input tasks, script tasks, gateways, subprocesses, timer events) connected by flows. A candidate must understand the difference between a process variable and a process parameter, how activity class and assignment route a user task to a group or user, and how gateways (XOR for exclusive branching, OR for one-or-more, AND for parallel) evaluate outgoing flows. Know that escalations attach to user tasks and fire based on relative time (e.g., after assignment), and that exceptions (error events) can be caught at a boundary or by a parent subprocess.
Traps
Questions love to blur design-time vs run-time. A process model is a template; a process instance is one running copy with its own variable values. Another trap: confusing a gateway condition (evaluated on the flow) with a node output or a task's form. Also watch for questions that imply a subprocess shares variables automatically - it does not unless data is explicitly passed in/out through its inputs and outputs. Finally, remember that an automatic (script) task runs without human interaction, so it cannot have an assignment or escalation.
Rule of thumb
Trace one instance mentally: which node starts, what variable each gateway reads, and where the instance ends. If a branch condition reads a variable that no prior node sets, the branch is a likely bug - and a likely exam answer.
Worked example
An approval process routes to a manager group when amount > 1000, otherwise auto-approves. The XOR gateway reads amount; the manager task assigns to the group and carries a 2-day escalation. The auto-approve path is a script task. Passing amount into the subprocess requires it be declared as an input on that subprocess node.