I’d like to suggest an improvement related to the “Open File” trigger action in Tulip Player.
Currently, when opening a file (for example, a PDF), a warning message appears every single time. While we understand the security intent, this becomes disruptive in production environments where operators frequently access trusted, internal documents like SOPs or reference PDFs.
What’s a bit confusing is that:
The warning does not appear when opening a folder
It always appears when opening a file
There’s no option to configure or suppress it
This leads to an inconsistent user experience and adds unnecessary clicks for operators during daily workflows.
Is there a reason that you are using the open file action for this, as opposed to using the file variable type, and the variable widget to render this file directly in the player?
You hit the nail on the head, the added confirmation step there is primarily to give the user more explicity understanding of any added risk that might come with opening that file (and leaving the player).
The reason we open the file this way is because it’s a local file stored on a shared network drive. This file is frequently updated, and all engineers are connected to the same network drive in our facility. When an engineer updates the file and saves it in that directory, the latest version becomes immediately available in Tulip without requiring anyone to reopen the app or manually re-upload the file.
