QT-registrations version 2.4 introduces a new type of ticket: the Inspection.

Inspections is a customisable question form, with predefined choises. Like other type of tickets, the Inspection includes a title and a question message but also includes some parameters that the staff can configure: level of reply scores (Yes/No, 3 levels, 5 levels or percentage score) and an aggregation method (to compute total score of several replies).

The reply form includes a multiple choise list and a message (and other ticket fields if required).

An Inspection ticket can be used as recurrent inspection form and, thus, gathers several reply scores. The ticket itself will show a "total" score. This total can be computed using several methods, depending on the inspection purpose. The score of an Inspection can be the MEAN value of all replies, but also the maximum or the minimum values. Often, for recurrent inspections, when the goal is the control the evolution of an asset, the manager prefers to report on the LAST inspection score. Sometime, safety rules impose to perform an inspection every (e.g.) first day of the month and the result the safety inspection must show this result. In this case, we can schedule our inspections (and more inspection during the month), but the score will be the FIRST result as imposed by the safety rule.

In a section, the Inspections will be visible in the ticket list with a specific icon and the Replies column will show the "total" score. Each inspection ticket within a section can have different response levels as well as different aggregation methods.

By opening the Inspection detail, you will see all the replies individual score with date and message.

Tips: The reply form always includes a choise "Unknown": this choise allows adding reply message to an Inspection without score. These null scores are not taken into account for the "total" score, but are counted in the number of replies.

The application time is used as ticket and message issue time. The clock, visible at the bottom of the pages, can show an other time like a reference time specific to your organisation (e.g. the GMT time). If your webhost supports PHP 5.2 or next, you can now change also the application time.

In the page Regional Settings, you will see a link to change de application time. By default the applications time is your web server time. Since PHP 5.2, it's possible to change de application time by defining the time zone you want to use as your application time. If you don't see this link, that's because your current webserver runs a PHP version prior to 5.2 and in this case, changing application time requires to change the webserver configuration.

To change the application time you just have to specify a time zone identifier. To find the correct time zone, you can search per zone. Copy the identifier from to list, then click the save button. Note that the list of zones and identifiers may be different from one php version to an other.

When using the map module, in the list of tickets (or list of members) a small marker icon indicates which record has coordinates. This marker will show the coordinates and is clickable. By clicking this icon the map centres on this ticket (or user) location.

When using the map module, the coordinates are now displayed in both formats (degree minutes second and decimal degrees).

The coordinates are visible in the lists, in the detail of a ticket or a profile and by clicking on the map marker.

The coordinates also include a link that will open Google map and show this location.

When using the map module, in the edit forms like the new ticket form or the edit profile, in addition to clicking the map, we can now also input the coordinates in both formats (degrees minutes seconds or decimal degrees).

Inside a section, the number of tickets displayed is included in the information panel, as well as hidden tickets (when the section is setup to hide closed tickets).

The database now includes a timestamp associated to the status. User can view when the status was changed by moving the cursor on the status name. This status date is also visible when printing.

The stylesheets have been improved. For a better usability, stylesheet can include row highlight on mouse movement or defining alternate background colors per row.

When looking the ticket detail information, users can quickly find other tickets having similar categories.

Category input has been improved. This version offers a better support when working with hierarchical categories (or coded categories). This version also fixes a minor bug when using Opera brower.