Alerts Configuration
You use alerts to move information along and to monitor your data for potential problems that may require corrective action.
- You must submit timesheets and expense reports
- Transactions are submitted, approved, or rejected.
If you have not yet implemented DPS and plan to import a lot of data as part of the implementation process, you may want to wait until that process is completed before enabling alerts. If you enable the alerts before importing data, the import process may generate a lot meaningless alert notifications as it creates batches of new records.
Alerts and Workflows
Alerts and workflows are similar in they way move information along. However, you can configure workflows to a greater degree to meet your company's business rules. For example, you can configure workflows to notify you when an event occurs, and also to perform a specified action such as updating information in a field.
Alert Options
Use Alerts Configuration to specify:
- When alerts are sent
- How the alerts are sent (email message or via the notification center)
- Under what conditions the alerts are sent
- The contents of the email message (subject and message body) when alerts are sent via email messages
The options available vary and depend upon the alert type.
Polling Interval
To activate activity alerts, you must set the alert polling interval to a level other than zero. Deltek recommends a value of 60.
Alerts and Emails
Before you specify that you want to send alerts via email messages, verify that the DPS URL is set up correctly on the Email tab in . All alert email messages contain information that you can use to track down alert problems. This information includes the database name, database server, application server, and company code (if you use multiple companies).
Types of Alerts
There are two types of alerts.
| Alert type | Description |
|---|---|
| Alerts triggered by a reaction to information defined on your process server. (Most alerts are triggered by the process server.) | The process server:
|
| Alerts triggered by a change in information in your database. | Database alerts:
|
Alerts and Process Servers
For each alert, process server information displays, including: status (such as running, waiting, or complete), the time the run started and ended, the time of the next run, and the frequency of the run. For most alerts, run frequency is connected to their functionality.
Alert history is retained. After each run of an alert, the job is retained and the new job is re-inserted back into the queue. This allows you to view error messages or to confirm that the jobs run correctly. The alerts' queue clears on an hourly basis and retains only the most recent 20 jobs (for successful runs) and 40 jobs (for errors).
System vs. Company Alerts
You set Accounting and Resource Planning alerts on a system-wide basis.
You set Time, Expense, Purchasing, and Transaction Center alerts at the company level.
Alerts and Multiple Languages
If your firm uses multiple languages, a Languages lookup displays on the Alerts Rules grid. This lookup displays the languages that the system administrator enabled in Module Activation. Use this lookup to select the language for this alert. Only employees with the same selected language receive the message. However, if the field is blank, all employees receive the message, no matter what language is used.
For example, if an email alert is set up for English US and English UK, then only employees that have English US or English UK specified in the Language field in Employees receive that message. The administrator must set up a separate alert rule for Spanish employees if they require messages in Spanish.
The Language field displays <languages selected> if any languages are selected.
Alerts and Multiple Companies
If your firm uses multiple companies, you must set up alerts for each company. Because an employee may be associated with more than one company, the alerts only consider the employees that are active in the company for which the alert is configured.
For example, employee John James may be associated and active in Company A and Company B, and associated but inactive with Company C. Company A will send an email alert if a timesheet is late by 2 days, and Company B and Company C will send an email alert when a timesheet is late by 4 days. Because John James is only active in Company A and Company B, he will receive an alert from Company A after 2 days and from Company B after 4 days. He is inactive in Company C, so even though an alert is configured, it will not be sent.
When an alert is configured to be sent to the employee's supervisor, the email message goes to the employee's home company supervisor. For more information, see the discussion of employees and the Multicompany application in the Concepts section.