Create Trip
The Create Trip context properties define the various booking policies or rules that may exist at a client site. In most cases, the options and values applied should be the same as those in Trapeze PASS.
| Property | Description |
|---|---|
| Start of the daily window of booking trip access times. | |
| Close of the daily window of booking trip access times. | |
| If selected, booking trip access is closed on holidays. | |
(… stands for the days of the week) |
Sets the Start of window for creating trips through the IVR on the specified day. This setting overrides the global WindowOpen for that day only. |
| (… stands for the days of the week) | Sets the Close of window for creating trips through the IVR on the specified day. This setting overrides the global WindowClose for that day only. |
| If selected, then calculation of the ReqTime of the pick-up is based on the trip time-distance against the ReqTime of the drop-off and then the ReqTime of the drop-off will be moved to ReqLate. | |
| If selected, then calculation of the ReqTime of the pick-up uses only the average
speed. If cleared, then the MaxOBT and factors tables will be used. |
|
| If selected, then the time requested will be compared to the valid ADA polygon times for the pick-up and drop-off polygons. | |
| If selected, then inactive clients will not be allowed to create trips. | |
| If selected, then all points of a trip must be correctly geocoded. | |
| If selected, then paraservice area rules will be checked. | |
| If selected, then the origin and destination of a new trip must fall in at least one funding source polygon. | |
| If selected, then the booking purpose must match at least one of the funding source purposes when creating a booking. | |
| If selected, then clients who wish to book a trip must have at least one eligibility condition defined. | |
| If selected and a denial exists that matches a new booking, then it will be superseded by the new booking upon saving. | |
| Early tolerance when comparing requested times of denials and new bookings. | |
| Late tolerance when comparing requested times of denials and new bookings. | |
| If cleared, then only the client’s first funding source will be defaulted. | |
| The same booking can not be created within this number of minutes from the time the last booking was denied by the schedule server. | |
| If selected and DO (drop-off) Logic is used, then the requested pick-up time will
be moved outside of the drop-off early/late window (if ReqDoEtAdj > TravelTime). If cleared, then the system will use TravelTime only to calculate the requested pick-up time. |
|
| If selected, then the GetClientInfo method returns a flag to indicate when the client is conditionally eligible and that new bookings are not allowed to be created. | |
| Custom method name of eligibility tests. | |
| If selected, then testing will not stop at the first test that denies the trip. | |
| The outcome when there are no tests for the eligibility condition. | |
| The outcome when the perform tests is set to No for the test condition | |
| Precedence order of eligibility tests. | |
| If selected, the tests of all client conditions are concatenated and tested together. | |
| If selected, eligibility test swill be performed for all new bookings. | |
| Default pick-up solution set of eligibility tests. | |
| Default drop-off solution set of eligibility tests. | |
| Default eligibility test solution set. | |
| If selected, then client eligibility rules will be enforced for all new bookings. | |
| If selected, then at least one passenger must have a Passenger Type equal to the client’s default passenger type. | |
| If selected, then prepayment for all new bookings of the client will be skipped if the client’s record is set as Prepayment Not Allowed. | |
| If selected, when login as a worker, Escort selection will be displayed on Book a Trip page, and Escort will be viewed on Trip Details page. | |
Use bitwise operation to exclude validation checks. Exclude multiple checks by
adding these numbers. (For example, 2 + 4 = 6 to exclude ADA and Service Area.)
|
|
| If selected, then all passengers on a trip must have a valid fare type (that is, a fare type greater than 0). | |
| If selected, then a fixed route alternative will be found and displayed for the user’s trip. | |
| If selected, PassCreateTrip counts the default companion toward the limit on additional passengers. | |
| Subtype abbreviation to stamp bookings when they are first created. | |
| Maximum number of additional passengers allowed during trip booking. | |
| Maximum number of trips allowed to be created by a given client each day.
Subsequent trip creations will not be allowed by the PassCreateTrip method. Set to 0 to disable this feature. |
|
| Maximum number of trips allowed for a client on a given LDate. Subsequent trip creations will not be allowed by the PassCreateTrip method. Set to 0 to disable this feature. |
|
| Minimum authorization number length. | |
| If selected, then eligibility dates of funding sources for a new booking will not be checked. | |
| If selected, then a new booking must have a valid paraservice ID. For example, from request, the client record, or an eligibility rule. | |
| If selected, this service will not save new bookings that fail booking verification. | |
| If selected, ADA polygons and provider security will be checked on each newly-created booking. | |
| If selected, then the provider ID of the client in a new booking must be greater than 0 (that is, a valid provider). | |
| If selected, then Req DO Logic adds Direct To Adj. | |
| If value is set to Both, Pickup Phone, or Dropoff Phone, the specified phone number(s) must be provided when creating a booking. | |
| If selected, then clients will not be checked for suspension or eligibility. | |
| If selected, then load and unload times from various sources (for example, request, client record, address or location, space type, and paraservice ID) will be summed into BookingLeg records. Otherwise, only the load-unload time from the request will go into booking legs. | |
|
If selected, the service does not allow the creation of a booking that would overlap with an already existing scheduled booking by the same client. The estimated length (in time) of the new trip will be used in this calculation. |
|
|
|
If selected, the service checks for new bookings against old bookings that are yet to be scheduled. It does not allow the creation of a booking that would overlap with an already existing unscheduled booking for the same client. This property is only applied if the CheckForTripOverlap context property is On. |
|
Sets the minimum amount of time (in minutes) that must exist between the drop-off time of an existing booking and the requested time of a new trip to prevent an overlap. This also applies when placing a new trip before an existing booking, for example, between the new trip's drop-off time and the requested pick-up time of the existing booking. |
|
|
Sets the minimum amount of time (in minutes) that must exist between a new trip's requested time and the pick-up time of an existing booking for the same client to prevent an overlap. |
|
|
If selected, the trip purpose of a new booking has to be greater than 0. |
|
| If selected, the trip purpose of a new booking has to be > 0 (valid booking purpose). | |
|
|
If selected, the origin and destination of a new trip must fall in at least one funding source polygon. |
| Allows bookings for trips with passenger types. |