Hi Ramon!
Thanks for bringing this to our attention. I think the best solution would be to reload dynamic folders which are configured to automatically load on startup/load after the save operation. I will see that this gets implemented until the next release.
One last question: are you using Windows or macOS on the client side?
Regards,
Stefan
Sorry, I forgot to respond to that. We use Windows.
Just to let you know, the next release will now reload all configured dynamic folder when saved to a Royal Server.
Stay tuned...
Related to this request (I'm on macOS), it would be wonderful if reloading a dynamic folder did not disconnect active connections (sessions) for any connections that are children of the dynamic folder. If the particular connection definition which my active session is launched from is in RAM, and has not changed during/after the reload, keeping the active session alive would be a welcome improvement.
If you prefer I open this as a separate thread, please let me know.
Thanks,
Alan.
Hi Alan,
to better track this particular issue, please open a thread in the appropriate forum for the client. Thank you!
Stefan
Ramon Medina
We have a Dynamic Folder that looks up our Keeper Secrets Manager credentials using PowerShell. We set it to automatically load, and it does do that on startup.
However, if any change is made to the document to cause it to automatically save, the contents of the Dynamic Folder disappear, and do not reload automatically. We have to manually right-click on it and choose Reload.
We don't have this problem if we create a document outside of Royal Server that is not shared, as the contents can be cached.
Two potential solutions (for us) would be to either allow Dynamic Folder contents to cache in RAM only, so they don't disappear when the document saves but also are not written to disk. Or, include another option such as "Reload Automatically after Save."