In the [BlueZone] section, you can configure the backup working directory folder and set the time it takes for the BlueZone session to automatically disconnect. You can also hide specific configuration dialog buttons.
[BlueZone] ;BackupWorkingDir=PathOfBackupWorkingDirectory ;KeyboardInactivityTimer=NumberOfMinutes AppendVersionToWorkingDir=No AllowCrossVersionInterop=Yes ;HideDialogButtons=
Sets the path to the back up working directory. This entry is commented out by default. You must delete the semicolon to enable this feature.
You can add a custom backup folder where BlueZone saves a backup copy of the working directory. If the backup working directory is configured, every time BlueZone writes to a file (creates or saves a profile, script, macro, VBA project, power pad file, dialog file, and so on), the file is also copied to the backup working directory.
If the primary working directory is unavailable, BlueZone automatically switches to the backup working directory.
You can also include environment variables in the path between angle brackets or percent characters. For example:
BackupWorkingDir=%USERPROFILE%\BlueZone
For example, if the following is set, after 20 minutes of inactivity, the BlueZone session will automatically disconnect:
KeyboardInactivityTimer=20
When set to AppendVersionToWorkingDir=No, the default value, no version number will be appended to the working directory path when BlueZone is upgraded. All of the user's previously created certificate, configuration, log, macro, script, spool, trace, and transfer files will be available to the newly installed version.
It is recommended that end users keep the default value of No so the files will be immediately available after an upgrade.
When set to AppendVersionToWorkingDir=Yes, the major version number is appended to the working directory.
Configuring this setting to Yes is useful for administrators who must run multiple version of BlueZone Web-to-Host or want to test a new version before going live.
If an end user configures this setting to Yes, the previously created certificate, configuration, log, macro, script, spool, traces, and transfer files are kept separate from the newly installed version. To continue to use these files, the user must copy the files to the new directory structure.
When set to AllowCrossVersionInterop=Yes, the default value, older versions of BlueZone can communicate with newer versions. For example, if you have versions 5.1 and 6.1 installed, version 5.1 will communicate with version 6.1.
This setting effects functionality such as , , ActiveX events, and whether the host automation objects and HLLAPI DLLs can connect to a different version of BlueZone.
To specify a specific version, refer to “Multiple side-by-side versions of BlueZone” in the BlueZone Advanced Automation Developer’s Guide. If no version is specified, the latest registered version of the BlueZone Host Automation Object is used.
When set to AllowCrossVersionInterop=No, different versions of BlueZone do not communicate.
Default button = 1
Open button = 2
Save As button = 8
Help button = 16
To hide a single button, type the value. For example, to hide the Open button, type HideDialogButtons=2.
To hide multiple buttons, add the values together and type the sum. For example, to hide the Open and Save As buttons, type HideDialogButtons=10.