cancel
Showing results for 
Search instead for 
Did you mean: 

versioning policy

Eric_Ace
Confirmed Champ
Confirmed Champ

I'm trying to implement a default versioning policy as follows:

  1. On initial document creation - set the version to 1.0
  2. Thereafter - increment the minor version number (1.1, 1.2, ...)

I have tried various combinations of:

...
<policy id="test" increment="MINOR" order="11">
    <initialState major="1" minor="0" />
</policy>
...

I've tried before/after, multiple policies, etc. Looking at the Framework code - it looks like what I'm trying to do isn't supported because of how the policies are applied before and after. I'm therefore planning to implement this with a filter class but it seemed better - if possible - to do it just with a contribution. If I'm missing something, guidance is appreciated. Thanks.

4 REPLIES 4

Kevin_Leturc
Star Contributor
Star Contributor

Hi Eric,

Your example looks good and should work to initialize the versioning state to 1.0 and then increment by minor after every update (if and only if document has dirty properties). What does not work in your case ?

Thank you. After initial document creation the version is always "1.1". Here's what I see

Hi,

I see. Thank you for responding. This gives me what I need. Thanks.

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.