User Interface & UX Design Flashcards

Which Appian design pattern should be used when an interface needs to load data only after a user interaction, such as a button click?

Answer: Use a!refreshVariable() with refreshOnVarChange triggered by a local variable the button updates

By linking a!refreshVariable() to a local variable that the button modifies, the interface can defer a data load until triggered by user action.

What does the 'readOnly' property on an Appian input field do?

Answer: Displays the field value without allowing user edits

Setting readOnly to true renders an input field as display-only text, preventing user modification while still showing the current value.

In Appian, which component is best suited for allowing users to upload files as part of a process task?

Answer: a!fileUploadField()

a!fileUploadField() provides a native file upload control in Appian interfaces, storing uploaded files in Appian's document management system.

What is the advantage of using 'a!gridField()' over 'a!listLayout()' for displaying tabular data in Appian?

Answer: a!gridField() supports sortable columns, pagination, and row selection for interactive data grids

a!gridField() is a feature-rich grid component with built-in sort, pagination, and selection capabilities suitable for interactive tabular data.

Which Appian expression function returns the currently logged-in user's username?

Answer: loggedInUser()

loggedInUser() returns the username of the currently authenticated user, commonly used for personalization and security checks in interfaces.

In Appian, what is the purpose of using 'a!save()' inside a button's 'saveInto' parameter?

Answer: To update a local variable or process variable with a new value when the button is clicked

a!save() targets a specific variable (local or process) and assigns it a new value when the associated button or link is clicked.