Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
My requirement is to refresh my related action button when any event happens and the visibility for the related action set to false
Discussion posts and replies are publicly visible
Which kind of event is happening? Whenever another related action occurs, even when it's in a modal, Appian will reevaluate the visibility expression once the modal closes.
ok, Assume I have 2 related action
1. Add service to account(visibility criteria acct_status="Active")
2. Deactive Account- will make acct_status= "Deactive"
When a user clicks on any active Account from the record list and stays on the record view. meanwhile, another user deactivated the same account and change the status from "Active" to "Deactive", Then the first user still sees the 1st related action. How does it get refreshed without reloading the page
Unknown said:Then the first user still sees the 1st related action. How does it get refreshed without reloading the page
There's no direct way to do this. If you're worried about this race condition, the main thing I'd suggest you implement is an in-process check which checks the status of (a freshly-queried copy of) the Account Status, and if it's already been deactivated, simply route the process flow to an end node (or potentially to a separate task with a read-only display informing the user that it's been previously deactivated).
I actually don't think that's necessary. I believe Appian reruns the visibility expression once an action is clicked to ensure the users can't access something they shouldn't be able to
yes, but is there a way to refine the Appian error message for such scenario?
Danny Verb said:I believe Appian reruns the visibility expression once an action is clicked
That would certainly be interesting, but I've never observed this.