Notification Generator Properties
The following table explains the Notification context properties for Remarks,Schedule-Based Alerts, and Service Notices that apply to INFO-Web G3.
| Property | Description |
|---|---|
| If selected, remarks are generated and sent to users who have service notice subscriptions provided that the delivery method they requested is also activated. | |
| Number of minutes after a remark notification has expired. No attempts are made to send an expired notification. | |
| GeneratorTransitNowRemarksPollingInterval | Latency in seconds between two consecutive database polls when searching for new remark notifications to send. |
| Delivery priority of remark notifications relative to the other items handled by the delivery device. This range from 1 (high priority) to 99 (low priority). | |
| Number of days that the system looks back for remarks. Notifications are not sent for remarks with a from date before the set range. | |
| Number of days to look ahead for remarks. Notifications are not sent for remarks with a from date after the set range. | |
| If selected, remarks notifications are sent by email to users with service notice subscriptions (for remarks) who requested them. | |
| Alias of the page used to generate the notification message. | |
| Maximum number of times that the system attempts to send the remarks by email. | |
| If selected, remark notifications are sent through an SMS (Short Message Service) service to users with service notice subscriptions who requested them. | |
| Alias of the page used to generate the notification message. | |
| Maximum number of times that the system attempts to send remark notifications through an SMS service. | |
| If selected, schedule-based alerts are generated and sent to users who have service notice subscriptions provided that the delivery method they requested is also activated. | |
| Number of minutes after a schedule-based alert notification has expired. No attempts are made to send an expired notification. | |
| Latency in seconds between two consecutive database polls when searching for new schedule-based alert notifications to send. | |
| Delivery priority of schedule-based alert notifications relative to the other items handled by the delivery device. This range from 1 (high priority) to 99 (low priority). | |
| Number of minutes to look ahead for schedule-based alerts. Notifications are not sent for schedule-based alerts with a from date after the set range. | |
| If selected, schedule-based alert notifications are sent through email to users with service notice subscriptions who requested them. | |
| Maximum number of times that the system attempts to send schedule-based alerts through email. | |
| Email address that appears in the From field and identifies sender of the email. | |
| Number of trip times that the email service returns regardless of the routes. | |
| Number of trip times that the email service returns for each route and route direction that passes the selected stop. | |
| Text that appears in the email message when there are no available times for the requested stop. | |
| If selected, real time data is included in the email message. | |
| If selected, schedule-based alert notifications are sent through a Voice (IVR) service to users with service notice subscriptions who requested them. | |
| Maximum number of times that the system attempts to send schedule-based alerts through a Voice (IVR) service. | |
| Alias of the VoiceXML page served to the recipient of the call. | |
| If selected, service notices are generated and sent to users who have service notice subscriptions provided that the delivery method they requested is also activated. | |
| Number of minutes after a service notice notification has expired. No attempts are made to send an expired notification. | |
| Generator TransitNow ServiceNotices PollingInterval | Latency in seconds between two consecutive database polls when searching for new service notice notifications to send. |
| Delivery priority of service notice notifications relative to the other items handled by the delivery device. This range from 1 (high priority) to 99 (low priority). | |
| Number of days that the system looks back for service notices. Notifications are not sent for service notices with a from date before the set range. | |
| Number of days to look ahead for remarks. Notifications are not sent for service notices with a from date after the set range. | |
| If selected, service notice notifications are sent by email to users with service notice subscriptions (for service notices) who requested them. | |
| Alias of the page used to generate the notification message. | |
| Maximum number of times that the system attempts to send the service notices by email. | |
| If selected, service notice notifications are sent through an SMS (Short Message Service) service to users with service notice subscriptions who requested them. | |
| Alias of the page used to generate the notification message. | |
| Maximum number of times that the system attempts to send service notice notifications through an SMS service. |