Create Template Package Wizard

This field displays the file path where the packaged template will be located. CaseWare only supports the existence of one .ac or .ac_ file in this folder. Client files residing in subfolders of the top-level folder are not supported. Click Browse to choose a different location and specify a File name.

• If selecting a template

  Click Browse to select the template you want to package. If a template was selected in the Templates dialog, that selection is automatically input as the client file.

• If creating a shared files package

  Use the drop-down list and select None (Create Shared Files Package). A Shared Files Package will be created. These packages consist of files that target multiple templates and cannot be uninstalled.

  Note: When creating a Shared Files Package, all other options within this page are disabled except Enforce a minimum CaseWare version of:.

This field specifies a template name to identify the template that will be installed from this package.

The name entered here appears in the Templates dialog.

This field specifies a version number for the package. Enter version numbers in the boxes 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.

This field specifies a unique tag provided to the package. You might want to have different builds of the same version (for example a US build and a Canadian build).

The version tag 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.

Use the drop-down menu or click Browse to select a registry file.

Select a registry file if there are elements in the template that require modification of the registry.

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 specify additional controls if Allow this Template to be Repackaged is selected.

When this check box is selected and a template is being repackaged, only the Global Options page is displayed in the wizard. Within the Global Options page only the Output File and Template Name fields can be changed.

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.

Select to install the repackaged template in the document library.

Select to install the template without registering it. No registry key will be added for the template and it will not be displayed in the list of templates that new client files can be based on.

Note: This option is only available if Install Template in Document Library is selected.

If selected, the Make Patch button displays when a user selects this template from Tools | Templates.

Select to allow the template to be opened after installation.

In the last page of the installation wizard, a check box (Open the Template for editing) is shown. If this check box is selected the template will be opened in template mode once packager is closed.

Select to perform a verification of the files when they are compressed into the package.

Click to open the More Options dialog. The dialog provides two dropdown option lists:

• Options for backing up the existing template.

• Options for uninstalling the existing template.

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.

A preview of the watermark is shown in the watermark box. The default image is the Template Packager image shown below.

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. The default image is the CaseWare icon shown below.

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

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.

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

Select an option to overwrite existing layouts.

• Merge and Overwrite

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

• Skip if Exist

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

• Replace Existing Folder

  Deletes existing layout folder and copies layouts from 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.

This column specifies the files to be included.

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

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

Click this button to remove a single file or all files.

Click this button to include individual files.

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

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

Create shortcut on desktop

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

Allow user to specify Knowledge library extract path

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

Register this COM file during installation

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

Select an option to overwrite existing files.

• Merge and Overwrite

  Combines the selected files and overwrites any existing version of the files when the template is installed on the user's machine. When Merge and Overwrite is set on folders, you can specify the following overwrite options for each file inside the folder.

  • 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 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.

• Skip if Exist

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

• Replace Existing Folder

  Deletes existing folders and copies the files from the template package.

Applications added here will be executed before the template is installed.

Applications added here will be executed after the template is installed.

This field specifies a unique label assigned to each application. The label specified here is reflected in the Label column in the screenshot below.

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.

The following case-sensitive macros can be specified. When the package is subsequently installed, the macros are expanded to the corresponding paths specified by the user on the summary page and passed as parameters to the installer being run.

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

Important: 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.

Click to launch the Advanced Options dialog.