Hi all,
is there a way to prevent users from interacting with the Workshop UI after they click an Edit/Save action until the action completes? I’m using purely Workshop (no custom frontend), and I’d like to “lock” the UI or disable interactions while the action is running.
This is an interesting request, I don’t think we’ve heard this one before. Typically users are looking for more minimal loading states if anything.
We have seen some issues though where users can begin working and after the action completes some object sets/variables may reload and wipe out what the user was working on so I could see this being a valid configuration option in the future.
We could also do this via something like a variable backed by the loading state of a particular action which would let you set an overlay that can’t be closed to visible with variable backed overlay state.
I will make internal note of this feature request, but for now I’d recommend searching for an alternate pattern that will work for your use case.
1 Like
Hi @evanj ,
I also what to add on as we are working on something similar, we use a custom iframe widget that lets users make changes which are then written back to the same backing dataset. We’ve managed to show a loading popup inside the iframe, but the core issue still remains — if multiple users are working at the same time, we don’t have a clear way to handle concurrency (or locking). Ideally, only one users’ changes for a given value combination should persist, or there should be some queueing mechanism to avoid overwriting/reloading each other’s edits.
Right now, if one user saves, the entire iframe reloads for everyone using the app, which causes other users to lose any unsaved edits unless they happen to submit first. So even though we tried to abstract away from Workshop app it ended up creating a new set of challenges instead of solving the original one. Im curious to know if there is already a fix available.
@Benutzer7 there is a great guide on how to set up proper locking here from @Joel !
https://community.palantir.com/t/workshop-dashboard/5665/2?u=phil-m
4 Likes
Thank you for the response. Yes this is what I have been doing; through creating an overlay after the action is trigger.