-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for deleting subform-layoutset #13482
Comments
Originally posted by @mlqn in #13680 (review) As @mlqn pointed out, deletion of layoutsets does not sync applicationmetadata or bpmn references, where fileupload might be relevant for subforms if they are allowed within the layout. Update: |
Tested OK:
Also verified that the "Delete subform" button is only available when a subform layoutset is selected. A few observations that probably go a little beyond this issue:
Since we are still working on the UX of how the user should experience managing subforms, I suggest we don't to anything about this for now, since we might be changing things anyways. The actual functionality of this issue (deleting the subform layout-set) seems to be working as expected 🥳 |
We need to support deleting layout sets in general, but in this task, we must specifically address deleting layout sets for subforms. How should we approach this?
Suggestion:
We notify the user that all subforms using the layout-set that is being deleted will also be removed. Then, we send a delete request to the backend, which will update all necessary locations. After that, the backend will provide us with information via web sockets about the files that have been changed, allowing us to invalidate queries on the frontend accordingly. (We do already have web-sockets and invalidaiton setup ready for use).
The text was updated successfully, but these errors were encountered: