Appian Exam ACD101 Topic 1 Question 16 Discussion

Actual exam question for Appian's ACD101 exam

Question #: 16
Topic #: 1

You are configuring a local variable on an interface to store the date and time that the username field was last modified. The local variables are currently configured as follows:

Which a!refreshVariable configuration should be added so that local!usernameLastModified stores the correct timestamp?

ArefreshInterval: 0

BrefreshOnVarChange: local!username

CrefreshAlways: true

Show Suggested Answer

Suggested Answer: B

The a!refreshVariable function should be configured to refresh when the local!username variable changes. This is achieved by setting the refreshOnVarChange parameter to local!username, which will update the local!usernameLastModified variable with the current timestamp whenever local!username is modified. Reference:

Appian Documentation: a!refreshVariable Function

by Bettina at Jul 05, 2024, 06:11 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Daren

11 months ago

Ah, the age-old question of when to refresh a variable. I say we go with the sassy option C, 'refreshAlways: true'. That way, we can keep our users on their toes, wondering when the timestamp will change next!

upvoted 0 times

Darell

10 months ago

I'm with User2, let's keep it sassy with refreshAlways!

upvoted 0 times

...

Jenelle

10 months ago

I disagree, I prefer option C) refreshAlways: true.

upvoted 0 times

...

Melina

11 months ago

I think we should go with option A) refreshInterval: 0.

upvoted 0 times

...

Sherman

11 months ago

I think refreshInterval: 0 would be the best option to update the timestamp immediately.

upvoted 0 times

...

Luis

11 months ago

Wait, wait, wait... why would we want to refresh the variable every single time? Wouldn't that be a bit overkill? I reckon option B is the way to go - it'll only update the timestamp when the username actually changes.

upvoted 0 times

...

Mitsue

11 months ago

Hey, that's not a bad idea! Keeping 'em guessing, eh? Although, I do worry it might drive our users a little crazy. Maybe we should just stick with the sensible option B and call it a day.

upvoted 0 times

Destiny

10 months ago

Malcolm: Sounds good to me. Option B it is!

upvoted 0 times

...

Rasheeda

10 months ago

Agreed, let's stick with option B and move on.

upvoted 0 times

...

Malcolm

11 months ago

Yeah, that sounds like the most sensible choice.

upvoted 0 times

...

Ciara

11 months ago

I think we should go with option B.

upvoted 0 times

...

Ciara

12 months ago

But wouldn't refreshAlways: true ensure that the timestamp is always up to date?

upvoted 0 times

...

Roselle

12 months ago

I disagree, I believe refreshOnVarChange: local!username is the right choice.

upvoted 0 times

...

Ciara

12 months ago

I think the correct configuration should be refreshAlways: true.

upvoted 0 times

...

Linette

12 months ago

Okay, so we need to configure the refreshVariable to store the timestamp of when the username field was last modified. I think option B is the correct answer here, since it will refresh the local!usernameLastModified variable whenever the local!username variable changes.

upvoted 0 times

Gaston

11 months ago

Definitely, using refreshOnVarChange with local!username ensures that local!usernameLastModified stays up to date with any changes to the username field.

upvoted 0 times

...