Notification Delivery Properties
The following table explains the Notification/Delivery context properties that apply to INFO-Web G3.
| Property | Description |
|---|---|
| If selected, the Notification Delivery services is started. | |
| If selected, notifications are sent by Email service. Restart the Notification service to apply your change. |
|
| Latency in seconds between two consecutive database polls when searching for maturing items deliverable by Email service. | |
| Maximum number of records to fetch at any given database poll. A value of 0 means
an unlimited number. This is the default. Restart the Notification service to apply your change. |
|
| Path of Temporary folder for email attachments. Click the folder icon on the
Value field to open the Browse for folder
dialog box. Restart the Notification service to apply your change. |
|
| If selected, NotificationWaitingArea records with common Alert IDs are grouped
together upon delivery. Email addresses are batched into a single, comma separated
list in the Bcc field. The MessageBody is used to differentiate between Email and SMS messages that are delivered through the Email Gateway. |
|
| Maximum number of records sent in an email message when Alert Grouping is
selected. Note: This value must never be less than 1. A value of 1 effectively
disables Alert Grouping. The default and minimum value is 1. |
|
| Number of days the Email delivery device should look back when searching for notifications with dat files that need to be deleted. Notifications with a delivery date before this look back period will not have their dat files purged. | |
| If selected, the dat file created for the notification is preserved after the notification is sent. If not selected, the dat file is deleted. This is the default. | |
| If selected, the system manages the deliverable items from the Apple Push Notification service. | |
| Latency in seconds between two consecutive database polls when searching for maturing items deliverable by APN. | |
| Maximum number of records to fetch at any given database poll. A value of 0 means an unlimited number. This is the default. | |
| iOS application bundle ID, which is usually a reverse domain name style string. | |
| If selected, the Apple development notification server will be used, This is only used if the application is in the development stage. | |
| Full path of the certificate file, which Apply provides in Privacy Enhanced Mail (PEM) or p12 (pkcs #12) format. | |
| Password for the certificate file, if any. | |
| Full path to the private key file, which Apple provides in PEM format. If the pkcs #12 format is used, it can be empty. | |
| Password for the private key file. | |
| If selected, the system manages the deliverable items from the Google Cloud Messaging (GCM) push notification service. | |
| Latency in seconds between two consecutive database polls when searching for maturing items deliverable by GCM. | |
| Maximum number of records to fetch at any given database poll. A value of 0 means an unlimited number. | |
| API key used to contact Google | |
| If selected, any GCM request is sent through the Firebase Cloud Messaging (FCM)
push service, which is the new version of GCM. FCM in legacy mode is backward compatible with GCM. We recommend that this property remain selected. |
|
| If selected, notifications sent by SMS service. Restart the Notification service to apply your change. |
|
| Latency in seconds between two consecutive database polls when searching for maturing items deliverable by GCM. | |
| If selected, the notifications are delivered through the email server. Restart the Notification service to apply your change. |