nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Help required to understand versioning

mike001

Hello,

I've been reading through the documentation to better understand versioning in Alfresco 4 but I can't work out what exactly gets versioned.

If I create a new version of a content item will the old version retain the values of all properties including those applied through aspects or is it only the actual document (i.e the word, xls, html file etc) that's versioned?

Many thanks,

Mike.

Find more posts tagged with

Comments

mrogers

It depends…

You can version both content and metadata. However by default "Share" only turns on versioning of content, and it also does "lazy" versioning.

bisana

Hi Mrogers
Thanks for the info
What will happen If Custom Type Properties or Custom Aspect properties applied on a document keeps on changing, is it possible for a version and rollback based on that versioning.

mrogers

Yes if you are versioning properties you can rollback to a previous version.

mike001

Thank you for your responses. My next question is how do I enable the versioning of properties? At the moment I've defined a custom content model with two custom optional aspects. The custom content model has the versioning aspect applied but when I pull back an old version through a CMIS client it doesn't seem to have the property values that I know were applied when it was the latest version.

Many thanks,

Mike.

mrogers

When you add the versionable aspect you set a property on the versionable aspect.

Can't quite remember the name but its something obvious like cm:auto version properties.

scouil

You can look at the definition of the aspect here:
<tomcat home>/webapps/alfresco/WEB-INF/classes/alfresco/model/contentModel.xml and search for "cm:versionable"

So I guess the property would be cm:autoVersionOnUpdateProps
On my Alfresco version, the default value is already true though…

kroser

If anyone can finish this thread and specify the final solution for turning on versioning of properties in the latest community version, I'd really appreciate it. I would hope there is something to change in a .properties file to do this.