The Archival Policy tab indicates how long the server archives a completed instance of a process or schedule object and contains the following fields:
Defines the minimum number of days that the system retains completed and failed instances of processes. The age of an instance is measured in hours. If an instance ends at 10:00 p.m. and you set this option to one day, the instance remains in the Library until 10:00 p.m. the following day.
Default: This input field defaults to 0.
Defines the minimum number of Failed instances of the Object (Process, Schedule, and SRF) that are retained. To view the retained instances of an object, select the Current filter of the respective object from the Operations dashboard.
The remaining objects are archived and to view the archived objects, select the Archived filter of the respective object from the Operations dashboard. When the Failed instances exceed the specified value in the field, the product archives the object instances with the oldest timestamp of completion.
However, the instances are archived only after they are retained for a minimum number of days as specified in the Minimum Days of Process History field.
Default: This input field defaults to 0. You can specify a positive integer value.
When 0 is specified, instances are archived but are not retained.
Defines the minimum number of Finished (completed and aborted) instances of the Object (Process, Schedule, and SRF) that are retained. To view the retained instances of an object, select the Current filter of the respective object from the Operations dashboard.
The remaining objects are archived and to view the archived objects, select the Archived filter of the respective object from the Operations dashboard. When the number of Finished (completed and aborted) instances exceed the specified value, the application archives the object instances with the oldest timestamp of completion.
However, the instances are archived only after they are retained for a minimum number of days as specified in the Minimum Days of Process History field.
Default value: 0. You can specify a positive integer value.
When 0 is specified, instances are archived but are not retained.
Enables you to inherit Archival Policy property settings for an object from the Orchestrator.
Default: Selected
Important: The above object level properties are applicable only if the Inherit archival policy from Orchestrator check box is cleared.
Important! If an object is deleted, then the archival policy for the object defaults to server level settings defined in the Configuration browser.
Note: In previous releases, you could not retrieve the archived instances to the current filter. In this release, if you increase the number to retained instances of Archival Policy (from 3 to 4 here), the instances that are archived in previous Archival Run are retained to the Current Filter.
Consider the following Archival Policy Settings at the Configuration Browser level:
Result after Archival Thread is executed. (after 12 minutes).
All the instances that are younger than three days are retained and the instances beyond three days are archived.
Now, change Policy at the Configuration Browser as follows:
Result after Archival Thread is executed (after 12 minutes). All the instances that are younger than four days are retained.
Instances that were earlier archived beyond three days (fourth day), are also now retrieved to the current filter.
The behavior of retrieving the archived instances to the current filter is applicable to the following Archival Parameter fields:
|
Copyright © 2014 CA.
All rights reserved.
|
|