Deleted.
Solved! Go to Solution.
It is unfortunate that this can only be set globally while the autoVersionOnUpdateProps can be set on a node-level. though that might significantly increase size of DB if setting a large list of properties.
As long as you have a consistent list of "excludedOnUpdateProps" for your entire system, that approach is ideal. If fine-grained control is needed I think the option to setup a custom versioning behaviour might be more appropriate, e.g. for different types of nodes. In that case I would disable autoVersionOnUpdateProps and use a custom behaviour to create a version via Version2Service (after checking the property changes for relevant ones).
Hi,
Please refer to Versioning Behaviour
If you scroll to the end of the page, you will see the ability to override the "versionableAspect" to exclude specific properties (via "excludedOnUpdateProps").
Regards,
Jan
It is unfortunate that this can only be set globally while the autoVersionOnUpdateProps can be set on a node-level. though that might significantly increase size of DB if setting a large list of properties.
As long as you have a consistent list of "excludedOnUpdateProps" for your entire system, that approach is ideal. If fine-grained control is needed I think the option to setup a custom versioning behaviour might be more appropriate, e.g. for different types of nodes. In that case I would disable autoVersionOnUpdateProps and use a custom behaviour to create a version via Version2Service (after checking the property changes for relevant ones).
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.