a record related action. This allows the action to be performed in the context of a specific record, making it straightforward for users to initiate processes directly from the record view.
References
* Appian Documentation: Record Related Actions

In Appian, when an interface references an expression rule, the interface is considered a dependent because it depends on the expression rule to function correctly. Conversely, the expression rule is a precedent because the interface relies on it.
Reference:
Appian Documentation: Managing Application Contents

To establish a many-to-many relationship between two record types in Appian, you should create a junction or mapping record type that will handle the many-to-many association. This new record type should have two one-to-many relationships, one to each of the original record types (ACME_Student and ACME_Class). This setup allows each student to be associated with multiple classes and each class to be associated with multiple students.
Reference: Appian Documentation - Record Type Relationships

The best practice for naming variables in Appian is to use clear and descriptive names that convey the purpose or content of the variable. Therefore, local!applicantHeight is the best option as it precisely describes the value contained by the variable, which is the height of an applicant. This naming convention aids in readability and maintainability of the code, making it easier for developers to understand and modify the code in the future.
References: Appian Best Practices - Expression Writing and Naming Conventions