Hi Dojo,
we are working on a solution to save comments in a memory file. This part works good: in a Visio the user can type text into a shape to set a session variable, which then is saved into a memory file (DataMiner own; Automation -> memory file) by a custom automation script. Reading from the file is also possible: when a user starts an automation script to read from the memory file, the value (comment) then is presented nicely using the same session variable.
The issue here is that we try to find a way to have the new/updated comment to be presented for all users connected to the system that currently have opened the corresponding visual. We haven't figured out yet how to achieve this... so far, every user manually has to start the read script, so that the session variable is updated with the comment from the memory file.
Any ideas how to smoothen the user experience here? 🙂
Thanks a lot!
Hi Nils,
Maybe executing the script when opening the page could help?
How to execute an automation script on visio page opening
Hope it helps.
Hi Nils,
Maybe I am missing something but the execute script option is available at page level (not shape level). The script that will be executed will be the one defined in the page. I don’t expect that other script defined in shapes will be executed. Please could you confirm if this is the case?
Hi Miguel,
we’ve looked into this once again, and of course, you are absolutely right! Defining the Execute on the page level works perfectly fine with the ExecuteSetsOnInit option.
This solves only half of our problem, but at least with this we can force a refresh when the page is freshly opened. We still have to find a way to force a refresh while the page is already displayed…
Hi Nils,
A possible workaround is to force the refresh is to run the script via scheduler. For example you could run the script every x amount of minutes. However, it is true that this workaround will not fully cover your requirement.
Apart from that I believe there is no other option to force refreshing overviews when there is an update in a memory file.
If this requirement is a must in your integration, then a connector could be the best option.
Hi Miguel,
thanks for your feedback. We’ve already looked into this, but using the ExecuteSetsOnInit option would lead to an execution of all the scripts – including the one writing a comment into the memory file and therefore deleting the entry already saved in the file…