MENU
You are using a local variable in an expression rule to describe the height of an applicant.
Which statement correctly describes the application of Appian best practices for naming your local variable?
Suggested Answer: B
Get Premium ACD101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
36 comments · newest first
CA
Callie
10 months ago
Definitely going with B, it makes the most sense!
LA
Lauryn
11 months ago
Wait, local!x? That’s a bit too vague, right?
LU
Lucy
11 months ago
C just seems confusing, why not be specific?
VE
Venita
11 months ago
A is way too abbreviated, not a fan.
LE
Leonida
11 months ago
I think B is the best choice, it’s clear and descriptive.
PE
Pearly
12 months ago
I’m a bit confused about option C. Using 'local!x' seems too vague, but I guess it could work in some contexts? I’m not sure if it’s best practice though.
KI
Kiley
12 months ago
I think I saw a similar question in our practice tests. If I recall correctly, option B was highlighted as the best practice for naming conventions.
AL
Alise
12 months ago
I'm not entirely sure, but I feel like using abbreviations like in option A could lead to confusion later on. We should aim for descriptive names, right?
MA
Mari
1 year ago
I remember we discussed the importance of clear variable names in our last study session. I think option B makes the most sense for clarity.
JA
Jacquline
1 year ago
I think the best approach here is to use the most descriptive variable name possible, which would be option B. "local!applicantHeight" clearly communicates the purpose of the variable, which is important for maintainability and understanding the code.
CA
Carlton
1 year ago
Option A seems like it might be the right answer - "local!hoaa" to abbreviate "Height of an Applicant". That would follow the convention of minimizing typing and code length. But I'm not 100% sure.
GA
Gail
1 year ago
Hmm, I'm a bit unsure about this one. I know Appian has specific naming conventions, but I can't quite remember the details. I'll have to think this through carefully.
RO
Roslyn
1 year ago
I'm pretty confident this is option B - "local!applicantHeight". Appian best practices recommend using descriptive variable names that clearly communicate the purpose of the variable.
MA
Marget
1 year ago
This seems like a straightforward configuration question. I'll need to carefully read through the requirements and think about the different options.
MI
Mike
2 years ago
I think option C is also a valid choice, as it follows a common naming convention for variables.
CA
Carissa
2 years ago
But using abbreviations can make the code less readable for other developers.
TW
Twila
2 years ago
Appian devs who use 'local!x' must also prefer their variable names to be as mysterious as their codebase. Just sayin'.
OR
Ora
2 years ago
Yeah, I prefer shorter variable names to save time when coding.
TA
Taryn
2 years ago
A) local!hoaa - This employs the naming convention of abbreviating 'Height of an applicant' to minimize typing.
FR
Francene
2 years ago
I always use descriptive variable names to make my code more readable.
OL
Olive
2 years ago
B) local!applicantHeight - This employs the naming convention of specifically describing the value contained by the variable.
OL
Olene
2 years ago
I'm with Dallas on this one. 'local!x' is the coding equivalent of shrugging your shoulders. Let's be better than that.
TA
Tamra
2 years ago
B) local!applicantHeight - This employs the naming convention of specifically describing the value contained by the variable.
SH
Shawnta
2 years ago
A) local!hoaa - This employs the naming convention of abbreviating 'Height of an applicant' to minimize both the typing required by developers and the length of code Appian is required to parse.
HO
Howard
2 years ago
I disagree, I believe option A is more efficient in terms of typing and code length.
CA
Carissa
2 years ago
I think option B is the best choice because it clearly describes the variable.
DA
Dallas
2 years ago
Using 'local!x' just feels lazy. Might as well call it 'local!whatevs' while we're at it.
DA
Darci
2 years ago
Definitely 'local!applicantHeight'. Keeping variable names explicit and meaningful is a no-brainer for Appian best practices.
CH
Chantay
2 years ago
'local!x' might be confusing for future developers, 'local!applicantHeight' is much clearer.
RE
Rebbecca
2 years ago
I think 'local!hoaa' is too vague, we should stick with 'local!applicantHeight'.
VE
Venita
2 years ago
I agree, 'local!applicantHeight' is definitely the best choice.
GI
Gilbert
2 years ago
Hmm, 'local!hoaa' seems a bit too cryptic. I prefer 'local!applicantHeight' - it's clear and descriptive.
BR
Brunilda
2 years ago
Yeah, 'local!hoaa' is too cryptic, 'local!applicantHeight' is much better.
LO
Lon
2 years ago
I prefer 'local!applicantHeight' as well, it's easier to understand.
HY
Hyman
2 years ago
I agree, 'local!applicantHeight' is clear and descriptive.
LA
Lavonda
2 years ago
I think 'local!applicantHeight' is the best choice.