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

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

• A. refreshOnVarChange: local!username
• B. refreshOnVarChange: local!usernameLastModified
• C. value: now()
• D. refreshOnEvent: local!username

Answer: (A)

The idea is to refresh a value based on another variable’s change so you can capture the moment of change. In Appian, a!refreshVariable re-evaluates its value when something it depends on changes. By tying the refresh to the username variable, the refresh runs precisely when the username changes, allowing you to set the timestamp to now() at that moment and store it in local!usernameLastModified. Using refreshOnVarChange with local!username ensures the timestamp updates only as soon as the username updates. The other options either trigger on the timestamp itself, on some unrelated event, or without a trigger tied to the username change, so they wouldn’t reliably update the timestamp at the moment the username changes.

The idea is to refresh a value based on another variable’s change so you can capture the moment of change. In Appian, a!refreshVariable re-evaluates its value when something it depends on changes. By tying the refresh to the username variable, the refresh runs precisely when the username changes, allowing you to set the timestamp to now() at that moment and store it in local!usernameLastModified. Using refreshOnVarChange with local!username ensures the timestamp updates only as soon as the username updates. The other options either trigger on the timestamp itself, on some unrelated event, or without a trigger tied to the username change, so they wouldn’t reliably update the timestamp at the moment the username changes.