Patching Template Files

Displays the file path where the packaged template will be located. Click Browse to choose a different location and specify a File name.

Click to select the template you want to patch.

Specifies a version number for the package. Enter version numbers and a version tag to keep track of different versions.

The version number is added to the registry during the installation of the template. The version information is used to determine which version to overwrite when you are patching a template.

The minimum version number the template can have and still have files overwritten by the patch. A patch with a Min Version of 2.0.0 would overrite a template with version number 2.5.0, but not 1.0.0.

The maximum version number the template can have and still have files overwritten by the patch. A patch with a Max Version of 2.0.0 would overrite a template with version number 1.5.0, but not 3.0.0.

If checked, the template will only be applied to a template which has a matching version tag. For example, a patch with the version tag Rev A could only be applied to a template with a version tag Rev A.

If unchecked, the patch will apply its version tag to the template. For example, if a patch with a version tag of Rev A were applied to a template without a version tag, the patched template would then have the version tag Rev A.

Note: Revision tags are case sensitive.

Select to allow the template to be repackaged.

Note: Preventing templates from being repackaged on a machine where the template is already installed is a known security measure.

Select to limit the template to be used with a minimum version of CaseWare Working Papers.

If this check box is selected, use the drop-down list to select a version and enter a build number in the Build field to specify the minimum version of Working Papers and build number for this template to be used in.

Include an End User License Agreement (EULA) that the user must accept before the installation can proceed.

You can enter the file name, use the drop-down list, or click Browse to select an *.rtf or *.txt file.

Include text to be displayed on the first page of the installation wizard.

You can enter the file name, use the drop-down list, or click Browse to select an *.rtf or *.txt file.

Include a custom image to show on the left side of the first page of the installation wizard.

You can enter the file name, use the drop-down, or click Browse to select a *.bmp file. For optimum resolution, the size of the watermark graphic must be 165x450 pixels.

Include a custom image in the header of the installation wizard.

You can enter the file path, use the drop-down list, or click Browse to select an *.rtf or *.txt file.

Include a custom icon to represent a template in the Templates dialog.

You can enter a file path, use the drop-down list, or click Browse to select a *.bmp or *.ico file. A preview is shown in the Icon box.

A preview of the header to be included is shown. Click the image to choose a new one.

A preview of the icon to be included is shown. Click the image to choose a new one.

Click to build the template package without continuing through the wizard.

Click this button to select another file path where layouts are located.

Select the check box beside each layout you want to include in the template package.

Note: If the selected layout requires dependent layouts, those layouts are automatically included, even if you haven't selected them. The next time you package template files, the layouts previously selected and their dependent layouts are automatically selected and are always included in the package.

Select an option to overwrite existing layouts.

• Merge folder contents

  Combines the selected layouts and overwrites any existing version of the layouts when the template is installed on the user's machine.

• Skip if folder exists

  Skips overwriting any layouts if they already exist on the user's machine.

• Delete existing folder and then replace

  Deletes existing layout folder and copies layouts from the template package.

Click to build the template package without continuing through the wizard.

Click to include folders. Including a folder will include all of the files within the folder.

Select this option to provide the user the option to install knowledge library files in a location other than the program folder.

Note: This option only appears when Knowledge Libraries is selected.

Click to build the template package without continuing through the wizard.

Select this option to add a desktop shortcut for the file.

Note: This option only appears when an individual file added with Add Files is selected.

This column specifies the files to be included.

The files selected for each category will be installed to the following locations:

Select an option to determine how existing files will be overwritten:

• Always Overwrite: Overwrites the selected files.
• Do Not Overwrite: Skip overwriting if the file exists.
• Overwrite if Newer Date: Replace existing file if the file in Packager is more recent.
• Overwrite if Newer Version: Replace existing file if the file in the package is a more recent version.
• Overwrite if Newer Version and then Newer Date: Replace existing file if the file in the package by checking the version number and then checking the date.
• Prompt User: If the destination already contains a file or folder being installed then the user is prompted to select an action.

Note: This option only appears when an individual file is selected, or when a folder is selected and Merge folder contentsis selected from the Folder Merge Actions drop down menu.

Select an option to determine merge behavior for existing folders:

• Merge folder contents: Folder contents are merged, and files are overwritten according to File Overwrite Actions
• Skip if Folder Exists: Skips merging any folders if they already exist on the user's machine.
• Delete Existing Folder and Replace: Deletes existing folders and copies files from the template package.
• Prompt User to Overwrite Files: If the patch destination already contains a file in the selected folder the user is prompted to select an action.

Select this option if you want to deliver *.exe or *.dll files to be used by scripting.

Note: This option only appears when an .exe or .dll file added with Add Files is selected.

Click to remove a single file or all files.

This column specifies the file path of the files to be included.

• Execute before installation: Applications added here will be executed before the template is installed.
• Execture after installation: Applications added here will be executed after the template is installed.
• Execute before uninstillation: Applications added here will be executed before the template is uninstalled.
• Execute after unistillation: Applications added here will be executed after the template is uninstalled.

This field specifies a unique label assigned to each application.

This field specifies the file path of the application.

This field specifies the name of the application.

This field specifies additional parameters that are needed to run the executable. The additional parameters are passed to the Template Installer which will run the executable and append the command line parameter.

Select this option to include all supporting files needed for installing the application.

Note: Use this check box with caution; if, for example, you put the executable on your C: drive and select this check box, then all files on your C: drive are included in the template package.

Choose this option to prevent the selected executable from running in unattended mode.

See Advanced Options Dialog for more information.