The Scripting Options are available only within the Enterprise Edition of zsDuplicateHunter. The Scripting Options give you control over the default locations where scripts and results are stored as well as control over how the filename of the results is generated and what is displayed after the script has run.
The Scripts Folder stores the default path which is used when opening and saving scripts. The Results Folder stores the folder to which all results will be written.
The Results Display Type controls what zsDuplicateHunter displays after a script has been run. The default option, Display full report after run will display an HTML report with the results of the script including each step that was run. The Display pass/fail after run option will simply display a message after the script has run stating whether or not the script has passed or failed. ZsDuplicateHunter determines if the script has passed or failed based on the Script Passes variable. You can optionally display the results from the message informing you if the script passed or failed. The Display nothing after run option will not display anything after the script has finished. You can check the results by opening the result file for the script which will be in the Results Folder.
The Include Date in Report Filename option determines whether or not zsDuplicateHunter includes the date in the name of the results file when it writes the report for the script results. By including the date, you can track a history of the script results. However, including the date will cause a new file to be created with each run of the program. Be sure to periodically archive your results to save hard-drive space.
The Log actions during run options allows you to log each action that is run to the zsDuplicateHunter log file which is located in the directory where you installed zsDuplicateHunter. This option can be useful to debug a script if you have created an infinite loop, or if the script does not finish.
The Global Variables section allows you to create variables which are used for all script runs. With global variables, you can make your scripts more robust by taking out common information from the script and creating a global variable for it. For example, if you are calling a large number of scripts, you could create a global variable which contains the path of the script and then reference the global variable within your scripts. Or, if you are running zsDuplicateHunter on different operating systems, you can define a global variable for the operating system and then branch within the script depending on the current operating system. The Add Global Variable button adds a new row to the Global Variables table. The Remove Global Variable button removes the currently selected row or rows. |