Updates (Module Exchange)

In ClassiX, updates are called diff. Diffs are regularly generated by ClassiX and include all changes (module extensions, DLL extensions and error corrections) after the last diff. Diffs are created individually for the customers. Therefore the exchange cycle can be different from customer to customer.

1. Diff provision

The diff is a zip file, which is transferred to the customer via e-mail or via file transfer. If the diff contains new DLLs, e-mail distribution is not possible due to the diff size. The zip file name contains diff- and DLL version. (CUSTOMER-4.4.111.zip  accords to the DLL version 4.4 and the diff version number 111)

2. Diff analysis

The diff contains a file called changes.html. This file describes all changes that have been made after the last diff. Based on this file, all affected user's areas can be informed about the changes and it is possible to execute personal tests in reference to the changes.

3. Diff testing

A diff that has been exported by ClassiX, already had to undergo quality assurance. Nevertheless, before transferring the diff into the real system, it should be imported into a test system. Depending on the support model, the customer has to control, whether the default changes harmonize with the customized adjustments or not. Furthermore, it is advisable to get a general idea of the changes in the test system and to use the test system for training purposes, before the diff is directly adopted by the real system.

Remark: A separate test system has its own test database, as well as its own module- and DLL directories etc..

4. Importing the diff

Importing the diff into the real system is no different to the import into the test system. Please proceed as follows:

1. It is only possible to import a new diff, if all previous diffs have been imported before. Therefore it needs to be considered that the current AppsWH version is the direct precursor of the current diff version.
    
2. The zip file has to be extracted into a separate directory. Generally, this directory is called "labes", it is located  below the Classix directory and therefore on the same level as the real system root directory (ROOTDIR). ( ./ClassiX/Label)
    
3. The diff has to be analyzed with the changes.html file. Please get a general idea of what steps need to be considered before starting the import. If the diff includes workflows (*.wfl), transaction descriptions (*.txn) or reports (*.rpt), they must be imported with the according modules, right after the diff import. Reorgs have to be executed as described in the file changes.html.
   
   Characteristic DLL exchange:
   DLLs can be exchanged only after all ClassiX sessions have been closed. To guarantee that this is the case, it is recommended to shut down the database for the module exchange. (A DLL exchange while running other operations is also possible, but it should only be executed after consultation with the ClassiX Support.)
    
4. The folders have to be copied from the extracted directory into the ROOTDIR (./ClassiX/"Clientname") and the tasks from step 3 have to be executed.
    
5. The module modifications are available after restart. Starting ClassiX for the first time, please check, if the new DLL and AppsWH version are displayed correctly.
    
6. If the diff has been imported while running other operations, all users have to restart ClassiX once to continue working with equal module conditions.