Hi Bram,

The Close document process action is not a valid starting point for a process flow. I do see that the documentation is misleading and can make you thing it could be a starting point.

We will put a list of valid starting actions onto our documentation page in the near future and change the explanation text of this process action. 

Edited (5-6-2024): Process flow actions | Thinkwise Documentation (thinkwisesoftware.com)
Close document can be a starting point of a process flow in Universal

Kind regards,
Mark Jongeling

Is there a way to either prevent manually closing a document or triggering an action (alongside with the record_id of the selected record) when a document is closed?

Hi Roy,

It is currently not possible to prevent the user from closing documents/screens nor to trigger an action when a document/screen is closed. 

To add, there is an Extended property called 'ShutdownProcedure’ you can use when the GUI gets closed by the user. This is execute the named procedure.

Feel free to create an Idea for this. Do add some examples for when this is handy 

Hi Mark

The Extended property probably applies to closing the GUI completely, so the entire application?
Is it somehow possible to link something like that to a specific screen?
We are looking for some kind of "on close-event" so that we can execute a follow-up in a flow after the user closes the (previously opened) input screen. We have now created an extra task for this that the user can start. But if the user does not use this task to close the screen, but simply "clicks away" the screen, the (subsequent) process flow started with this task will of course not be executed.