Repackaging the master template is the process that assembles all the decisions made for template defaults and customized content into a package that can be easily distributed to all end users. The repackage process creates a .cwp file, which is the same format as the original installation file. The repackage function is CaseWare International’s version of zipping files.
While template authors are working in the template file, the changes are affecting multiple background files. The repackage process ensures that all of these unseen files are assembled for distribution. You cannot simply copy selected files and place them on the network for end users to access, or place them on individual computers.
After executing the repackage function, the file is placed in the default CaseWare template directory and is prepended with the word copy. For example, if you are working with the Financials IFRS template, the file will be named Copy of FinancialsIFRS.cwp and will be located in the following directory: C:\Program Files (x86)\CaseWare\Template. Template authors can rename this file and then distribute this file to all end users. It is a best practice to put the date of repackage and the template version in the file name. For example, if the current shipping version is v10.30 and the repackage is created today, the revised file name would be FinancialsIFRS v10.30 04-10-13.cwp. This is the file that would be distributed for all users to install.
Each time template authors receive updates from CaseWare International, or make changes that need to be replicated by users, the repackage process must be performed. Including the repackage date in the file name helps with keeping track of versions.
There are two methods to repackage the template:
- Repackaging using the CQ - Organization settings document will lock the libraries and firm defaults. This is the method to use when redistributing to all users.
- The second method is to select Templates from the Tools menu in Working Papers, and then click Repackage. This is the recommended way to create a backup of the master or to transfer the master to another template author. This method does not lock the libraries and firm defaults.