I'm frequently asked if it's possible to setup FME Desktop with some default configuration e.g. Proxies, Shared folders, database connection file locations, window layout, transformer versions turned on, number of recent workspaces set to 10 etc... and then save that off as a config file that can be deployed to other installations of FME Desktop in an organisation. Currently the closest option to this is a silent install, or packaging FME, but that's much more of an admin overhead.
It feels like with 2019's ability to save presets in Transformers we're going in the right direction, so here's a suggestion along the same theme that will help organisations with more than a couple of installations of FME Desktop.
An addition to such a feature: run FME Desktop with different (eg: saved) configurations/profile.
When I want to do changes in a user's environment I need to change multiple settings in FME Options to switch to that env (default path, connection location, etc). Running FME with a saved config would be much more convenient and quick.
I have cobbled together something of a workaround in answer to my own question on https://knowledge.safe.com/idea/96245/environment-testersetter.html
Might not work for everyone.
Would definitely be a great enhancement to daily work !!
I fully support this idea - we package up FME for staff to deploy, and want to set a default shared directory for all web connections to ensure everyone is using the same ones, especially when publishing to FME Server.
@davideagle I cannot find any option in the silent install documentation about setting default shared folders. Are you able to clarify how this would work?