CM System 7.2 introduced Revision purge for all content items.
We’re looking for the following enhancements:
[ul]
[li]Specify a jcr:path or rx:sys_contentid to purge revisions[/li][li]Recursive setting for jcr:path[/li][li]“Dry run” that displays each impacted content item and number of matched revisions to be purged[/li][/ul]
I like the third enhancement. For us, it would be more useful tool if we could specify a content type (or multiple) that we could remove the revisions of. (ie. say we want all file content types to only hold 2 revisions, but all other content types to have an unlimited number…)
[QUOTE=jitendra;20309]I like the third enhancement. For us, it would be more useful tool if we could specify a content type (or multiple) that we could remove the revisions of. (ie. say we want all file content types to only hold 2 revisions, but all other content types to have an unlimited number…)[/QUOTE] +1 Specify content type(s) for content item matching criteria.
Also, do you think we should have an extension (item post-processing or workflow action) that checks the number of public revisions for the content item upon transitioning to public, and if the number of revisions is greater than the specified parameter then purge?