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.
Reference: Appian Best Practices - Expression Writing and Naming Conventions

To achieve the behavior where users see only " active " vehicle records by default but can also view all records when needed, you should configure a user filter for the status field on the Vehicle record list. This user filter should have a default value set to " active " , which will filter the list to only show active records initially. However, users will still have the option to adjust the filter to see all records, thus accommodating occasional auditing requests.
References: Appian Documentation - Record List Filters and User Filters

Given that ri!name is defined as "Maria" and ri!directory contains two a!map() structures, one of which includes the name "Maria," the expression wherecontains(ri!name, index(ri!directory, "name")) will evaluate as follows: The index() function will return a list of values from ri!directory for the key "name," which will be {"Maria", "Steven"}. The wherecontains() function will then check where "Maria" is found within this list. Since "Maria" is the first element, the function will return a list of indices where "Maria" is found, in this case, {1}. Appian lists are 1-indexed, so the first position is represented by 1, not 0.
Reference: Appian Expression Language Documentation - Functions

Explanation:

Based on the default behavior for task assignments in Appian, when a User Input Task is assigned to a group, any one member of the group can accept the task. Once accepted, the task becomes locked to that user, and they are responsible for completing it. This prevents multiple users from working on the same task simultaneously and ensures clear accountability.
Reference: Appian Documentation - Task Assignments and User Input Tasks