Description of problem:

Customers want to associate multiple content views where Composite Content View fits.

But the versioning of the content views within and the content view of the Composite have to be manually updated before being published.

Customer wants to remove this restriction.  By design this manual version control was put in place to validate that things were tested appropriately before full updates.

Composite CV     (has own version)
   CV1:APP_TEAM1 (has own version)
   CV2:APP_TEAM2 (has own version)

If you used the example below

Lifecycle Environments

freefall_dev--->publish_dev--->qa---->prod

So inside the freefall_dev you could automate version update/publish for the Composite Content Views in some scheduled fashion and then promote as to the publish_dev.


Version-Release number of selected component (if applicable):

Current 6.0.3


How reproducible:


See description above.

Basically create a composite view like described above and update the content view, you can't publish until version is updated manually, and you can't promote until it's published.

Expected results:

Allow control over version update/publish/promote policies via scheduling like sync.

It could be point in time or automatic on update.

Additional info:

To workaround this...

We discussed ways of having a cron job to have a nightly mechanism to publish/promote from say a freefall_dev env to dev env.