What is NOT considered a best practice for labeling in Appian?

Using repeated words to show that fields are related is not considered a best practice for labeling in Appian. Effective labeling enhances clarity and user experience within applications. When labeling similar fields, it's preferable to use consistent and succinct labeling without unnecessary repetition. This practice helps maintain a streamlined interface and improves readability. For example, if there are multiple fields related to "Address," it's better to simply label them as "Street," "City," and "State" rather than repeating the word "Address" for each field.

Options that involve justified label positions for read-only fields, avoiding mixing different label positions, and using the above-content label position for editable fields all contribute positively to user comprehension and interaction, aligning with established best practices in Appian's design guidelines. These approaches ensure that users can quickly interpret information and navigate the interface more efficiently.