We have multiple schedules to control a rather complex synchronization topology (the complexity is a functional requirement in our environment, global enterprise, failover servers, near-real-time data needs, etc) This works very well and has been tried and true for some time.
However, we need to update many of these profiles frequently to simply switch a subdirectory. This happens multiple times per day, once for each session we run (name of the session), and is the same across many profiles. The problem is, the (session) subdirectory naming scheme can't be comprised out of the existing variables that Syncovery provides.
Updating a system environment variable would be absolutely ideal to update all profiles and reduce the risk of an accidental type-o, or profile configuration change. This works, and Syncovery will pick up the environment variable upon application start, but it will not update after it is changed in the system. We would have to close and re-start the application and the scheduler, which isn't really an option as the scheduler is essentially constantly in the process of handling other jobs.
Would updating syncovery to refresh the environment variables at the start of every job (either attended or unattended scheduler) be an option in a future update? Or provide another way for users to create their own custom "syncovery-wide" variables?
This way, we can simply update an environment variable to update 30+ sync profiles. This would remove the need to even edit profiles for us. This will also reduce the risk of the operator making an accidental change inside the profile, since they won't go into the edit dialog anymore (which we have had happen before, an accidental switch from smart tracking to exact mirror and "move" has caused much grief before)
Thanks,
-Scott