BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Appian Exam ACD100 Topic 3 Question 38 Discussion

Actual exam question for Appian's ACD100 exam
Question #: 38
Topic #: 3
[All ACD100 Questions]

In a rule, there is a variable named local!numberOfCustomers which will eventually change value.

You are tasked with creating a variable that captures the original value so that you can later compare the original and new value.

Which parameter settings should you use for your new variable?

Show Suggested Answer Hide Answer
Suggested Answer: B

Referencing another local variable creates a dependency between the two variables and ensures that the referenced variable is always evaluated first.


Contribute your Thoughts:

Tandra
1 months ago
Hold up, is this a trick question? I bet the answer is none of the above, and we have to write our own custom code to do this. That's how they get you, you know.
upvoted 0 times
Maile
2 days ago
C) refreshOnReferencedVarChange: true
upvoted 0 times
...
Reita
11 days ago
B) refreshOnReferencedVarChange: false
upvoted 0 times
...
Sharita
16 days ago
A) refreshAlways:true
upvoted 0 times
...
...
Glory
1 months ago
Bah, who needs to keep track of the original value? Just use the new one, it's more exciting that way!
upvoted 0 times
Dorothy
15 days ago
Nah, I prefer using the new value, keeps things interesting.
upvoted 0 times
...
Nell
19 days ago
I agree, it can be useful for comparison later on.
upvoted 0 times
...
Shawn
22 days ago
I think it's important to keep track of the original value.
upvoted 0 times
...
...
Tasia
1 months ago
Ooh, I bet option A is the one! Refreshing the variable all the time sounds like the safest bet.
upvoted 0 times
...
Cristina
2 months ago
Hmm, I'm not sure. Option D seems to make the most sense to me, since it directly references the variable we're interested in.
upvoted 0 times
Lera
19 days ago
Yeah, that could work. Let's go with option C.
upvoted 0 times
...
Alisha
26 days ago
That's a good point. Maybe we should go with option C instead.
upvoted 0 times
...
Halina
1 months ago
But what if the variable changes before we compare?
upvoted 0 times
...
William
1 months ago
I think option D is the best choice.
upvoted 0 times
...
...
Raina
2 months ago
I'm not sure, but I think refreshOnReferencedVarChange: true could also work for this scenario.
upvoted 0 times
...
Isabelle
2 months ago
I disagree, I believe refreshOnVarChange:local!numberOfCustomers is the best option to capture the original value.
upvoted 0 times
...
Malcolm
2 months ago
I think option C is the way to go. Refreshing the variable whenever the referenced variable changes is the best way to keep the original value up-to-date.
upvoted 0 times
Lindy
1 months ago
True, option C provides a more general approach to tracking changes in the variable.
upvoted 0 times
...
Rickie
1 months ago
I think option D might be too specific, option C covers all changes to the referenced variable.
upvoted 0 times
...
Shizue
1 months ago
But wouldn't option D also work since it specifically references the variable we want to track?
upvoted 0 times
...
Wilda
1 months ago
I agree, option C seems like the most logical choice.
upvoted 0 times
...
...
Dudley
2 months ago
I think we should use refreshOnReferencedVarChange: false for the new variable.
upvoted 0 times
...

Save Cancel