Setting up the Alerts System Settings should be performed after the outgoing email settings were set and tested (see Outgoing Email Settings). This is to make sure you actually receive Alerts once they are ready, and to avoid the unnecessary accumulation of Alerts that could not be sent due to wrong outgoing emails settings, etc.
To set up the Alerts Server, log-in to the server, open a command prompt and run: <Installation_DIR>\Server\ServerConfig.exe
The following window will appear:
Alerts Server Setting Window
Alerts Server Settings:
| • | Alerts Mode – The Alerts mode can be one of the following: On, Off or Pause. On - You should use the On setting when you wish to activate the Alerts mechanism. Note that if you activate the Alerts after they have been Paused (see below), you may wish to consider deleting some old Events from the queue in order to avoid Alerts for old Events from being sent once you reactivate the server. See more details on how to delete Events from the queue below in the Clearing the Activity Queue option. Off (default) - This mode should be used when you do not want the system to prepare or send Alerts at all. This means events in the system will not create any Alerts, and when you re-activate the Commit Alerts Server, no Alerts will be waiting to be sent. When installing the Commit Alerts Server, the system is OFF by default, and should be set to ON when you wish to activate the Alerts mechanism. Pause - This mode should be used when you want the system to create Alerts for events in the system, but avoid sending them until you switch the mode to On. This can be helpful when you have SMTP/mail server problems and you want to fix them before activating the Alerts. Note that in this Pause mode, the Alerts accumulate until you reactivate the Alerts system. Once you reactivate the system, you should consider deleting old Alerts from the queue, as they may already be irrelevant (see Delete Alerts option below). Note that if you have SMTP/mail problems, it is advisable to use the Pause option, since it collects the Alerts before sending them to the outgoing email. This allows you to delete old Alerts later from the queue since they have not been sent. If you leave the system working, the Alerts will be accumulated as outgoing emails, and once the problem is fixed, they will all be sent, and you will not be able to clean up older Alerts. |
| • | From Email Address, Email Sender Name - Here you define the Email From Address that will be used when sending the Alerts. You can define an Alias to be used which will reflect the source of this email (such as "CommitCRM Alert"). |
| • | Clearing the Activity Queue - This is an advanced option, which should be used carefully. You should use this option in cases where you wish to delete pending Events which haven't been sent as Alerts yet. For example, if you have SMTP/mail Server problems, and you paused the Commit Alerts system, you may wish to clean up the queue of Events and keep only the last day or two. This is to avoid sending a large number of Alerts at once when reactivating the system, and also to avoid sending Alerts for old events which are no longer relevant. |
Important Notes: 1. Alerts will start to be sent only after each user defines their own Alert settings (and only when CommitServer service is running) 2. System Alert setup may take some time to take effect in the Commit Server. In order for it to take effect immediately, you should restart the Commit Server Service. |