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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Appian Exam ACD101 Topic 2 Question 20 Discussion

Actual exam question for Appian's ACD101 exam
Question #: 20
Topic #: 2
[All ACD101 Questions]

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?

Show Suggested Answer Hide 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 Olga at Sep 07, 2024, 04:04 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Pamella
1 months ago
I think both options could work, but refreshOnVarChange might be more efficient in this case.
upvoted 0 times
...
Colton
2 months ago
Haha, I'm just picturing the developer who thought 'refreshInterval: 0' was a good idea. That's a recipe for a never-ending loop!
upvoted 0 times
Margart
7 days ago
User 4: Or just set refreshAlways to true to be safe.
upvoted 0 times
...
Zena
9 days ago
User 3: Maybe refreshOnVarChange: local!username would be a better option.
upvoted 0 times
...
Lou
10 days ago
User 2: I agree, it would just keep refreshing non-stop.
upvoted 0 times
...
Alpha
12 days ago
User 1: Yeah, setting refreshInterval to 0 is definitely a bad idea.
upvoted 0 times
...
...
Craig
2 months ago
A is not going to work at all. We need the variable to refresh, not stay static.
upvoted 0 times
Nana
30 days ago
Then maybe option B) refreshOnVarChange: local!username would be the best choice.
upvoted 0 times
...
Miesha
1 months ago
No, that won't work. We need the variable to refresh, not stay static.
upvoted 0 times
...
Valentin
1 months ago
I think we should go with option C) refreshAlways: true.
upvoted 0 times
...
...
Irma
2 months ago
But if we want the timestamp to be updated whenever the username field is modified, shouldn't we use refreshOnVarChange?
upvoted 0 times
...
Novella
2 months ago
I disagree, I believe the correct answer is C) refreshAlways: true.
upvoted 0 times
...
Elfriede
2 months ago
C seems a bit overkill, don't you think? Refreshing it constantly would be a waste of resources.
upvoted 0 times
...
Darci
2 months ago
Hmm, I think B is the way to go. Refreshing the variable whenever the username changes makes perfect sense.
upvoted 0 times
Kanisha
29 days ago
Definitely, having it refresh on username change will give us the most accurate information.
upvoted 0 times
...
Ora
30 days ago
I agree, B seems like the most logical option for keeping track of when the username was last modified.
upvoted 0 times
...
Detra
1 months ago
Yeah, that sounds like the right choice. It will ensure the timestamp is always up to date.
upvoted 0 times
...
Ruby
2 months ago
I think B is the way to go. Refreshing the variable whenever the username changes makes perfect sense.
upvoted 0 times
...
...
Irma
2 months ago
I think the answer is B) refreshOnVarChange: local!username.
upvoted 0 times
...

Save Cancel