Scheduler
A built-in tool that runs system tasks that are scheduled by the user. A system task is a task that is scheduled and performed by Planon ProCenter at the set time.
The scheduler processes notification and alarm tasks scheduled by the user at regular intervals. It is available in System Settings. In the scheduler (System Settings > Scheduled tasks) you can view the system tasks that exist in Planon ProCenter , and you can set the time interval at which they are run.
The time interval of the scheduler is specified in > .
 | • The scheduler uses the system date as reference date. • If you are working in a multi-time zone situation and the server and clients run in different time zones, the notifications will be offset once you switch from winter time to summer time. If, for example the server runs in a UTC time zone (not taking into account daylight savings), the first time an alert is run, the start date time is translated to the UTC time for the scheduler. After that the scheduler runs server side in the server's time zone. |
In addition to the time interval specified here, there is also a time interval specified at the notifications/alarm definition level. The following table outlines which interval setting becomes effective in which situation:
Time interval | ||
|---|---|---|
Notification-/Alarm definitions level | Scheduled tasks level | Result |
Every 5 minutes | Once per day | Once per day |
Every other day | Once per day | Every other day |
Tasks are handled according to their type:
Notifications
For notifications, an email is sent to each user who must be informed.
The email content is based on the selected mail merge template.
The email content is based on the selected mail merge template.
| | It is possible to use expressions in the Email subject field of the mail merge report that is linked to the notification. With an expression you can specify a dynamic email subject. Example: a notification's mail merge settings on orders could include an expression that adjusts the number of days an order is overdue in the email's subject, per notification. See Creating a dynamic email subject using expressions for an example. |
| | If the Email subject field is not populated, the name of the notification definition is used. If this is not populated either, the code of the notification definition is used. |
| | For more information on working with mail merge templates, see Creating a mail merge definition and a template file (Reports). . |
Alarms
For alarms, when the task returns an active alarm (ringing), an alarm status is created for each user linked to the alarm definition. When an alarm is no longer ringing it is removed from the My alarms selection step
Actions
For actions, a task is performed in a scheduled interval of time. A task could be anything such as the execution of the CAD Import and the renewal of Contracts. These actions are automatically performed by the system at a specified time.
| | If the Email subject field is not populated, the name of the notification definition is used. If this is not populated either, the code of the notification definition is used. |
| | For more information, see Creating a mail merge definition and a template file (Reports). |
| | Alerts are run based on the user who created the definition. If you have an overloaded scheduler, you can do one of the following: • Decrease the number of notifications. • Increase the interval of the notifications. • Increase the MaxConcurrentJobs in scheduler settings. |
| | For more information on MaxConcurrentJobs or Scheduler settings, see Additional scheduler settings (Administrator's Guide). |