PASS Trapeze6 Properties
Trapeze6 properties, or context properties, control the system appearance of PASS and other Trapeze applications.
| Context Property | Description |
|---|---|
|
This defines the number of minutes used for the time periods that group similar departure times together in the Drive Time Analyzer - DCES Update schedule job agent job type. For example, use 5 for 5-minute intervals, 15 for 15-minute (quarter-hour) intervals, and 30 for 30-minute (half-hour) intervals. The maximum is 1440 (24 hours). Use 0 to prevent departure time grouping. Note that setting this value too high can lead to reverse travel discrepancy warnings in the log. Values of 15 or less are recommended for better accuracy. If you change this value, restart the application. |
|
| Score to be assigned when Google returns a full match. This is a single defined value that will apply to all matches. (The lower the score, the better the match.) The default value is 1. |
|
| Score to be assigned when Google returns a partial match. This is a single defined value that will apply to all partial matches. (The lower the score, the better the match.) The default value is 500. |
|
| Score to be assigned when a partial match is returned for Google
auto-complete. This is a single defined value that will apply to all Google auto-complete partial matches. (The lower the score, the better the match.) For example, if Hospital is typed, Google may offer multiple suggestions of hospitals within the defined map area as partial matches. The default value is 500. |
|
| (Trip Broker) If selected, trip booking information cannot be edited after a booking has been performed unless the booking is unperformed. The property is cleared by default. | |
| (Trip Broker) If selected, users can create Provider Reimbursement (fare) rates and calculation. | |
| The setting used for drop-off logic distance calculations. If the property is set to Default, then the setting defined in Trapeze4 under , on the Profile tab, under is used. Setting the Trapeze6 Drop-Off Logic distance calc. method to another setting (PointToPoint, Triangulation, Barrier Restriction, or Street Routing) will use the distance calculation method as defined in Schedule Server. The default setting for this property is Default (that is, it will use a Faring calculation rather than a Schedule Server calculation). |
|
| MinimumDistance defines the shortest distance between pick-up (PU) and drop-off (DO) when a booking is created. | |
| If selected, Trapeze6 users can log in with their birth date if they are
missing an email address. If cleared, Trapeze6 users can log in with their date of birth one time only, and set a password to be used for future sessions. |
|
| (Trapeze Rapid Response) Client’s home address type. | |
| (Trapeze Rapid Response) Client’s emergency address type. | |
| The format of date of birth to be considered as WEB or IVR password (when or is set). Format options are as follows:
|
|
| If selected, clients can log in using either the ClientId or ClientCode. | |
| The Client Code prefix (Prefix = User Input + Suffix). Valid only if UseClientIdOrClientCode is selected. | |
| The Client Code suffix (Prefix = User Input + Suffix). Valid only if UseClientIdOrClientCode is selected. | |
| Schedule ID for use in the testing monitor screen. | |
| Default contact type for PASS clients. | |
| The maximum number of login attempts permitted before the account gets locked out (if EnableLockout is set). | |
| Maximum length of client IDs. | |
| Maximum length of client passwords. | |
| Minimum length of client passwords. | |
| If selected, client passwords must be digits only; entry checking is applied. | |
| . | If selected, the PassResetWebPassword() method resets the client password and resets a password lock out. If cleared, the lockout field is not reset when the client password is reset. Cleared by default. |
| If selected, the client code will be used to authenticate clients instead of the client ID. | |
| (PASS-Web/IVR only) If selected, the client date of birth will be used to
authenticate clients instead of the client ID. For more information, refer to the PASS-Web or IVR documentation. |
|
| Format of the client date of birth; currently can be either YYYYMMDD or DDMM. | |
| If selected, the client account will be locked out after this many attempts. Clients should call the transit agency to have their account unlocked. | |
| Name of the field in the Clients table that is used to lock or unlock clients. | |
| Name of the field in the Clients table that is used to store the number of a client’s continuously failed login attempts. | |
| Number of days in the past to apply or display DCES entries that can be updated. | |
|
Defines the percentage weight given to actual travel times to update the DCES cache times when an actual time has been recorded. For example, if the historical value for a given trip is 15 minutes and the new time is recorded as 11 minutes, and this value is set as 25 (%) then the travel time is calculated as: New time = (<difference weight> × <actual time>) + (1 – [<difference weight> × <historical time>]) = (0.25 × 11) + (0.75 × 15) = 2.75 + 11.25 = 14 |
|
| Defines the percent change between historical and actual times that trigger an automatic DCES update. For example, if this value is set to 5, and the percent change between the historical and actual times is only 3 percent, the system will automatically update the historical DCES record with the new time that is calculated. | |
| HTTP address for the debit card server. | |
| IP port of the debit card server. | |
| UserName for the DebitCard connection. | |
| Password for the DebitCard connection. | |
| Pooling time. | |
| URL for the ETIS web service. | |
| Port number for the ETIS web service. | |
| Average speed in kilometers per hour. | |
| Maximum journey results returned from ETIS. | |
| ETIS stop size. | |
| Maximum walking distance for a connection trip if not in the booking. | |
| Latitude to meter factor. | |
| Longitude to meter factor. | |
| Time distance overlay in meters for the extra buffer. | |
| Time offset factor to be multiplied with the max time for the requested pick-up time. | |
| Maximum initial ETIS stop result count. | |
| Maximum extended ETIS stop result count. | |
| Call trip eligibility condition code 1. | |
| Call trip eligibility condition code 2. | |
| Maximum time window expansion in minutes. | |
| Maximum distance expansion in meters. | |
| Start distance of the radius in meters. | |
| Distance expansion stop in meters. | |
| Distance expansion step in meters. | |
| Time window expansion step in minutes. | |
| PolyTypeId | |
| If selected, the ETIS JourneyPlanner is enabled. | |
| ETIS Stop size. | |
| Maximum ETIS result count. | |
| Booking tag abbreviation for setting requested times. | |
| Fare type for service lines. | |
| Fare type for call trips. | |
| Call trip requested early buffer minutes. | |
| Call trip requested late buffer minutes. | |
| Connection trip to stop requested time buffer. | |
| Call trip requested late buffer minutes. | |
| Connection trip booking tag abbreviation. | |
| Booking subtype for demand-response trips. | |
| Booking sutbype for transfer trips. | |
| Call trip text to display in the dialog box. | |
| If selected, searches can be stopped. | |
| If selected, timing is enabled. | |
| If selected, pick-up discount percent is enabled. | |
| If selected, drop-off discount percent is enabled. | |
| Should contain the same value for the jurisdiction PolyTypeId as found in PASS. | |
| Smallest purchase amount that can be made using the client purse. The default value is 0. |
|
| Maximum allowable purchase for EZ-Wallet. | |
| Entry mask for the confirmation number when purchasing with a credit card. | |
| Credit card type pairs (Code – Display Name). | |
| Debit card type pairs in the format Code – Display Name. | |
| IP Address or the domain of the website running PASS-Web. This is used to create links in the email messages sent by the system. | |
| Port of the Service Shell running PASS-Web. This is used to create links in the email messages sent by the system. |
|
| If selected, the web server is shown running the SSL protocol. This is used to create links in the email messages sent by the system. | |
| The maximum quantity of tickets allowed for Transport Unit purchases. | |
| The maximum quantity of tickets that can be purchased for Transport Units. | |
| The minimum quantity of tickets that can be purchased for Transport Units. | |
| Security group name for the user. | |
| Call center security group for the user. | |
| AssetWorks’ server address. For example, http://ServerAddress. | |
| Location of the *.asmx file, where Server Address is the
URL specified by the property. For example, http://ServerAddress/TrapezeIntegration/TrapezeIntegration.asmx. Web Services Source location is TrapezeIntegration/TrapezeIntegration.asmx. |
|
| AssetWorks namespace URL. For example, http://tempuri.org. | |
| Username to access the AssetWorks web services. | |
| Password to access the AssetWorks web services. | |
| Enables the INIT interface. | |
| Specifies the INIT API URL. | |
| Specifies the INIT Inspection API URL. | |
| User Name for 3rdParty INIT API access | |
| Password for 3rdParty INIT API access | |
| TimeOut for INIT requests in seconds | |
| Recall interval for unsuccessful operations. Value in minutes. 0 = Do not recall. |
|
| INIT API parameter (fara = 210, waltti = 213, t-card = 215, open loop = 217). | |
| INIT API parameter (Segment Number / Client in MOBILEvario). | |
| If a trip is performed and the system attempts to charge the client (using the INIT interface) and the attempt fails, this is the total number of times the attempt should be made before the system gives up. | |
| INIT API parameter (current operator of the vehicle). | |
| INIT API parameter (current route number). | |
| INIT API parameter (current line). | |
| INIT API parameter. | |
| INIT API parameter (driver number). | |
| FareTypeIDs | Comma-separated list of Fare Type IDs for which the INIT API is called. |
| Template for the Client Name display. | |
| Template for the driver information display. | |
| Template for the co-driver information display. | |
| Alias of the markup to be invoked during dispatcher update callbacks. | |
| If selected, dispatcher update notification is enabled. | |
| Precedence order used when selecting the phone number to be added to the notification. | |
| Alias of the markup to be invoked during driver initiated callbacks. | |
| Alias of the markup to be invoked during manually-triggered ImminentArrival callbacks. | |
| Alias of the markup to be invoked during noshow callbacks. | |
| Latency in seconds between two consecutive polls of the Notification database to monitor the telephony state of items added by the proxy. | |
| Delivery priority of Proxy notifications relative to other items handled by the delivery device (1–99), where 1 is high priority and 99 is low priority. | |
| Maximum number of times to try to send a notification requested by the Proxy. | |
| Message ID to be sent to the Stub service when the client requests to have the vehicle wait in response to a notification. | |
| Message ID to be sent to the Stub service when the client has canceled a trip in response to a notification. | |
| Message ID to be sent to the Stub service when the client has chosen to speak to a dispatcher in response to a notification. | |
| Message ID to be sent to the Stub service when the call was sent to the client during a notification. | |
| Message ID to be sent to the Stub service when no response was received from the client during a notification. | |
| Message ID and its corresponding canned message contents will be sent to the
MdtCenter when starting a NoShow notification. Set to 0 to disable this function. |
|
| Message ID and its corresponding canned message contents will be sent to the
MdtCenter when starting a Remind notification. Set to 0 to disable this function. |
|
| Life time of a transaction in sections. If the previous transaction is still in the life time and not yet completed, new transactions will be refused. |
|
|
Defines the number of days ahead of the FromDate for the ToDate (when a ToDate is not specified). When a from date is not specified, DateIntervalCheck uses the current date. The security permission allows users to access DateIntervalCheck. (This permission was added so that the Anonymous user could have access to this service if needed.) |
|
| If selected, all noshow events from the Schedule Server will be push no-show notifications. | |
| If selected, notification settings for new bookings will be stored in third-party format. | |
| Notification type used for a NoShow. | |
| Notification Type used for an Arrival. | |
| If selected, unscheduled trips are also returned by the PassGetCallbackTrips method. | |
| Address of the service to send messages to clients through third-party IVR systems. | |
| Port of service to send messages to clients through third-party IVR systems. | |
| Additional information that is appended to the RUI after the IP address and port. Note that an error may result if this value is left blank. | |
| Maximum length of time in milliseconds permitted for third-party IVR systems to respond to requests. | |
| Delivery timeout in minutes for third-party IVR systems. | |
| Interface for calling third-party IVR systems. | |
| Username for the third-party IVR shell. | |
| Password for the third-party IVR shell. | |
| Threshold in minutes for resending IVR callbacks. | |
| Threshold in minutes for sending reminders to clients. | |
| Threshold in minutes of schedule time changes required to send a reminder to the client. | |
| Number of itineraries to return. | |
| Default criteria to minimize when determining solutions. | |
| Search window start time in seconds from midnight. | |
| Duration of the search window in seconds. | |
| If selected, solutions will be also be sent to the ATIS server. | |
| If selected, the new ATIS interface will be used. | |
| ATIS namespace to be used in SOAP calls. | |
| ATIS default parameter set. | |
| If selected, polygon abbreviations will be sent instead of polygon IDs. | |
| If selected, the ATIS trip planner will be used; otherwise, the INFO trip planner will be used. | |
| Solution search radius around the route list. | |
| Solution search radius around the urban core. | |
| HTTP address and service name of the ATIS server. | |
| IP port of the ATIS server. | |
| Socket connection to the ATIS server time out. | |
| HTTP address, port, and service name of ATIS servers; used for load balancing. For example, 10:00-13/http://172.16.1.84:80/cgi-\bin-soap/soap.cgi,http://172.16.1.85:80/cgi-big-soap/soap.cgi;10:00-15:00\http://172.16.1.85:80/cgi-bin-soap/soap.cgi. | |
| Amount of time in minutes after the vehicle does not send an AVL message, the vehicle is considered not reporting. | |
| Maximum number of days ahead of the travel day that a casual booking can be created by a client. | |
| If selected, clients are allowed to book new trips on the same day as the travel day. | |
| If selected, clients are allowed to book a new trip on business days only.
This feature is for calculating the days window for PASS-Web or IVR. |
|
| SubType abbreviation if AllowSameDayBooking is selected and a special SubType is required for same day bookings created through the Web. | |
| If selected, clients are allowed to book a new trip only on the days loaded before by the Schedule Server. | |
| If selected, the client's suspended days are excluded from available booking dates. | |
| If selected, a flag is sent back to the client that represents the property’s policy on allowing an unscheduled booking to be canceled by a Web client. | |
| If selected, a flag is sent back to the client that represents the property’s policy on allowing an unscheduled booking to be scheduled by a Web client. | |
| If selected, a flag is sent back to the client that represents the property’s policy on allowing a scheduled booking to be scheduled by a Web client. | |
| If selected, a flag is sent back to the client that represents the property’s policy on allowing a scheduled booking to be canceled by a Web client. | |
| Default interval in minutes between each booking time returned by booking times methods. | |
| Minimum time in minutes between the current time and the requested time for a
new booking. Used to prevent clients from booking trips too close to the current time. |
|
| The available time (in time format) to specify whether the last booking day is an allowable booking day, for example, available time = 8:00, maximum days in advance = 2. If before 8:00, the 2nd day in advance is not valid to book, so the maximum days in advance is 1. If after 8:00, the 2nd day in advance is valid, so the maximum days in advance is 2. | |
|
|
| Number of days in advance the restriction should be applied for the Absolute time mode. | |
| Cutoff time of the day for the Absolute time mode. | |
| Used to calculate the window of valid booking times for a return trip; the minimum time in minutes that a client is required to spend at the chosen destination before being allowed to return. | |
| Logic used by PassBookingTimesWindow() to determine if any time can be returned. | |
| If selected, this property overrides times set in the and properties and matches polygon times (even if they fall outside
these windows). The OverrideWindowWithPolygonTime property returns the open and close times of the polygon from 0:00 to 24:00. |
|
| Start of the daily window of drop-off booking times. | |
| Close of the daily window of drop-off booking times. | |
| Start of a Monday window of drop-off booking times. | |
| Close of a Monday window of drop-off booking times. | |
| Start of a Tuesday window of drop-off booking times. | |
| Close of a Tuesday window of drop-off booking times. | |
| Start of a Wednesday window of drop-off booking times. | |
| Close of a Wednesday window of drop-off booking times. | |
| Start of a Thursday window of drop-off booking times. | |
| Close of a Thursday window of drop-off booking times. | |
| Start of a Friday window of drop-off booking times. | |
| Close of a Friday window of drop-off booking times. | |
| Start of a Saturday window of drop-off booking times. | |
| Close of a Saturday window of drop-off booking times. | |
| Start of a Sunday window of drop-off booking times. | |
| Close of a Sunday window of drop-off booking times. | |
| Start of the daily window of pick-up booking times. | |
| Close of the daily window of pick-up booking times. | |
| Start of a Monday window of drop-off booking times. | |
| Close of a Monday window of pick-up booking times. | |
| Start of a Tuesday window of pick-up booking times. | |
| Close of a Tuesday window of pick-up booking times. | |
| Start of a Wednesday window of pick-up booking times. | |
| Close of a Wednesday window of pick-up booking times. | |
| Start of a Thursday window of pick-up booking times. | |
| Close of a Thursday window of pick-up booking times. | |
| Start of a Friday window of pick-up booking times. | |
| Close of a Friday window of pick-up booking times. | |
| Start of a Saturday window of pick-up booking times. | |
| Close of a Saturday window of pick-up booking times. | |
| Start of a Sunday window of pick-up booking times. | |
| Close of a Sunday window of pick-up booking times. | |
| If selected, the schedule status ID will be overwritten for canceled trips. | |
| Trip cancellation status code for late cancellations. | |
| Trip cancellation status code for in-advance cancellations. | |
| Trip cancellation status code for same day cancellations. | |
| Trip cancellation status code for at-the-door cancellations. | |
|
Check schedule status:
|
|
| Trip cancellation status code for no-show cancellations. | |
| If selected, bookings will be stamped CS if the client cancels the trip on the same day that the trip is to be taken. | |
| If selected, bookings will be stamped CS instead of CL if the client cancels the trip on the same day that the trip is to be taken but at a late time. | |
| Trip time to be used in comparisons to the current time when calculating the new SchedStatus during a CancelTrip request. | |
| If selected, a confirmation number will be generated for each cancellation. | |
|
|
| Number of days before the pick-up that the absolute time will be applied to.
Used only if TimeMode is set to Absolute. |
|
| Cancellations after this time on the day specified by DaysBeforePickup will
be considered late. Used only if TimeMode is set to Absolute. |
|
| Minimum number of minutes before trip pick-up time that a cancellation may be
made through the service. Set to 0 to disable this feature. |
|
| Minimum number of minutes before trip pick-up time that a cancellation may be
made by a driver through the service. Set to 0 to disable this feature. |
|
| If selected, cancel late tolerance will be used. | |
| If selected, weekends will be excluded when checking for late
cancellations. Must be used with Absolute time mode. |
|
| If the trip is canceled within this many minutes before the requested pick-up time or any time after, the booking will be stamped as a noshow (schedule status NS). | |
| If the trip is canceled within this many minutes before the requested pick-up time or any time after, the booking will be stamped as a cancel at door (schedule status CD). | |
| If selected, cancel late tolerance will be used. | |
| If selected, weekends will be excluded when checking for late cancellations. Must be used with Absolute time mode. | |
| If selected, holidays will be excluded when checking for late
cancellations. Must be used with Absolute time mode. |
|
|
|
| Number of days before the pick-up that the absolute time will be applied to.
Used only if TimeMode is set to Absolute. |
|
| Cancellations after this time on the day specified by DaysBeforePickup will
be considered late. Used only if TimeMode is set to Absolute. |
|
| If a trip is canceled within this many minutes before the requested pick-up
time or any time after, the service will attempt to cancel it late (schedule
status CL). Used only if the time mode is set to Relative. |
|
| If selected, then new clients will be automatically marked as Active. This property is stored in the database. |
|
| Allows you to have mandatory inputs in the table for PassCreateClient method. | |
| If selected, then the trip purpose of a booking must be greater than 0 (that is, a valid booking purpose). | |
| If enabled, stores PU and DO legs addresses in upper case. | |
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.
|
|
| Maximum number of additional passengers allowed during trip booking. | |
| If selected, then the provider ID of the client in a new booking must be greater than 0 (that is, a valid provider). | |
| Minimum authorization number length. | |
| If selected, then eligibility dates of funding sources for a new booking will not be checked. | |
| If selected, then the booking purpose must match at least one of the funding source purposes when creating a booking. | |
| If selected, then clients will not be checked for suspension or eligibility. | |
| If selected, then inactive clients will not be allowed to create trips. | |
| If selected, then clients will not be checked for suspension or eligibility. | |
| If selected, then the origin and destination of a new trip must fall in at least one funding source polygon. | |
| 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 all passengers on a trip must have a valid fare type (that is, a fare type greater than 0). | |
| If selected, then all points of a trip must be correctly geocoded. | |
| If selected, then clients who wish to book a trip must have at least one eligibility condition defined. | |
| 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 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, then a new booking must have a valid paraservie ID. For example, from request, the client record, or an eligibility rule. | |
| 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. | |
| 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. |
|
| 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. |
|
| 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. | |
| 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. |
|
| Subtype abbreviation to stamp bookings when they are first created. | |
| If selected, then paraservice area rules will be checked. | |
| If selected, then Req DO Logic adds Direct To Adj. | |
| If cleared, then only the client’s first funding source will be defaulted. | |
| If selected, then when logged in as a worker, the Escort selection will be shown on the Book a Trip page, and the Escort will be viewed on the Trip Detail page. | |
| If selected, then a fixed route alternative will be found and displayed for the user’s trip. | |
| Specifies valid passenger types. When empty, all passenger types are valid. Otherwise, trips can only be created using the specified passenger types (comma-delimited string). Note that when companion mode is "D" and the client's default companion is considered invalid, PassCreateTrip will fail. |
|
| If selected, the default companion settings in the client record are ignored
and the maximum number of additional passengers defined in the context property is enforced. If IgnoreClientCompanionSetting is cleared, the default companion settings in the client record are respected and the MaximumNumberOfAdditionalPassengers is added to the existing default number of companions. This property is selected by default. |
|
Determines how to handle phone numbers when booking trips using
PassInfoServer (that is, Trapeze6). For example, when using the Book Trip screen
in PASS-Web.
|
|
| The same booking cannot be created within this number of minutes from the last time the booking was denied by Schedule Server. | |
| If selected, then the ATIS faring server will be called for a booking that has just been successfully saved during a PassCreateTrip call. | |
| Subtype abbreviation to stamp bookigns with when no ATIS faring solution is found. | |
| The Trip cancel code for ATIS server call failure. | |
| UserLong field (minus 1) to use for staring ATIS trip start times in Booking records. | |
| UserDouble field to use for storing ATIS trip start times in Booking records. | |
| UserDouble field to use for storing ATIS reduced fares in Booking records. | |
| User String field for storing ATIS routes in Booking records. | |
| UserString field to use for storing ATIS start times in Booking records. | |
|
Fare amount to save to a client’s companion:
|
|
|
Fare amount to save to clients:
|
|
| Client fare type when faring a booking by ATIS. | |
| Companion fare type when faring a booking by ATIS. | |
| If selected, the CreateTrip method will not auto-schedule a booking unless a successful ATIS faring call is made. | |
| 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. | |
| Start of a Monday window of booking trip access times. | |
| Close of a Monday window of booking trip access times. | |
| Start of a Tuesday window of booking trip access times. | |
| Close of a Tuesday window of booking trip access times. | |
| Start of a Wednesday window of booking trip access times. | |
| Close of a Wednesday window of booking trip access times. | |
| Start of a Thursday window of booking trip access times. | |
| Close of a Thursday window of booking trip access times. | |
| Start of a Friday window of booking trip access times. | |
| Close of a Friday window of booking trip access times. | |
| Start of a Saturday window of booking trip access times. | |
| Close of a Saturday window of booking trip access times. | |
| Start of a Sunday window of booking trip access times. | |
| Close of a Sunday window of booking trip access times. | |
| 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 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 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. | |
| Custom method name of eligibility tests. | |
| If selected, the tests of all client conditions are concatenated and tested together. | |
| Default pick-up solution set of eligibility tests. | |
| Default drop-off solution set of eligibility tests. | |
| Default eligibility test solution set. | |
| If selected, eligibility test swill be performed for all new bookings. | |
| Sets the logic used by PassCreateTrip() to determine if the trip can be
booked. For more information, contact Customer Care. |
|
| Sets the logic used by PassCreateTrip() to determine which funding source is
used to pay for the trip. For more information, contact Customer Care. |
|
| Sets the logic used by PassCreateTrip() to determine the subtype abbreviation
of the booking. For more information, contact Customer Care. |
|
| Sets the logic used by PassCreateTrip() to determine if a trip can be
scheduled. For more information, contact Customer Care. |
|
| If selected, ADA polygons and provider security will be checked on each newly-created booking. | |
| If selected, this service will not save new bookings that fail booking verification. | |
| If selected, then the service will not allow the creation of a booking that would overlap with an already existing scheduled booking by the same client. | |
| 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 of the same client to prevent overlap. | |
| Minimum amount of time in minutes that must exist between a new trip’s requested time and the drop-off time of an existing booking of the same client to prevent overlap. | |
| If selected, then the service will not allow the creation of a booking that
would overlap with an already-existing unscheduled booking by the same client.
Works with CheckForTripOverlap. |
|
| If selected, then the confirmation page will be displayed. | |
| Specifies the method of calculation through which the transaction fee will be charged. | |
| Percentage of the amount that will be charged as a transaction fee. | |
| Fixed amount that will be charged per transaction. | |
| Minimum amount that an account can be topped up in each transaction. | |
| Maximum amount that an account can be topped up in each transaction. | |
| Maximum amount that an account can have in total. | |
| If the account total is less than this amount, the top up option will be shown on the booking screen. | |
| Specifies the number of failures an auto top-up rule can have until it is temporarily disabled for the day | |
| Specifies the number of failing days an auto top-up rule can have until it is indefinitely disabled. A failing day is when the the number of failures within a day exceeds the value set in AutoTopUpDailyRetryLimit. The auto top-up rule remains disabled until it is enabled by the user. | |
| Enables email notifications to clients that autotop up has been disabled due to a credit card failing the allowed attempts. | |
| If selected, then the top up account module is accessible by users. | |
| If selected, the subscription function is enabled. | |
| First day of the week in a week template (also referenced by the PASS-Web calendar display) | |
| Schedule type ID used in live schedules. | |
| Schedule type ID used in template schedules. | |
| If selected, mobility aids are selectable by users. | |
| Default passenger type of a client for a new booking if a client’s record does not specify one. | |
| Default space type of a client for a new booking if a client’s record does not specify one. | |
| Passenger type of a client’s companion for a new booking if the client’s record does not specify one. | |
| Space type of a client’s companion for a new booking if the client’s record does not specify one. | |
| Fare type of a client’s companion for a new booking if the client’s record does not specify one. | |
| Default fare type for a passenger record when no others are available. | |
| Average speed for trip duration calculations in kilometers per hour (kph). | |
| ADA polygon type ID setting for the property. | |
| Jurisdiction polygon type ID setting for the property. | |
| Speed zone polygon type ID for the property. | |
| Service parameter polygon type ID setting for the property. | |
| Paraservice parameter polygon type ID setting for the property. | |
| Service area polygon type ID setting for the property. | |
| Booking PolyTypeId setting for the property. | |
| Default security group setting for the property. | |
| Name of the address type that represents a client home address. Typically, this is CH in North America. | |
| Name of the address type that represents an employee home address. Typically, this is EH in North America. | |
| Default booking subtype abbreviation. | |
| Booking subtype for solutions with transfers in it. | |
| Subtype that will cause bookings to be automatically unscheduled if updated to this subtype. | |
| Worker associates clients by the selected table. | |
| IVR survey from-date in RAW date format (YYYYMMDD). If set to 0, the survey from-date will not be checked. |
|
| IVR survey to-date in RAW date format (YYYYMMDD). If set to 0, the survey to-date is today. |
|
| If selected, can create will call bookings with given SubType (will not validate ReqTime for will call bookings). | |
| If selected, then comments will be displayed in PASS-Web. For example, on the booking screens and view trips screens. |
|
| If cleared, then clients can override existing comments or enter new comments
if there were originally no comments. If selected, comments are read-only. |
|
| If selected, then comment fields will be pre-populated with comments from the
selected booking locations if they exist. If cleared, then comment fields will always be blank to start with. |
|
| Comma-separated list of eligibility conditions with the WebEnabled flag set
to 1. If any of the user’s web-enabled conditions match any of the conditions in this property, the Book Trip option will be displayed, but repeat trips will be allowed. The default value is " (a single quotation mark) and is stored in the database. To enable an easy-to-use checklist of options, in the Client Shell, click , click the Screen Modules tab. Select the check box beside Cmn_Cli_CommonScreens, and then restart the Client Shell. |
|
| Email address for client registration. | |
| Email address to receive feedback submissions; multiple email address may be
entered, separated by a semicolon (;). The default value is “ (a single quotation mark) and is stored in the database. |
|
| Recipient of emails for customer subscriptions, particularly with canceling, holding, or adding subscriptions. | |
| Network location of email server. | |
| If selected, the service will calculate faring during certain methods. | |
| Maximum number of client transactions to be displayed on the My Account/My
Profile page. If set to 0, all transactions are returned. |
|
| Client default overdraft limit (0-9999.990000). Also used with EZ-Wallet. |
|
| If selected, the server will check for prepaid faring deductions on trip
cancellations or uncancellations. Also used with EZ-Wallet. |
|
| If cleared, the client must have enough account balance to prepay for all new bookings. | |
| If enabled, fare collection will be ignored at perform. | |
| If selected, fares use the client’s numPU. | |
| Distance unit. | |
| Time unit. | |
| Distance method. | |
| Fare distance polygon type ID. | |
| Fare distance polygon type ID. | |
| Multiple factor for interface fare calculation type. | |
| Default fare type ID if there are no trip solutions. | |
| Either deducts the full fare or nothing from the client account. | |
| Allows the fare to not be fully deducted, even if prepayment is required. | |
| Minimum allowable automatic top-up threshold for purse. | |
| Maximum allowable top-up threshold for purse (0 = no maximum). | |
| Minimum allowable automatic top-up deposit for purse. | |
| Maximum allowable auto top-up deposit for purse (0 = no maximum). | |
| Default fare type ID. If null, PASS defaults will be used. | |
| Number of minutes before and after the selected time to calculate a fare. | |
| Interval in minutes between user selectable times. | |
| Start of daily window of trip times in seconds from midnight. | |
| End of daily window of trip times in seconds from midnight. | |
| If selected, the lowest fare within the specified window will be applied. | |
| Default time increment in minutes for fare window. | |
| Default time offset in minutes from the requested time for the fare window. | |
| Default time window in minutes for fare calculation. | |
| Logic used by PassCreateTrip() and PassCheckClientFeatureAccess() to determine if a client can book trips. | |
| Logic used by PassCancelTrip() and PassCheckClientFeatureAccess() to determine if a client can cancel existing bookings. | |
| Logic used by PassGetClientTrips() and PassCheckClientFeatureAccess() to determine if a client can view existing bookings. | |
| Logic used to determine if a client can enroll in PASS-Web. | |
|
Allows an expression to determine if a client can create new bookings (that is, bookings that have not been pre-defined) to be defined. Used with PASS-Web. For more information about this feature, contact Customer Care. |
|
| Allows an expression to determine if a client's information can be updated. | |
| Time format used in returns to legacy clients. | |
| If selected, then the time format is returned to legacy clients in HHMMSS format. | |
| Date format in returns to legacy clients. | |
| If selected, then the date format returned to legacy clients is in YYYYMMDD format. | |
| Weekday template format in returns to legacy clients. | |
| If cleared, then the service will use StreetNo when returning booking legs; otherwise, it will use StreetNum. | |
| If selected, forwarding to the NOVUS shell is enabled. | |
| HTTP address to the NOVUS server. | |
| IP port of the NOVUS server. | |
| Username for the NOVUS shell. | |
| Password for the NOVUS shell. | |
| If selected, then the default provider is retrieved from the ClientProvider
table. If cleared, the providerID in the Clients table is used. |
|
| List of Address Types that are not available for booking online. The Value is a comma-delimited list of the allowed address types. For example, CH,CM,LO |
|
Defines how client trips should be sorted:
The default setting is Sort by oldest trips first. |
|
| Maximum number of records that will be returned by a call to GetClientTrips.
If any query produces more, an error will be returned instead. |
|
| Number of days from the current date for which GetClientTrips will search for active subscriptions. Set to 0 to report to the end of next month. | |
| Number of months, excluding the current month, to look back for previous
trips on the View Trips page. For example, if the current month is April, the value 3 lets the user select months going back to and including January. Set to 0 to set the earliest date to January 1990. The default is 0 and is stored in the database. |
|
| Precedence order used when selecting trip times to be displayed by browsers.
If Sch/Neg/Req are all blank, EstTime will be used if available. |
|
| If selected, then in the GetClientTrips response, then the value of the SchTime field will be that of the UserTime1 field when not empty. | |
|
If selected, PassInfoServer will return results for both the current day and the previous day (when the trip time is 24:00 or greater). For example, a trip scheduled on November 29 at 26:00 would be included in the results for November 30. If cleared, the system maintains the old behavior. This property is cleared by default. |
|
| Trips on the ViewTrips page will not be shown if the subtype abbreviation is equal to this value. If blank, no trips will be hidden. | |
| Expression to determine whether or not the displayed trip can be canceled. | |
| Expression to filter trips based on specific booking attributes. For example, CCSecGroup or SubTpeAbbr. | |
| If selected, then the provider message with a specific ProviderId will be displayed on the View Trip Page. | |
| If Enabled is selected, then the provider message with this ProviderId will displayed. | |
| Provider name corresponding to the ProviderId. | |
| Corresponding ProviderId message to be displayed if Enabled is selected. | |
| Provider message will appear only after this ShownTime (raw time) on the day before the trip. | |
| If selected, GetScheduleManifest will return MobAid descriptions. If cleared, MobAid codes are returned. |
|
| Path to report file for PDF version of GetScheduleManifest. | |
| Default duration of search windows in seconds from the current time. | |
| Maximum number of records to be returned. | |
| If selected, the caller will be asked to confirm any entered dates before continuing. | |
| If selected, the caller will be prompted for separate entry of the month (MM)
and day (D). If cleared, the date is entered all at once in YYYYMMDD format or DayOfWeek. |
|
| If selected, a date entered as DayOfWeek (for example, Monday or Tuesday)
that matches today’s DayOfWeek is interpreted to be one week from today. If cleared, today’s date is assumed. |
|
| If a date is entered with the month and day only without a year, this parameter indicates how many days prior to today to consider when assigning a year. | |
| If selected, the caller will be asked to confirm any entered times before continuing. | |
| If selected, the caller will be prompted for separate entry of the hour (HH) and minutes (MM). If cleared, the time is entered all at once in HHMM format. | |
| If selected, times will be read in 24-hour (military) format. If cleared, times will be read as AM or PM. | |
| (PASS-IPA) The user name used by Navitia to log into their API. The token provided by Navitia is the username. | |
| (PASS-IPA) Not currently used. Leave this field blank. If Navitia adds a password requirement, this field will be used for the password that corresponds to the Navitia user name (token). |
|
| World origin longitude point for distance calculations. | |
| World origin latitude point for distance calculations. | |
|
Distance calculation method:
|
|
| Maximum number of client nodes to return from PassGetMostFrequentClientNodes | |
| Number of days to look back for frequent addresses. | |
| If selected, trips booked in the future will also be considered when looking for addresses. | |
| If selected, the system will try to use the Payment Module for Pass purchases. | |
| If selected, payment processors will POST to a page when completed. Also, this is the url you will be directed to. | |
| Port number that the Schedule Server is listening on. | |
| IP address of the Schedule Server. | |
| Schedule parameter set name. | |
| Schedule violation set name. | |
| If selected, then booking’s negotiated times will be synchronized with its requested times during its creation as if the client had agreed to the booking. | |
| If selected, then booking’s negotiated times will be synchronized with its scheduled times during its creation as if the client had agreed to the booking. | |
| If selected, then tolerances will be applied to drop-off requested times when implicitly synching requested or negotiated times. | |
| Subtype abbreviation to be set for bookings when no scheduling solutions are found. | |
| This property determines when the denial subtype is stamped on the booking.
It can be stamped immediately, when the schedule server returns no solutions (that
is, when the trip is denied by the Schedule Server), or when the user confirms the
trip denial. The default behavior is to stamp the denial subtype when Schedule Server denies the trip. |
|
| Cancel code that is applied to the booking when no scheduling solutions are found. Leave empty to keep the booking unscheduled. | |
| If selected, then the booking record will be stamped with the provider that was specified by its scheduling solution. | |
| If selected, then solutions will be filtered for duplicate scheduled times and number of transfers. | |
| If selected, then extra information like RunName and Violations will be returned with any scheduling solutions that are found. | |
| If Off, then ESW and LSW parameters will be forced to 0 when scheduling a booking. | |
| If selected, then clients will be allowed to schedule trips. If cleared, clients are not allowed to schedule. |
|
|
Whether to enforce client providers:
|
|
| If selected, then available runs will be filtered by the logged in user’s security group. | |
| If selected, sets the maximum number of minutes allowed for scheduling trips that are earlier or later than its requested time. | |
| If selected, sets the number of minutes the search window is extended both ways after each unsuccessful search. | |
| Tolerance early for drop-off leg when a new booking is saved. | |
| Tolerance late for drop-off leg when a new booking is saved. | |
| Sets the logic used PassSaveSolution() to determine if a trip can be
scheduled. For more information, contact Customer Care. |
|
| If selected, then this service will delete bookings that fail to schedule. | |
| If selected, the service will delete bookings when scheduling solutions are requested for it but are not found. | |
| Tolerance early for pick-up leg when a new booking is saved. | |
| Tolerance late for pick-up leg when a new booking is saved. | |
| Decides the product to which service-based scheduling is applied. | |
| Decides what product to apply no service solution based on service based scheduling. | |
| If selected, then a valid password is required to log in before any service requests are allowed. A valid password can contain no characters. | |
| If selected, then the system will check if the client email is validated. | |
|
Dictates the accepted content of the password input tag. Can be set to one of the following:
|
|
| If selected, users can see features they are not permitted to use. | |
| If selected, clients are required to provide non-blank passwords for password-related operations. | |
| If selected, then clients can change their passwords. If cleared, password change text boxes will be read-only. |
|
| If selected, then any client records that are marked Inactive are treated as
if they don’t exist during authentication. If cleared, then a code indicating the Inactive state is returned. |
|
| Value is a comma-delimited list of ProviderIDs. The system will check the client record before letting the client log in online. If the client does not have a matching provider on file, they will not be able to access the web portal. For more information, contact Customer Care. |
|
| If selected, only numerical passwords are allowed. | |
|
Number of previous passwords to remember for IVR. New user passwords must not be included on this list. If 0 is used, no password history is enforced. |
|
| If selected, reset password for web logic is enabled. | |
| Lists the characters that cannot be used in a client password. | |
| Specifies the minimum length of the client’s password. | |
|
Specifies the constraints of the client’s password:
|
|
| If selected, passwords are required to use at least one special character.
Acceptable characters are as follows: \~`!@#$%^&*()-_+={}[]|;:<>,./?" |
|
| Specifies how many previous client passwords are to be stored in the ClientPasswordHistory table. | |
| The number of days a password is valid before the user needs to change or reset it. If set to 0, passwords never expire. | |
| Comma-separated list of dates in MMDD format of possible end dates for
subscriptions. If the user is not allowed to select an end date for a subscription, this list will be used. Otherwise, this property should be left empty. |
|
| If selected, then the current date is within the
EnableRenewNumDaysBeforeExpire and DisableRenewNumDaysBeforeExpire range. A button will be displayed for the user to automatically renew the subscription. |
|
| Number of days before a subscription expires to begin displaying a Renew
Subscription button to the user. Set to 0 to always display the button. The default value is 30. |
|
| Number of days before a subscription expires to stop displaying a Renew
Subscription button to the user. Set to 0 to always display the button. The default value is 14. |
|
| All subscriptions will be created with the IsPending flag set to this value. | |
| If selected, terms and conditions must be accepted to proceed with login. | |
| If selected, multiple client results can be viewed after performing a search. | |
| If true, this instance of PassInfoServer will launch the payment monitor
which will keep track of processing payments. This should ONLY be enabled on ONE
instance of PassInfoServer. Note: Changing this property requires restarting the
server shell
|
|
| A list of comma delimited emails addresses where notifications are sent to when a payment is unable to be processed. | |
| Maximum amount of times the payment monitor will try processing a message before moving onto other messages and then coming back to retry processing. | |
| Maximum amount of time to wait for any active message processing tasks to complete before forcibly destroying the PassPaymentMonitor instance. | |
| Timer interval to check the message queue for messages that are waiting, but
the monitor is not processing. Note: Changing this property requires restarting
the server shell. |
|
| Timer interval to wait before reprocessing a cycled message. Cycling the message, the PassPaymentMonitor should leave it for a while before rehandling. | |
| The host of the service that provides payment interfaces. | |
| The port of the service that provides payment interfaces. | |
| The payment card profile that contains information for the payment card service. | |
| Address type for the client’s country registration address. If empty, only the usual home address type will be created. |
|
| New Certification On the Fly clients will inherit all settings from the
master client, including the eligibility conditions. If there is an Administrative Unit (admunit) master client, then the client gets the eligibility conditions from the Administrative Unit master client. |
|
| Maximum number of stops to be returned from the stop look-up service. | |
| Maximum number of clients to be returned from the client look-up service. | |
| Maximum number of locations to be returned from the location look-up service. | |
| Text to show for the currency. | |
| Default Shelter Status in the Rapid Response Status screen. | |
| Default template for the Location fast find item. | |
| If selected, the TpaBooking module will be launched when the TpaBookingServer service starts. | |
| If selected, then a booking will be run through polygon checking during the PassLegacy1 plug-in startup so that all subsequent polygon checks will be fast. (This is because the mapping DLLs will have already been loaded.) | |
| Default DSN for the Config database. | |
| Default user name for the Config database. | |
| Default password for the Config database. | |
| Default DSN for the Config database. | |
| IP address that the CTM Server is listening on. | |
| Port number that the CTM Server is listening on. | |
| Default parameter set name for CTM Server. | |
|
If selected, the system changes some of its functionality to allow for double day scheduling and viewing of trips. |
|
| IP address that the Schedule Server is listening on. | |
| Port number that the Schedule Server is listening on. | |
| Lists the ObjectType/DeviceAbbr pairs that are authorized to be retrieved
from the function GetContactInfo, which returns client information associated with
a defined BookingID. ObjectType/DeviceAbbr pairs defined in this property are separated by semi-colons and ObjectTypes and DeviceAbbrs are separated by commas (without spaces). For example, if the client has CH Phone; CH Email; and EM Email, then the property will show CH,Phone;CH,Email;EM,Email; Leave the property blank to return all contact information for the client. |
|
| Defines the refresh period. | |
| Template for the Cmn Person name display. | |
| If selected, check the provider status of the booking when determining if the booking can be cancelled. | |
| Default name of exported reports. | |
| If selected, synchronization now uses a different thread than the Service Shell, which speeds start up. | |
| Maximum number of days in the past that each provider will be able to view or
edit. To specify no restrictions, use 0. |
|
| When true, show provider status on Trips View in Manage Clients and Manage Bookings. | |
List of trip statuses that are allowed for export:
|
|
| If selected, trips are shown on a map in a new pane in Trip Broker. The map shows pick-up and drop-off locations. AVL information is shown if the previous run event has been performed and the vehicle is going to the client, or if the client is on board. |
|
| Enable bidding logic. | |
| Set up refresh period (in seconds). | |
| Set up refresh period for provider cost calculation (in seconds). | |
| Round bid amounts to whole dollar values. | |
| Minimum time between the earliest booking on the lot and the end date/time of the lot. | |
| Defines the template for the actual vehicle in itinerary view. | |
| Defines the template for the actual driver field in itinerary view. | |
| InfoServer host address. | |
| InfoServer IP port number. | |
| InfoServer user name. | |
| InfoServer password. | |
| Enable Trip Broker offer logic. | |
CSV of trip statuses when provider from the run will be set on the trip.
|
|
CSV of trip statuses when provider will be removed from trip.
|
|
| CSV of user names from which to trace Trip Broker requests. | |
| If selected, multiple values entered into the run itinerary grid will be saved in one request. | |
| If selected, a column sorting plug-in is enabled for runs. Default setting is cleared. |
|
| If selected, Para runs are reordered by actual odometer in bulk edit. | |
| If selected, Taxi and Clip runs are sorted bu client last name, client first
name, and BookingId. Default setting is On. |
|
| If selected, events can be dragged-and-dropped inside the itinerary.
Default setting is On. |
|
| If selected, odometer values are validated. Default setting is On. Trapeze recommends selecting Off if sorting is enabled. |
|
| Enables a timeout for a status. | |
| Defines refresh period for status expiry (in seconds). | |
| Defines how long the status has to transition before it expires. | |
| Status to which the expiry times applies. | |
| Status to transition to when the Transition From status expires. | |
| Interface type. | |
| Default PCA type abbreviation. |