ACA User Interface & UX Design 1 — Questions and Answers
Question 1: Which Appian component is used to create a multi-step form where each step is shown on a separate screen?
- Wizard (a!wizardLayout()) (Correct answer)
- Tab Layout
- Section Layout
- Form Layout
Correct answer: Wizard (a!wizardLayout())
The Wizard layout in Appian breaks a long form into sequential steps, improving usability for complex data entry tasks.
Question 2: In Appian, which property controls whether an interface component is visible to the end user?
- showWhen (Correct answer)
- isVisible
- displayCondition
- renderIf
Correct answer: showWhen
The showWhen property in Appian interface components accepts a boolean expression to conditionally show or hide the component.
Question 3: What is the recommended Appian pattern for validating user input on a form before submission?
- Use validations parameter on input fields with a!isNullOrEmpty() or custom rules (Correct answer)
- Validate inputs inside the process model after form submission
- Run a separate validation interface after the main form
- Use JavaScript alert() calls for inline validation
Correct answer: Use validations parameter on input fields with a!isNullOrEmpty() or custom rules
Appian supports inline field validations using the validations parameter, which shows error messages immediately when conditions are violated.
Question 4: Which Appian layout component is used to place two interface components side by side in columns?
- a!columnsLayout() (Correct answer)
- a!sectionLayout()
- a!sideBySideLayout()
- a!boxLayout()
Correct answer: a!columnsLayout()
a!columnsLayout() in Appian arranges child components in horizontal columns, enabling side-by-side placement.
Question 5: What Appian component allows users to select from a predefined list of options in a compact dropdown format?
- a!dropdownField() (Correct answer)
- a!radioButtonField()
- a!checkboxField()
- a!textField()
Correct answer: a!dropdownField()
a!dropdownField() renders a compact select input that lets users pick one option from a list, saving screen space compared to radio buttons.
Question 6: In Appian, what is the purpose of the 'a!localVariables()' function in an interface?
- To define variables scoped to the interface that can be read and modified without affecting process data (Correct answer)
- To declare global constants accessible across all interfaces in the application
- To define variables stored permanently in the database
- To pass variables between separate process models
Correct answer: To define variables scoped to the interface that can be read and modified without affecting process data
a!localVariables() creates interface-scoped variables for tracking UI state (like form step, toggles, temp inputs) without involving the process engine.
Which Appian component is used to create a multi-step form where each step is shown on a separate screen?