Since Version 2, Build 2011, ViceVersa PRO supports local and global scripts. Scripts can be setup to run before and/or after a profile execution.
Typically scripts before profile execution are run to prepare the computer environment. For example, mapping a network drive or connecting to a network resource. Instead, scripts after profile execution are run to disconnect from the network or to report, e.g. via e-mail, the results of a synchronization or a backup.
Scripts can be Visual Basic scripts (*.vbs), batch files (*.bat, *.cmd) or Java scripts (*.js)
Scripts can be global (a global script is run for all profiles) or local (a local script is only run for one profile).
Global scripts must be located in the "GlobalScripts" folder in the ViceVersa PRO installation folder, usually 'c:\program files\ViceVersa PRO2\GlobalScripts'
They must be called global_start.ext (global_start is the global script to run when a profile starts) or global_end.ext (global_end is the global script to run when a profile ends). .ext can be one of the supported extensions, that is .vbs, .js, .bat or .cmd
If you need to define multiple start scripts, the first script must be called 'global_start.ext', the second one 'global_start_1.ext', the third one 'global_start_2.ext' and so on, up to a max of 9. Same mechanism for the global end scripts: the first must be called 'global_end.ext', the second one 'global_end_1.ext', the third one 'global_end_2.ext' and so on, up to a max of 9.
Once you have created and placed your global scripts in the GlobalScripts folder, you will need to activate the option "Run custom scripts before comparison" and/or "Run custom scripts after execution" in the profile settings for the profiles you wish to run the scripts for. If you do not activate these profile options, the profile will not run the global scripts before and/or after execution.
Local scripts are run only for a specific profile. Differently from global scripts, local scripts must be located in the same folder as the ViceVersa profile file (.fsf file) and they must be called 'profilename_start.ext' for the script to run before execution, or 'profilename_end.ext' for the script to run after exection; profilename is the name of you profile, which you want to run the local script for. .ext can be one of the supported extensions, that is .vbs, .js, .bat or .cmd
Also for running local scripts, you will need to activate one or both the options "Run custom scripts before comparison" and "Run custom scripts after execution" in the profile settings for the profiles you wish to run the local scripts for.