views and action security refresh

RE: views and action security refresh

alex.acosta — Tue, 14 Apr 2026 16:38:09 GMT

I would recommend changing the a!recordActionField() to use either the "MENU" and "MENU_ICON" with securityOnDemand set to true, this way the security evaluates when the user clicks to open the menu. Keep in mind that a!refreshVariable() with refreshAfter: "RECORD_ACTION" only controls when a local variable’s value is recalculated after a record action dialog completes; it does not control when the record action’s own visibility/security is re‑evaluated.

RE: views and action security refresh

saisaran31 — Thu, 09 Apr 2026 08:47:35 GMT

Thanks for your reply Shubham Aware and Stefan Helzle . Now i came up with the solution that to have a refresh related action in the record header so that when a user clicks the entire record get reloaded similar to a browser refresh

RE: views and action security refresh

Stefan Helzle — Thu, 09 Apr 2026 05:51:23 GMT

To refresh data, I typically use some local variable. Then, I wrap all the queries I want to trigger into a refresh variable referencing this local. Then, I modify that local using a button or link.

RE: views and action security refresh

Shubham Aware — Thu, 09 Apr 2026 05:16:07 GMT

Record action visibility defined in Views & Actions is evaluated at page load time, not on a!refreshVariable(). Even with a start form or refresh action, Appian does not re-evaluate action-level security mid-session without a full page reload.
You can try to move the visibility logic entirely into the child interface using a local variable that refreshes with your data. Remove it from Views & Actions.