I posted this to the Higher Ed special interest group but am adding it here in case others have helpful feedback.
While reading Vancouver release notes, I learned there are now default archive and destroy rules for "variable data of standard catalog items, record producers, and catalog task tables". The rules are inactive by default. I can see how it would be necessary to archive/destroy old records to maintain reasonable performance levels but we use some catalog items for forms, some of which must legally be kept for seven years.
Do other organizations use the service catalog this way? If so, have you developed policies for when to archive and when to destroy old tickets? Do you move printer-friendly PDF copies to a document storage app to comply with legal requirements? Is reporting an issue?
Has anyone experienced delays in performance because they haven't archived/destroyed old data? When did you start noticing it? (I'm trying to get a rough idea of how long we have to work this out, though that probably depends more on the size of the variables tables than on the number of years worth of data or the number of tickets.)
Thanks in advance for any feedback.
