When naming a local variable for an applicant's height in an expression rule, which naming convention reflects best practice?

When naming a local variable for an applicant's height in an expression rule, which naming convention reflects best practice?

• A. local!height
• B. local!ApplicantHeight
• C. local!applicantHeight
• D. local!heightInCm

Answer: (C)

Descriptive, consistent naming of local variables using lowerCamelCase is best. local!applicantHeight communicates exactly what the value represents—the height of the applicant—without tying it to a specific unit or introducing unnecessary complexity. It follows the common Appian style of starting the variable name with a lowercase letter and using camelCase for readability. The other options are less ideal: a generic local!height is vague about whose height it is; local!ApplicantHeight uses an uppercase initial, which isn’t the standard convention for local variables; and local!heightInCm hardcodes a unit into the name, which can become misleading if the unit changes or if you work with multiple units later.

Descriptive, consistent naming of local variables using lowerCamelCase is best. local!applicantHeight communicates exactly what the value represents—the height of the applicant—without tying it to a specific unit or introducing unnecessary complexity. It follows the common Appian style of starting the variable name with a lowercase letter and using camelCase for readability. The other options are less ideal: a generic local!height is vague about whose height it is; local!ApplicantHeight uses an uppercase initial, which isn’t the standard convention for local variables; and local!heightInCm hardcodes a unit into the name, which can become misleading if the unit changes or if you work with multiple units later.