General Page
Data Retention
The Data Retention section contains settings that determine how long some data is kept by adTempus.
Default History Retention
The Default History Retention option determines how long adTempus retains the history for jobs when the job's history retention option is set to "Use global default setting." History information is removed from adTempus once it is older than the retention period.
By default adTempus is configured to keep information on the most recent 30 executions of each job. If you change this option to retain history for a certain number of days, be sure to consider the effect on jobs that run frequently, and adjust the settings for those jobs to use a shorter retention period as appropriate.
For example, suppose you change the default retention to 60 days, and you have some jobs that run every 5 minutes. These jobs will generate 17,280 instances in a 60-day period. Having a such a large amount of history for many jobs can create performance and database size issues for adTempus depending on your database configuration.
Retain server messages (such as unacknowledged alerts) for __ days
Most messages in the adTempus message log are related to a particular job; these messages are purged from the database according to the history retention settings for the job.
Some messages are not related to any job; these are purged after the number of days you specify here.
Alerts that have not been acknowledged are not deleted even if they are older than the age limit.
Do not delete failed instances that have not been acknowledged
When this option is checked, adTempus will never remove failed job instances that have not been acknowledged, even if the retention period has expired for them. If it is not checked, such instances will be removed according to the retention rules.
Database Operation Task
Default timeout for Database Operation Task Commands
This value determines how long database operations executed by the Database Operation Task are allowed to execute. The default value is 20 minutes; increase this value for operations that require more time. The timeout applies only to select and update operations; database job execution is not subject to a time limit. Each task can be configured with its own timeout instead of the default on the General page of the Database Operation Task window.
Allow rich text for object descriptions, documentation, notes
5.0
This option determines whether rich text can be used in fields that store object descriptions, documentation, and notes (all multi-line, free-form text fields, such as the Description field in the Job Properties).
When rich text is enabled, users can use formatting as in word processing software. Four settings are available
- Not allowed. Rich text is not allowed, and only plain text can be used (as in adTempus 4 and earlier.
- Allowed (default to plain text). Rich text is allowed, but the fields use plain text by default. The user can switch to rich text by checking the Use rich text checkbox below the text field.
- Preferred (default to rich text). Rich text is allowed and the fields use rich text by default. The user can switch to plain text by unchecking the Use rich text checkbox below the text field.
- Required (always use rich text). The fields always use the rich text editor and the user cannot switch to plain text.
For most installations there is no reason not to use the Required setting to always use plain text. You may wish to continue using plain text for some or all fields if:
- You have developed templates or standards for these fields that use plain text
- You are using the API or database queries to retrieve descriptions for reporting or other purposes, and need them to be in plain text
If you have upgraded from adTempus 4 or earlier, rich text support is turned off by default to ensure backward compatibility.