Navigation

 ·   Wiki Home
 ·   Wiki Help
 ·   Categories
 ·   Title List
 ·   Uncategorized Pages
 ·   Random Page
 ·   Recent Changes
 ·   RSS
 ·   Atom
 ·   What Links Here

Active Members:

Search:

 

Create or Find Page:

 

View Updating Configuring and Viewing Records in the Reservation Audits Table

Category:HWeb Dispatcher

Updating Configuring and Viewing Records in the Reservation Audits Table


Prior to software version 1.90, any changes that were made to a reservation, were stored within the reservation record itself. While effective, this process was not very efficient in that it could result in a potentially large record if multiple changes were made. The result being that the record would be slower to load for viewing or editing.
 
In Hudson HWeb version 1.90 historical changes made to a reservation record were moved from the Reservation Table in SQL to a new table named Reservation Audits.  In addition to helping keep the Reservation record size to a minimum, it also provides the ability now to sort and report based on reservation edit types. For example, you would now be able to create a report (custom grid) showing how many reservations had their PickupTOD’s modified for a particular date range or create a report showing when a group of reservations were Marked Paid.

This modification does not change how a user will view the changes applied to a reservation. The record may still be opened in HWeb Agent and then see all changes for that record by selecting the History tab.  When the History tab of a reservation is selected, the data for that record is retrieved instantly from the Reservation Audits table in the database.


Updating Existing Records and setting the configuration to use Res Audit

There are a few steps to this process.

1.  You want to make sure that everyone using Hudson is updated to version 1.90 or higher.

2.  Open the ReservationsAudit table in the SQL Manager and make sure the fields ResID and RecordUpdatedTOD are Indexed.

3.  Open the Admin and update the current reservations table so that all of the reservations that exist are updated to run this way.  Database Utilities>Update Records>Current Res Audit.

4.  Change the configuration settings so that any new reservations also use the audits tabel.Tools>Configuration>ApplicationConfiguration>Fare and Servcies>Hudson>Security.  Check the Use Res Audits box.

5.  Have everyone press F11.

6.  Run the Update Records again on the Admin (Database Utilities>Update Records>Current Res Audit)  This is so you update any records that may have been added or changed during the configuration changes you have been making.

7.  Have everyone press F11 again.

8.  Run step 6 but do it for the archived reservations table.



Building a Grid
Previous knowledge on how to build a custom grid in the HWeb Dispatcher system will prove extremely useful (read: necessary) before proceeding with the following instructions. For more information on how to build custom grids in HWeb Dispatcher, please look at the following article, which includes downloadable audio files that will coach you through the process of learning to build custom grids:
  http://kb.hudsonltd.com/article.php?id=258


Open HWeb Dispatcher
Click  File > New
Select Reservation Audits View

From here you may go into Grid Layout and determine the field(s) you wish to display:
  • ID - Each reservation change will be issued a unique identification number
  • ResID - This is the reservation number (local system) where the change was made
  • Event - The field that was modified (ex: PickupTOD, ServiceType, PickupAddress, etc.)
  • OldValue - The value displayed in the Event above, before the change was made
  • NewValue - The value displayed in the Event above, after the change was made and saved.
  • UpdateFlags -
  • UpdatedBy - User name of the person who made the change.
  • UpdatedTOD - Time Of Day that the new value was saved.
  • CUST1…CUST9 - The CUST fields are customizable data fields, accessed via Grid Properties, which may be configured with filters and formatting strings to display information from other tables in the database, via use of table Inner Joins.  This is advanced functionality and you are invited to contact Hudson Tech Support for additional assistance with this feature.






 

 

Categories: