In the Hudson system, a Token is a value that can be inserted into various document templates and is then automatically poplulated with the correct value from a reservation or trip, when the document is generated. An example of a commonly used Token would be Pickup Time. In the Reservations database, this value is stored as PickupTOD. A Token exists %PICKUPTOD% which can be inserted into a confirmation screen, email confirmation template, driver trip sheet, etc. which results in the reservation PickupTOD value being inserted in the proper place in each of these documents.

For example, in the client readback screen that appears on the Agent's screen, when saving a reservation, you may see the following:

Thank you for calling. We will pickup %FNAME% %LNAME% on %PICKUPDATE% at %PICKUPTOD%. We will arrive at %PICKUPADDR%, %PICKUPCITY% %PICKUPSTATE% in a %SERVICETYPE% and will deliver you to %DROPOFFLOCATION%......

(I think you probably get the idea and see how useful Tokens can be....)

There already exists an extensive list of Tokens that can be used "off the shelf." Click Here for a listing of these tokens.

Beginning with Reservation Database Level 108, you can use the new Token Engine to build and create your own Tokens.

These Tokens can be simple Text Statements (such as a cancellation policy) that you wish to customize and insert in various templates. They can also be most any value that is extracted from one of the tables in your database and then inserted into documents and templates that you create.

To create a Token consisting of a Text String:

Click Tools - Configuration - Tokens
Click File - Add New Token (or F1)
In the Token Field - enter the name of your Token (ex: CANCELPOLICY) (max of 32 characters)
In the String Field - enter the text to be displayed (ex: All reservations must be cancelled 24 hours or more prior to pickup time to avoid a 50% cancellation fee.) (max of 255 characters)
Click Update
Click Save Changes to DB.

You can now open any of the templates where you wish the Cancelation policy to appear, and can insert: %CANCELPOLICY% . When the document is generated, the text string you saved will be inserted.

For more complex and powerful Token creation....read on:

(This example creates a Token that lists the Preferred Driver # and Name that is selected during the Reservation entry process)

Following the steps outlined above:

1. Add a token Q1 with string value @@SELECT PrefDriver FROM Reservations WHERE ID=%ID%
2. Add a token Q2 with string value @@SELECT DriverName FROM Drivers WHERE ID=%Q1_V1%
3. In your template, add these tokens:

When the template is processed:
%Q1% & %Q2% will disappear and %Q1_V1% will = PrefDriver field from Reservations table
%Q2_V1% will = DriverName field from Drivers table

%Q1_V1% corresponds to the first column requested in your SQL Select query of Q1
%Q1_V2% is the second value.