We are looking for a way to ensure that certain functionality is always executed after a user has closed a certain screen (an opened document) in a flow in the Universal GUI. We have created a task that closes the screen and executes the functionality. But if the user closes the screen (document) itself, this functionality is not performed.
It is essential that this functionality is always executed (this sets triggers for synchronization with another application).

Is there a way to somehow enforce this? Or can we prevent the user from closing the screen without using the task?

These items do talk about on-close events in various forms, but there doesn't seem to be a solution

Close document starting point process flow | Thinkwise Community (thinkwisesoftware.com)

Process flow after close document | Thinkwise Community (thinkwisesoftware.com)