Thanks for posting to the Ivanti Community!
Sorry that it seems no one has the answer to be able to assist you on this yet. Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.
If not then please do consider the other ways to engage with us to get assistance:
Add depends on how far you wish to take knowledge and revisions. It is possible to create some rather complex knowledge re-versioning using quick actions and workflows to clone the existing article increase the version number and then push through and approval process. Once the approval is gained the old article can be archived automatically. You will need a new relationship to be created between the old and new versions ideally, thinking about it you could have a version tab which lists the old versions and links directly to them.
OOTB the knowledge number is generated from a counter, the field in my database is set to unique at the FRS_Knowledge object level. It comes from a counter using the $(GetNextCounter()) function.
The version field is just a manual field to use but as I mentioned above could be automated.