Hi,
Discussion posts and replies are publicly visible
cedric01 said:button displayed by a Related action.
Can you clarify a bit what you mean by this exactly?
My interface, is a RecordType view.
In this latter I have a related Action (let's call it "Enclose") and the visibility condition of this action depends of an ER that gets the History data described above.
The "Enclose" button is initially displayed.
So when I click on the Refresh button previously seen, I would need to trigger the refresh of the RecordType, and therefore to refresh the Visibility condition of the Enclose action (recall the ER).
With the Refresh button, all the data in that interface are now well refreshed, but the "Enclose" button keeps displayed, because the action was not refreshed.
If you're talking about a related action that shows in the top border of a record view, i'm pretty sure that the data used for that related action's visibility is completely outside of the scope of the local variables in your interface that you're refreshing, etc. I would expect a browser-level refresh might be needed to get that re-evaluated.
If you're talking about a related action housed in an on-form Record Action field, then.. well i'm less sure what the interplay is there. It may do its own evaluation and caching on the back-end ahead of time.
The related action I'm talking about has been added in the interface using the a!recordActionField function : a!recordActionField( actions: { a!recordActionItem( action: 'recordType!history.actions.enclose', identifier: ri!history.history_id ),