Appian Exam ACD100 Topic 3 Question 38 Discussion

Actual exam question for Appian's ACD100 exam

Question #: 38
Topic #: 3

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?

ArefreshAlways:true

BrefreshOnReferencedVarChange: false

CrefreshOnReferencedVarChange: true

DrefreshOnVarChange:local!numberOfCustomers

Show Suggested 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.

by Tegan at Sep 13, 2024, 06:37 PM

Limited Time Offer

25%

Off

Get Premium ACD100 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Tandra

2 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

Hermila

17 days ago

Let's double check the requirements before jumping to conclusions.

upvoted 0 times

...

Earleen

18 days ago

Yeah, it does seem like a tricky question. Custom code might be the way to go.

upvoted 0 times

...

Beckie

19 days ago

I think you might be right, we might have to write custom code for this.

upvoted 0 times

...

Billye

22 days ago

D) refreshOnVarChange:local!numberOfCustomers

upvoted 0 times

...

Maile

25 days ago

C) refreshOnReferencedVarChange: true

upvoted 0 times

...

Reita

1 months ago

B) refreshOnReferencedVarChange: false

upvoted 0 times

...

Sharita

1 months ago

A) refreshAlways:true

upvoted 0 times

...

Glory

2 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

1 months ago

Nah, I prefer using the new value, keeps things interesting.

upvoted 0 times

...

Nell

1 months ago

I agree, it can be useful for comparison later on.

upvoted 0 times

...

Shawn

2 months ago

I think it's important to keep track of the original value.

upvoted 0 times

...

Tasia

2 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

1 months ago

Yeah, that could work. Let's go with option C.

upvoted 0 times

...

Alisha

2 months ago

That's a good point. Maybe we should go with option C instead.

upvoted 0 times

...

Halina

2 months ago

But what if the variable changes before we compare?

upvoted 0 times

...

William

2 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

3 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