Expand my Community achievements bar.

The need for Version history by path


Level 1

I am involved with a project where AEM environment hosts content and related content applications for different business units across the organization. These business units, being responsible for different content types, have varied requirements for how many versions to keep in history. There is one business unit that needs 10 – 15 versions but other business units do not these many. If we increase the number of versions to keep in the version history (Day CQ WCM Version Purge Task) configuration, then it would result lot of unwanted versions being created and disk space being heavily utilized. I was thinking that it would be good idea to have flexibility that allows this configuration per content path (or paths), this will be relevant for the case mentioned. I actually think this may be necessary for organizations that have shared AEM infrastructure across multiple varied business units to ensure optimized disk space utilization.

Do you think this can be taken as feature enhancement?

1 Reply


Employee Advisor

I think that's a very good feature request :-) Can you please raise it via the usual support channels?