MENU
You should consider using a field value when the list of allowed values is ______________.
Suggested Answer: B
Get Premium PEGACPSA23V1 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
You would typically use a field value in Pega when the list of allowed values is:
B . Mostly static. Field values are best used for lists of allowed values that do not change frequently. They enable the use of predefined, constant values across the application, providing consistent data references for fields that have a set list of options.
28 comments · newest first
SH
Shawn
10 months ago
A is too limiting, right?
BE
Bernardo
11 months ago
Wait, are we sure about D? Seems off.
LA
Lauran
11 months ago
C makes sense too, but I'm not sure.
TH
Thurman
11 months ago
Definitely agree with B!
RH
Rhea
11 months ago
I think B is the best choice.
ST
Stevie
12 months ago
I definitely remember discussing when to use field values, and I think it might be when there are three or fewer items.
MA
Mattie
12 months ago
I’m leaning towards option B, but I also recall something about shared values across case types. It’s a bit confusing.
RI
Rikki
12 months ago
I feel like we practiced a question similar to this, and it was about case types. Maybe it's specific to one case type?
MI
Mirta
1 year ago
I think I remember that field values are useful when the list of allowed values is mostly static, but I'm not entirely sure.
JO
Jovita
1 year ago
I'm a little confused by this question. The options seem quite similar, and I'm not sure I fully understand the distinction between them. I'll have to re-read the question and options a few times to make sure I'm on the right track.
AL
Aleta
1 year ago
Okay, I've got this. The key is to focus on the list of allowed values. If it's a short, fixed list, then option A is the way to go. If the values are more dynamic or shared across cases, the other options become more relevant. I feel confident I can nail this.
TE
Tequila
1 year ago
Hmm, I'm a bit unsure about this one. The wording is a bit tricky, and I'm not entirely sure what the difference is between "mostly static" and "specific to one case type." I'll have to think this through carefully.
VI
Viva
1 year ago
This seems like a straightforward question about when to use a field value. I'll carefully read through the options and think about the scenarios where a limited set of values would be appropriate.
KA
Karl
1 year ago
I recall something about removing static ACLs. Maybe we shouldn't consider the extended access-list option at all?
KA
Katina
2 years ago
I'm not sure, but I think D) shared across all case types could also be a valid option for consistency.
BR
Brandon
2 years ago
I agree with Joye, because using a field value specific to one case type makes sense for organization and clarity.
SO
Sol
2 years ago
Shared across all case types? That's a bit too much flexibility for my liking. I'm sticking with C, thank you very much.
ON
Oneida
2 years ago
I prefer the simplicity of having a field value specific to one case type.
DI
Dierdre
2 years ago
I think having a shared field value across all case types can lead to confusion.
WE
Wei
2 years ago
I agree, having values specific to one case type makes things more organized.
AD
Adela
2 years ago
Specific to one case type? That's my jam! I'm all about that C option, keeping things nice and tidy.
KR
Kristeen
2 years ago
Mostly static, huh? Well, that's just the kind of predictability I crave in my life. Sign me up for option B!
CA
Candra
2 years ago
A field value is definitely the way to go when the list is three or fewer items. Nice and simple, just the way I like it!
LO
Louvenia
2 years ago
True, but field values are more suitable for smaller lists.
AN
Annamae
2 years ago
B) mostly static
ZA
Zana
2 years ago
That's right, it keeps things clean and easy to manage.
LA
Latia
2 years ago
A) three or fewer items
JO
Joye
2 years ago
I think the answer is C) specific to one case type.