You can use the following fields to define or edit rule definitions.
Specifies a unique identifier for the rule.
Indicates whether this rule is active. The inactive rule runs only once, even if it is scheduled for a recurrent process.
Specifies a workshift during which the rule should be in effect.
Specifies how often this rule will run.
Specifies the name of the file where you want to store the historic records. Enter the file name that you have mentioned while defining the archive and purge path. For more information, see the Define the Archive and Purge Path topic.
Specifies one of the following types of operation that the rule must execute:
Archives the historic records to a file and purges the archived records from the database.
Purges historic records from the database, but they are not written to the archive file.
Writes historic records to the archive file without purging them from the database. Use this option to test a newly created or edited archive and purge rule.
Specifies the name of the database object this rule can archive and purge. The Object Name field is automatically populated according to your selection in the Config. Object Name field.
Specifies the number of days a record is inactive to be eligible for the archive and purge from the database.
Archives and purges specific inactive records among the existing inactive records. Use this field when you want to create different rules for archiving and purging the subsets of expired records for the same object. Use the same syntax as you use for stored queries.
The following query archives and purges only assigned inactive request records with a priority of 1:
priority = 1 AND (assignee IS NOT NULL OR group IS NOT NULL) and active = 0
The following query format archives and purges records based on time-span:
close_date < EndAtTime(\'LAST_YEAR\')
| Copyright © 2013 CA.
|
Tell Technical Publications how we can improve this information |