Creating Custom Patches through Packing List Utility

Creating Custom Patches through Packing List Utility

The information contained in this document is current as of the date of publication and subject to change. Because Tally must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Tally, and Tally cannot guarantee the accuracy of any information presented after the date of publication. The information provided herein is general, not according to individual circumstances, and is not intended to substitute for informed professional advice. This document is for informational purposes only. TALLY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT AND SHALL NOT BE LIABLE FOR LOSS OR DAMAGE OF WHATEVER NATURE, ARISING OUT OF, OR IN CONNECTION WITH THE USE OF OR INABILITY TO USE THE CONTENT OF THIS PUBLICATION, AND/OR ANY CONDUCT UNDERTAKEN BY PLACING RELIANCE ON THE CONTENTS OF THIS PUBLICATION. Complying with all applicable copyright and other intellectual property laws is the responsibility of the user. All rights including copyrights, rights of translation, etc., are vested exclusively with TALLY SOLUTIONS PRIVATE LIMITED. No part of this document may be reproduced, translated, revised, stored in, or introduced into a retrieval system, or transmitted in any form, by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Tally Solutions Pvt. Ltd. Tally may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written licence agreement from Tally, the furnishing of this document does not give you any licence to these patents, trademarks, copyrights, or other intellectual property. 2009 Tally Solutions Pvt. Ltd. All rights reserved. Tally, Tally 9, Tally9, Tally.ERP, Tally.ERP 9, Shoper, Shoper 9, Shoper POS, Shoper HO, Shoper 9 POS, Shoper 9 HO, TallyDeveloper, Tally Developer, Tally.Developer 9, Tally.NET, Tally Development Environment, Tally Extender, Tally Integrator, Tally Integrated Network, Tally Service Partner, TallyAcademy & Power of Simplicity are either registered trademarks or trademarks of Tally Solutions Pvt. Ltd. in India and/or other countries. All other trademarks are properties of their respective owners. Version:Creating Custom Patches through Packing List Utility/1.1/August 2009

Contents Creating Custom Patches through Packing List Utility Introduction... 1 Custom Patches... 1 Packing List Activity... 2 i

Creating Custom Patches through Packing List Utility Introduction Customised.exe files, custom updates and other customisations specific to a customer can be deployed at the customers HO and POS locations through customised live updates. Custom live update can be run along with the standard Shoper live update. Patches for custom live update can be created using the packing list utility. New Live update carries the packing list as part of the patch file. This file contains the information about the files which are getting patched in the destination folder. The packing list file will have the complete information about the file name, destination folder, root folder, and the flag to hold that the registration required or not for the corresponding folder. This file will be used in the Live Update to patch the files in the respective folder. The new exe has been created to achieve this activity. This is an independent exe which will run without any dependency. This is a plug and play.exe file, which you have to copy and paste on to the user desktop and start using. Custom Patches The custom patch contains two major files. i.e, 1. Custom patches zip file (has to be created using the packing list utility) 2. Patchinfo.dat file containing the information about the patch Custom Patches Zip file The nomenclature of this file is based on the customer for whom the custom patch is being created. For example, if you are creating a custom patch for company ABC, you can name the custom patch as ABC_001.Zip for the first patch and then on an incremental basis as, 002, 003, etc. for the subsequent patches. Patchinfo.dat file Patchinfo.dat file should be located in the output folder which will hold the patch information entries. This file will get amended every time with a new entry once the patch zip file gets created using the packing list utility. 1

Creating Custom Patches Packing List Activity To deploy and use the Packing List Activity: 1. Double Click on Packing list utility exe The default window is displayed as shown. Figure 1. Packing List Utility window 2. Provide the folder path where all the patch files to be zipped are available. 3. Click on the Get Files button to show the files in the list view. 2

Creating Custom Patches The files are displayed as shown. Figure 2. Packing List Utility window - with files 4. From the tree view folder structure, select the destination folder where the files need to be saved. By default, focus will be on the Application folder. (Refer Fig.2). 5. Double click on the files in the list view which need to be saved in the selected destination folder. 3

Creating Custom Patches The Destination Computer s Files list will show the list of items added as shown. Figure 3. Destination Computer s Files list 6. By default the Registration Required flag will be set to NO. You can change it to YES, if registration is required for the added file. 7. Add all the files that have to be zipped. 8. Enter the patch name in the Patch Zip File Name field. 9. Enter the output path in the OutPut Folder Path field. 4

Creating Custom Patches The completed Packing list utility window is displayed as shown. Figure 4. Completed Packing list utility window 10. Click Generate Patch. The Packing list ini file is created; added along with the selected patch files and the patch zip file is created. The created patch zip file will have the name mentioned in the Patch Zip File Name field and saved in the path mentioned in the OutPut Folder Path field. 11. Finally, the output folder will have the Patch zip file and the PatchInfo.Dat file. Note: If there are any scripts which need to be shipped, it should be kept in the folder (whose contents are to be patched) along with the exes and other files. Scripts should be kept with the sub folder name Script. These files will not be shown in the list view when you click Get Files. Internally this will be handled and included in the patch zip file. 5