Maintaining Revision Levels
By Kyle Hatlestad on Mar 30, 2010
A question that came up on an earlier blog post was how to limit the number of revisions on a piece of content. UCM does not inherently enforce any sort of limit on how many revisions you can have. It's unlimited.
In some cases, there may be content that goes through lots of changes, but there just simply isn't a need to keep all of its revisions around. Deleting those revisions through the content information screen can be very cumbersome. And going through the Repository Manager applet can take time as well to filter and find the revisions to get rid of.
Running that export in Archiver is normally a manual process. But with Idc Command, you can script the process and have it run automatically from the server. Idc Command is a utility that allows you to run any of the content server services via the command line. You basically feed it a text file with the services and parameters defined along with the user to run it as. The Idc Command executable is located within the
$ ./IdcCommand -f DeleteOlderRevisions.txt -u sysadmin -l delete_revisions.log
In this example, our IdcCommand file to run the export and do the deletions would look like:
You can then use automated scheduling routines in the OS to run the command and command file at the frequency needed.
Remember that you are deleting the revisions from within UCM, but they are still getting placed within the archive. So you will need to delete those batches to have them fully removed (or re-import if you need to recover them).
For more information about Idc Command, you can find that in the Idc Command Reference Guide.