============================================================================ This file contains the list of correctives made to NewWayService 4 OroLogic Inc., February 5, 2010 ============================================================================ ============================================================================ ************************ Version 4.07 (February 5, 2010) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed problems of type "Access violation" that could happen randomly. Fixed display problems and other minor problems. Improvements: ============= Improved performances in the web interface. ============================================================================ ************************ Version 4.06 (November 16, 2009) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed problems of type "Access violation" that could happen randomly. Fixed a problem in the option "Recursive work orders". The field " days in advance" was not taken into account. Fixed a problem when sending work orders by e-mail when the box "Use a secured connection. (SSL)" was checked. Fixed a problem in the option "E-mail formats". Fixed display problems and other minor problems. Improvements: ============= It is now possible to delete a spare part even if there is transactions inventory linked to it. ============================================================================ ************************ Version 4.05 (September 10, 2009) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed a problem when saving data in the tab "Follow-up/Log" of a work order. For example, an error occured when the technician name was too long. Fixed display problems and other minor problems. Improvements: ============= It is now possible to select a predefined task from recustive work orders. It is now possible to have reminders 30 days in advance. On screen, it is now possible to sort data on the field "Internal notes" of a work oder. ============================================================================ ************************ Version 4.04 (August 17, 2009) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed a problem when sending work orders by e-mail. When e-mails were sent by the Windows service of NewWayService, the username and password were not correctly sent to the SMTP server. Most of the time, the resulting error was "Unable to relay". Fixed a problem in the web interface. The direct link http://servername:port/?section=addwo did not work all the time. Fixed display problems and other minor problems. ============================================================================ ************************ Version 4.03 (August 7, 2009) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed a display problem: When more than 5000 items was displayed on screen (such as 5000 customers) an "Access violation" error was displayed on screen. Fixed a problem when sending work orders by e-mail. In some cases, only one or two recipients was taken into account. Fixed access rights problems in the Windows version and the web interface. Fixed other display problems and other minor problems. ============================================================================ ************************ Version 4.02 (August 3, 2009) ============================================================================ Database structure: ================== Not modified (See note at the end of this document) Correctives: ============ Fixed a problem with e-mail formats. Information in sections "Service" and "Parts" were not displayed on the e-mail. Fixed some display problems. Fixed other minor problems. ============================================================================ ************************ Version 4.01 (July 9, 2009) ============================================================================ New major version. ============================================================================ End of the list of correctives ============================================================================ ============================================================================ ************************ Notes ============================================================================ Database structure "Modified": ============================== Indicates that this update must update the database structure. When the first user access the database using the new updated version, a confirmation message is displayed to modify the database structure. If the user answer "Yes" to the confirmation message, the database is automatically modified. Please note that if the security into the database is activated, the user will have to enter the Administrator password to be able to update the database structure. Once the database structure is modified, users of earlier versions will not be able to access the database anymore. You will have to install the new update on each computer and/or server so that all users can access the database again. When an update must modify the database structure, it is recommended to plan the deployment of the new update on each computer and/or servers. Database structure "Not Modified": =============================================== Indicates that this update does not have to modify the database structure. So, it is not necessary (although recommended) to install the new update on all computers and/or servers. Users of earlier versions will be able to continue to access the database. ============================================================================