User-Defined Booking Screen Properties
Booking Screen properties control the appearance and functionality of Trip Booking.
Open Trip Booking () to see Booking Screen properties.
| Property | Description |
|---|---|
| ACT for ReqDO | (Activate Requested Drop-Off) Specifies whether to
activate drop-off logic that calculates the pick-up time if a drop-off time is typed
into the Destination request field.
|
| ACT Groups for ReqDO | Specifies whether to apply requested drop-off logic to group trips. |
| Advanced Booking Days | Number of days in advance of the current day that reservations are accepted. The maximum value is 365. |
| Allow Multiple Legs | Specifies whether to allow multiple segments to be added to the trip (for example, when a client books a trip to travel from points A to B, points B to C, and points C to A). |
| Auto Search FX Itineraries | Specifies whether to automatically search for new FX itineraries. |
| Booking Save Timeout (sec.) | Number of seconds the system has to save a booking. Once this value is reached, a message is sent to the workstation indicating that the server failed to save the booking. |
| Change ReqTime on Scheduled | Specifies whether users can change a requested time once a trip has been scheduled. If set to No, the trip must be unscheduled before users can edit the time. |
| Check ADA | Specifies whether the Schedule Server should verify the ADA checks for the
client and requested trip when a booking is saved. After saving a booking, the
ADACheck PU (pick-up) and ADACheck DO (drop-off) fields in the Trip Administration
screen are populated with the status of the booking according to these checks.
For all trips, the system verifies that the origin and destination fall within an ADA polygon and that the booking time falls within ADA restrictions. Trips booked with requested pick-up times have additional
checks:
Trips booked with requested drop-off times have additional checks:
|
| Check Client Not Identified | Specifies whether trip bookings can be saved without a client selected. |
| Check double bookings | Specifies whether the system should check for any other trip that has been booked for the client for that same date when users type a date and name for a new booking. The system shows any bookings found in the Client/Booking Info dialog box. This feature is used to prevent double bookings. |
| Check Funding Source | Specifies whether the system, when a client has funding sources, should check funding source allowances and restrictions upon saving a booking. |
| Check Location Times | Specifies whether the system should check for existing pick-up or drop-off
times for a location during trip booking. The user can then choose an existing time
and reduce the number of trips to a common location. When a location with a time rule is selected as the drop-off or pick-up location, the Match Location Times dialog box appears whether or not the location is a Client, Location, or Frequent location type. The system can also search for trips to or from the location within the time period specified by the property. |
| Check Locations | Specifies whether a location is open during business hours to allow a client to be picked up or dropped off there. |
| Check Para service area | Specifies whether paraservice area rules should be applied to all bookings. |
| Check Prior Booking | Specifies whether to show warning message to users when they try to create a booking for a date or time prior to the current date or time. |
| Check Purpose match Source | Specifies whether the system should look for any funding source assigned to the purpose of the client’s trip. If a match is found, the fare charged to the client, which is subsidized by the funding source, can be applied if you have set up Funding Allowances. |
| Check service area | Specifies whether the system should verify that a trip’s pick-up and drop-off fall within the service area boundaries. |
| Clear Address Box | Specifies whether to show a message box to allow users to clear the address box when they attempt to edit (by overwriting or by making a selection with the Street Wizard) a field in the Origin or Destination address box of a saved booking. In the error message, clicking Yes causes all information in the address box to disappear; clicking No leaves the address information intact, although some fields can still be overwritten. When Clear Address Box is set to No, fields can be overwritten one at a time. |
| Client Type Required | Specifies whether users should be prompted to select a valid client type code in the Trip Booking screen to be able to save a booking. |
| Confirm Date On Save | Specifies whether to show a message to confirm the date(s) for which a booking is saved. |
| Default all client funding sources | Specifies whether to enable the client’s funding sources in the specified sequence to be automatically typed in the Funding Source fields in the Trip Booking screen. If set to No, only the first funding source is shown in the first Funding Source field. |
| Default batch parameter set | Default parameter set used in batch scheduling. |
| Default batch violation set | Default violation set used in batch scheduling. |
| Default Calendar Days | Number of days that the calendar shows when it is opened in the Trip Booking screen. |
| Default City | City name to automatically appear in the City field when creating a new booking by default. This default city can be overwritten manually. It is also overwritten by any city associated with a given client if that city is different from this default. |
| Default Date | Specifies whether to automatically insert the current date or the offset date into the Date field when creating a booking. Select No. |
| Default Date Offset | Specifies the date based on the default, plus the number of days typed in the Date field (for example, 0 = same day, 1 = tomorrow). |
| Default Location Type | Location type (for example, Other, Client, Location, Stop, Frequent) shown by default in the Origin and Destination frames of the Trip Booking screen. This property applies to both the classic Trip Booking and Quick Booking screens. |
| Default parameter set | Default parameter set when performing single insert scheduling in the Schedule Booking Wizard. |
| Default Request Offset | Request time forward from the current computer time. For example, if the current time of booking is 11:46 and the offset is 60, the system sets the request time for the booking 60 minutes ahead to 12:46. |
| Default Request Time | Specifies whether to activate the Default Request Offset property. |
| Default Service Type | Service type to be set as the default for all bookings (curb to curb, door to door, bed to bed). |
| Default to Casuals | Specifies whether to designate every booking as a casual booking when the Trip Booking screen is first opened. If set to No, the system automatically chooses a new booking as a subscription by default. |
| Default Trip Booking Screen | Specifies the type of Trip Booking screen that is shown by default:
To toggle between the Classic and New screens, press CTRL+SHIFT. |
| Default violation set | Default violation set when performing single insert scheduling in the Schedule Booking Wizard. |
| Enable booking wizard | Specifies whether to use an alternative method to guide users through the booking process. This property is used in Europe only. |
| Enable Service Line Guide | For use in Europe only. |
| Enforce PassType | Specifies whether to prevent users from saving bookings that have no default passenger type. The default is No. |
| F6 Clears Date | Specifies what happens when F6 is pressed on the Trip Booking screen:
|
| Faretype Required | Specifies whether to show a message when saving a booking with no selected fare type. |
| Funding Source Required | Specifies whether to show a message when saving a booking without a selected funding source. The text of the message depends on the permission key setting in Trapeze6. |
| Order locations by distance | Specifies whether users can matches for suggested locations when typing the name of a location to be sorted by distance from the trip’s origin instead of in alphabetical order. |
| Over Ride Funding Sources | Specifies whether users can select any funding source saved in the database in
the funding source lists. If set to No, the lists in the
funding source fields list only the funding sources assigned to the client in Client
Registration. Assigned funding sources are marked by an asterisk (*). Note: The first
funding source field in the Trip Booking screen automatically shows any funding
sources assigned for the client by default. |
| Paraservice type required | Specifies whether to prevent bookings from being saved unless a paraservice type is assigned to them. |
| Pending client eligibility expiration | Specifies whether users can select the number of days from the current date within which the system shows an alert that a client’s eligibility period is due to expire. If a trip booking is created within the selected number of days, the system shows a warning message. If a value is not defined, the default is 0, and the system will not show a warning message. You can also type a negative number, which prompts the system to provide a warning when the eligibility renewal date is overdue. |
| Provider Required | Specifies whether to prevent bookings from being saved unless a provider is selected. |
| Remove ineligible Funding Sources | Specifies whether to hide funding sources in the list that clients are ineligible for. |
| Show Fare Summary on Save | Specifies whether to show the Fare Summary dialog box when users save a booking. This dialog box shows the total fare for the trip, the amount the client must pay, the amount paid by the funding sources, and the amount deducted from the client account for prepaid fares. |
| Trip Plan Analyzer | Specifies whether to automatically load a saved booking into the Trip Plan Analyzer screen. |
| Trip Purpose Required | Specifies whether to prevent bookings from being saved unless a trip purpose is
specified. In this case, a message prompts the user to choose from the following options:
|
| TripAdmin- Show Row Count | Specifies whether to show the row count at the bottom of the Trip Administration screen. |
| Update Master Geocode | Specifies whether to activate the Update Master Address feature. When the user re-geocodes a client address (for example, CH) in the Trip Booking screen, the system can overwrite the address in Client Registration with the new one typed in the Trip Booking screen. If a common location is re-geocoded or the phone number or comment changed, the system offers to update the information in the Locations screen. If set to No, any re-geocode of client or common locations in the Trip Booking screen affects only that booking. Master addresses in the Client and Locations screens are unaffected. |