Enter the following properties for a schedule.
Table 16: Schedule properties
|
Name |
Schedule ID. Translate the given text using the  button. |
|
Description |
Detailed description of the schedule. Translate the given text using the button. |
|
Table |
Table whose data can be used by the schedule. |
|
Enabled |
Specifies whether the schedule is enabled.
NOTE: Only active schedules are run. Active schedules are only run if the QBM | Schedules configuration parameter is set. |
|
Time zones |
Unique identifier for the time zone that is used for running the schedule. Choose between Universal Time Code or one of the time zones in the menu.
NOTE:
When you add a new schedule, the time zone is preset to that of the client from which you started the Designer. |
|
Start (date) |
The day on which the schedule should be run for the first time. If this day conflicts with the defined interval type, the first run is on the next available day based on the start date. |
|
Validity period |
Period within which the schedule is run.
-
If the schedule will be run for an unlimited period, select the Unlimited duration option.
-
To set a validity period, select the Limited duration option and enter the day the schedule will be run for the last time in End (date). |
|
Occurs |
Interval in which the task is run. Other settings may be required depending on the settings.
-
Every minute: The schedule is run once a minute. The starting point is calculated from the rate of occurrence and the interval type.
-
Hourly: The schedule is run at defined intervals of a multiple of hours such as every two hours.
-
Under Repeat every, specify after how many hours the schedule is run again.
-
The starting point is calculated from the rate of occurrence and the interval type.
-
Daily: The schedule is run at specified times in a defined interval of days such as every second day at 6am and 6pm.
-
Under Start time, specify the times to run the schedule.
-
Under Repeat every, specify after how many days the schedule is run again.
-
Weekly: The schedule is run at a defined interval of weeks, on a specific day, at a specified time such as every second week on Monday at 6am and 6pm.
-
Under Start time, specify the times to run the schedule.
-
Under Repeat every, specify after how many weeks the schedule is run again.
-
Specify the set day of the week for running the schedule.
-
Weekly: The schedule is run at a defined interval of months, on a specific day, at a specified time such as every second month on the 1st and the 15th at 6am and 6pm.
-
Under Start time, specify the times to run the schedule.
-
Under Repeat every, specify after how many months the schedule is run again.
-
Specify the days of the month (1st - 31st of the month).
NOTE: If the Monthly interval type with the sub interval 29, 30 or 31 does not exist in this month, the last day of the month is used.
Example:
A schedule that is run on the 31st day of each month is run on April 30th. In February, the schedule is run on the 28th (or 29th in leap year).
-
Yearly: The schedule is run at a defined interval of years, on a specific day, at a specified time such as every year on the 1st, the 100th, and the 200th day at 6am and 6pm.
-
Under Start time, specify the times to run the schedule.
-
Under Repeat every, specify after how many years the schedule is run again.
-
Specify the days of the year (1st - 366th day of the year).
NOTE: If you select the 366th day of the year, the schedule is only run in leap years.
-
Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday: The schedule is run on a defined day of the week, in specified months, at specified times such as every second Saturday in January and June at 10am.
-
Under Start time, specify the times to run the schedule.
-
Under Repeat every, specify after how many days of the month the schedule is run again. The values 1 to 4, -1 (last day of the week), and -2 (last day but one of the week) are permitted.
-
Specify in which month to run the schedule. The values 1 to 12 are permitted. If the value is empty, the schedule is run each month. |
|
Start time |
Fixed start time Enter the time in local format for the chosen time zone. If there is a list of start times, the schedule is started at each of the given times. |
|
Repeat every |
Rate of occurrence for running the schedule within the selected time interval. |
|
Last planned run/Next planned run |
Activation time calculated by the DBQueue Processor. Activation times are recalculated whilst the schedule is running. The time of the next run is calculated from the interval type, rate of occurrence, and the start time.
NOTE: One Identity Manager provides the start information in the time zone of the client where the program was started. Changes due to daylight saving are taken into account. |
Related topics
The DBQueue Processor performs starts and checks schedules at regular intervals. First, all schedules are found that are enabled and within the valid time period. A task is queued in the DBQueue for each schedule to be run. Then the time for the next scheduled run is calculated and entered in the schedule.
For tasks with the Every minute and Hourly interval types, the next planned activation time will be determined from the time at which the schedule runs, how often it runs, and the specified time zone. For schedules with the interval types Daily, Weekly, Monthly and Yearly, the next planned activation time will be determined from the current day, the specified subinterval and the start time within the specified time zone.
Behavior of new schedules
When a new active schedule is added, the next scheduled run is calculated immediately. This is calculated on the basis on the start date or the current date of the next scheduled run. The time between runs is not taken into account.
The task is run if the activation time has been reached. When the next scheduled run is calculated, this time the interval will be taken into account.
Behavior of modified schedules
If a schedule changes, the next scheduled run is calculated immediately. This is calculated on the basis on the start date or the current date of the next scheduled run. The time between runs is not taken into account.
The task is run if the activation time has been reached. When the next scheduled run is calculated, this time the interval will be taken into account.
Some calculation tasks for the database are scheduled. There are schedules set up for these maintenance tasks, which you can customize as required. It is recommended to run maintenance task outside main working hours of the connected clients.
Table 17: Maintenance tasks for the database
|
Reduce size of change entries |
Reduce logs |
Daily |
|
Reduce size of process tracking logs |
Reduce logs |
Daily |
|
Purge dynamic users |
Reduce logs |
Daily |
|
Reduce size of process log entries |
Reduce logs |
Daily |
|
Reduce size of process history |
Reduce logs |
Daily |
|
Populate calendar |
Daily maintenance tasks |
Daily |
|
Lock table statistics |
Daily maintenance tasks |
Daily |
|
Calculate table statistics |
Daily maintenance tasks |
Daily |
|
Rebuild table index
NOTE: Reindexing of tables does not take place anymore if they are larger than 1 GB or have more than 1 million data records. Maintenance of these tables must be performed by the database administrator within maintenance periods. |
Daily maintenance tasks
|
Daily |
|
Delete closed cases in the IT Shop |
Daily maintenance tasks |
Daily |
|
Clean up DBQueue Processor buffer |
Daily maintenance tasks |
Daily |
|
Calculate statistics for data contents |
Weekly maintenance tasks |
Weekly |
|
Set RowLock |
Weekly maintenance tasks |
Weekly |
|
Recalculate implementation plans () |
Recompile all implementation plans |
Daily |
Related topics
One Identity Manager provides the means to send email notifications. For example, notifications can be sent from process handling, about attestation or the status of IT Shop requests.
You use mail templates to design the appearance and content of email notifications. A mail template consists of general main data such as target format, important, or mail notification confidentiality and one or more mail definitions. The mail text is defined in several languages in the mail template. The recipient's language preferences are taken into account when an email notification is generated.
Create and edit mail templates in the Designer or in the Manager. The Designer displays all mail templates of the system. You can edit individual mail templates such as mail templates for requests in IT Shop or mail templates for attestation in the Manager. For more information about editing mail templates in the Manager, refer to the administration guides for the modules.
A Designer is integrated in the Manager and in the Mail Template Editor to simplify writing notifications. In the Mail Template Editor you can create email texts with Microsoft Word style editing and formatting functions and a preview of the email.
Email notifications are generated through default processes during process handling. To use email notifications based on mail templates for other business procedures, for example creating user accounts, you have to create custom mail templates and processes. Use the MailComponent process component to provide the SendRichMail process task for this purpose.
Related topics
