INFO-Web Context Properties
Context properties allows you to access the centrally defined and maintained property values. This section lists the various categories and sub-categories of INFO-Web properties and their descriptions. Note that some categories have several sub-categories while some properties are shown as categories on their own, for example, Filter Lines By StopId.
| Property | Description |
|---|---|
| If selected, users are allowed access to INFO-Web. If not selected, INFO-Web is not activated. | |
| IP address or the domain name of the Service Shell running INFO-Web. If not set (field is blank), the IP address or domain name of the current page is used. This is the default. |
|
| Port of the Service Shell used for INFO-Web G3. If not set, the port of the current page is used. The default is 0. | |
| Frequency in seconds of how often INFO-Web refreshes the GetContext cache. You must restart the Service Shell after setting this value. | |
| If selected, users are allowed to access a feature that determines their current location. If not selected, their current location is not identfied. | |
| If selected, service adjustments are applied to all trips and stop times. This is not selected by default. | |
| INFO-Web Agency ID set as the default. (This is used in a multi-agency environment.) If not used, it is set to 0, which is the default. | |
| Minimum allowable start date from which a trip plan can be performed. | |
| If selected, the Search field in which users can search
for landmarks by name is activated on the Landmarks tab. If not selected, the field is not activated. This is the default. |
|
| Sets the number of days ahead into future sign-up periods so that users can
perform trip planning for dates that fall within future sign-up periods. Line data from the current and future sign-up periods will be loaded. If a route is found only in a future sign-up period, a message will be displayed showing when it will become active in the Routes screen. Trips on dates that fall within a future sign-up period will only use lines that exist within that sign-up period. |
|
| Number of days prior to the current date during which users can request itineraries. The default is 14, Min (minimum) is 0, and Max (maximum) is 365. | |
| If selected, the abbreviated service name is displayed. This is the default.
If not selected, the full service name is used. |
|
|
If selected, the GetDefaultOptions query uses the InfoFarePassengerType table for passenger types. If not selected, it uses the FarePassengerType table. If using the CTM engine, this property must be selected. If using the CTM Server, the setting depends on the faring module used. This is not selected by default. |
|
| If selected, users are allowed to provide feedback through INFO-Web. | |
| Email address to which feedback submitted through the INFO-Web Feedback module is sent. The field is blank by default. | |
Sets how the list of lines are sorted. The options are:
|
|
| If selected, users are allowed to save pages as favorites or bookmark pages with the My Profile feature. This is not selected by default. | |
|
Type of security validation applied when users fill in forms in order to prevent spam. The options are:
|
|
| Sets a value for the variable that will not be changed when a user submits a completed form, for example, registration. (Honeypot is a system that aims to detect and counteract spam and unauthorized use of the product.) The field is blank by default. | |
| User action when submitting a form changes one of the Honeypot variables to the defined value of the property. The default is true. | |
| Private key for the reCAPTCHA plugin. (reCAPTCHA is a CAPTCHA-like system that is used to establish that a computer user is human not a bot.) |
|
| Public key for the reCAPTCHA plugin. | |
| Walking speed set as the default. If set to 0.0, the walking times are not calculated. The default is 0 (kmh). | |
| If selected, the Passenger Type option is displayed in the Trip Planning page. | |
| If set to a value greater than 0, the system defines the margin (in seconds) around the current system time. If the itinerary request time falls within that margin and the Early Leeway Time Parameter is set to 0, the system looks for solutions from the requested time without any early leeway being subtracted. Trips in the past are not included in the solution if the client is requesting for the Next trips. This is set to 0 by default. | |
|
The following options determine how itineraries are searched around the requested time:
|
|
| Minimum distance threshold for displaying walking instructions for an individual walking leg, for example, distance from trip origin to first stop. This is set to 0 by default. The minimum is 0 and the maximum is 5000 meters. | |
| Maximum distance to recommend for the user to walk. If the straight-line distance between the trip's origin and destination is less than this value, set the ConsiderWalking flag of the itinerary (in the ItineraryLookup response) to 1. The default is 0. The minimum is 0 and the maximum is 5000 meters. | |
| If selected, fares of all passenger types that are defined in the system are included when requested in the itinerary details. This used only with the CTM Server. This is not selected by default. | |
| Vehicle class ID used as the default when generating pedestrian walking instructions. It is set to 0 as internal default. |