topic Re: Change versioning behaviour in Alfresco Forum https://connect.hyland.com/t5/alfresco-forum/change-versioning-behaviour/m-p/36017#M15190 <HTML><HEAD></HEAD><BODY><P>Unfortunately, about the only thing you can easily change is how versioning is applied to regular property updates and changes via version-unaware operations, e.g. if you simply execute an action on a document that changes its metadata, or use the WebDAV protocol to rename a file. The aspect cm:versionable primarily governs the auto-versioning behaviour. Now "Edit with Microsoft Office" unfortunately comes with inheren versioning as part of its core operations, that cannot be modified / configured. This is due to that interaction having to be compatible with the SharePoint default behaviour, which Office client applications expect.</P><P></P><P>What some of my customers do is simply delete the history of minor versions whnever it is getting to long, e.g. clearing out all but the latest 5 minor versions. This can be done via a scheduled job or a policy that reacts on new versions being created. This is an approach that requires custom Java code to be written and registered with the Repository.</P></BODY></HTML> Thu, 06 Apr 2017 17:51:13 GMT afaust 2017-04-06T17:51:13Z Change versioning behaviour https://connect.hyland.com/t5/alfresco-forum/change-versioning-behaviour/m-p/36016#M15189 Hello,I have a question on how to change the default versioning behaviour of Alfresco.Our documents go through a simple review process: a user creates or modifies a document, and requests another user to review and approve the document. As we would like keep track of the approved versions of a docum Thu, 06 Apr 2017 12:51:37 GMT https://connect.hyland.com/t5/alfresco-forum/change-versioning-behaviour/m-p/36016#M15189 pkhazzaka 2017-04-06T12:51:37Z Re: Change versioning behaviour https://connect.hyland.com/t5/alfresco-forum/change-versioning-behaviour/m-p/36017#M15190 <HTML><HEAD></HEAD><BODY><P>Unfortunately, about the only thing you can easily change is how versioning is applied to regular property updates and changes via version-unaware operations, e.g. if you simply execute an action on a document that changes its metadata, or use the WebDAV protocol to rename a file. The aspect cm:versionable primarily governs the auto-versioning behaviour. Now "Edit with Microsoft Office" unfortunately comes with inheren versioning as part of its core operations, that cannot be modified / configured. This is due to that interaction having to be compatible with the SharePoint default behaviour, which Office client applications expect.</P><P></P><P>What some of my customers do is simply delete the history of minor versions whnever it is getting to long, e.g. clearing out all but the latest 5 minor versions. This can be done via a scheduled job or a policy that reacts on new versions being created. This is an approach that requires custom Java code to be written and registered with the Repository.</P></BODY></HTML> Thu, 06 Apr 2017 17:51:13 GMT https://connect.hyland.com/t5/alfresco-forum/change-versioning-behaviour/m-p/36017#M15190 afaust 2017-04-06T17:51:13Z