Non Unique Version number

To ensure validity and correct versioning of documents we need check-out/in with non unique version numbers. This has been made impossible with release 44. 

We'd like to reuse a previously given version number for minor changes, especially on meta data. 



1 comment
  • Hello Peter,

    Thank you for your post. I would advise you to use a string instead of an integer because with the incoming release V45 of AODocs you will be able to customize the version name with custom script. In this way, you can programmatically control the way the version numbers are used and displayed. 

    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post