Warning: the procedure is different for the systems that use only the standard configurations, and for those who use customized and/or translated configurations!
You can upgrade GN4 configuration files, stored on a local drive of a System Administrator's workstation, and then, in the next step, upgrade your GN4 database with new configuration files. Unlike GN4 applications, that have version and build number, GN4 configuration haven't one, so you have to rely on the file date/size to identify the latest configurations, and - optionally - on an text editor with compare capabilities to locate changes.
The standard GN4 configuration files (about 294 files) are spread across about 20 sub-folders. The structure is clearly visible in GN4CONFIG.ZIP. For an easier support, it is recommended to keep the same structure on your local drive.
GN4 developers modify configuration files each now and then, adding or changing features and fixing bugs. What changes frequently are the files under GLOBAL > EDITORIAL.
Locating configuration files updated since your last upgrade
This requires that you know the date of your last upgrade!
Unzip the GN4CONFIG.ZIP in a folder of your choice (recommended: C:\TERA\GN4\CONFIG\) and then use Windows Explorer to search for all files. Sort the results by date. Check which files are updated since your last upgrade.
Updating your system configuration
There are two cases:
In that case, simply load all updated configuration files as explained in Importing configuration files in database (quick chart). Important: by loading updated files you accept all changes that may be applied on the updated configurations. Your menus, dialog boxes and keyboard shortcuts can change! |
For the configuration files you didn't customize, use the same procedure as explained in "Your GN4 system uses the standard configuration". For the customized configuration files, instead of replacing, that would cause a loss of all your customizations/translations, you need to compare your customized files with the latest standard ones, locate the changes and copy/paste the changes from the standard configurations in your customized configurations. Note: mostly, you will customize xxx_TABITEMS.XML and xxx_CONFIG.XML files, but candidates are also workflow files, XSL stylesheets and similar. When done, load updated customized configuration files as explained in Importing configuration files in database (quick chart). |