When using the Records Manager Landing page to display a Data Type, I configured Actions on the Data Type which generate a Flow Action. In that Flow Action, I set Form Refresh settings for a specific property. Although the property value changes in the UI, the Form Refresh does not trigger. This behavior occurs in the data-only context (Records Manager/Data Type) but appears to work in case context.
Expected Behavior:
Changing the configured property in the Flow Action should trigger the Form Refresh, updating dependent UI immediately.
Actual Behavior:
Property change is reflected in the UI, but the Form Refresh does not fire—dependent UI does not update. No visible errors; no server calls indicating a refresh.
@robotvinay The /refresh endpoints only exist on case and assignment level, not data level. Hence why it doesn’t get triggered when updating a data record. And from a usability point of view, I would try to stay away from embedding logic into data record authoring. If you have a process for updating accounts, I would wrap a process around it instead of doing direct CRUD operations. For simple updates it could make sense sometimes, but you seem to have a more complex authoring scenario.
@robotvinay just to add to @LantzAndreas advice, this is a space we know needs to improve. We have an item on product backlog addressing this space: Data objects support “refresh” endpoint (EPIC-101580). Does not help you now, but hope this knowledge helps.
I was just trying these things as they are already available as part of new actions creations for any dataobject.
It would be really nice once these features comes to the Data context too
