Hi folks,
EV 12.x is proud of the fact that you can now specify a zero-day retention. Somehow it escapes me in what situation to use it because I interpret that to mean that the archived item is deleted with the first expiry run after it's been archived? I haven't found an explanation anywhere.
Please enlighten me
Regards, Bert
Interesting question.
I can see usage in combination with using Classification. If you classify items during archiving, especially using Journal Archiving, you might be able to filter the 'crap' messages and give those a 0-day retention policy. Think 'best deal', birthday announcements/wishes, items marked as private perhaps.
I can't see direct benefit, but I am sure there is one (or two) :-)
Hi Gertjan,
thanks for the reply; Classification is a good point, but to my knowledge you can use the tag action "Delete from archive (evaction.discard)" for that purpose. It marks the item for deletion.
Any thoughts from Veritas?
regards, Bert
This took a bit of digging, but it looks like this is meant to be most useful in conjunction with the RetentionStartDate property of an item.
In the VAC, you can choose to have a Retention Category start counting from the Modified Date or the Archived Date, but if you're manipulating an individual item with the Content Management API (either inserting or updating), you can also set a RetentionStartDate from which that item's "retention clock" starts ticking. I think the idea is that a partner using the API could set a zero-day Retention Category and also set an item's RetentionStartDate to a day in the future, and therefore can specify the exact date on which the item shall expire. This mirrors the behavior of the "Fixed expiry date" option that's in the Retention Category Properties, except that it can be assigned to an individual item.
This was one of a complement of Retention and Records Management features introduced in EV 12.2 that cater to U.S. government customers operating under National Archives and Records Authority (NARA) regulations.
--Chris
