Could there be version/iteration control on CNs/variances. It is a bit confusing to users where if you searched for a change object or even looked within the product's changes folders, you would see the change object's version (ex, 1.1, 2.1). Yet within the actual change object there is no iteration. If version/iteration control is not offered on change objects, why do you display it as a Version on searches and folders?
What we were looking is the ability to iterate change objects (CN123456 Rev 1.1, Rev 1.2, Rev 1.3, etc.). Our users are concerned about the after submission and during routed approvals of change objects (but not yet approved) where changes may have to go back to rework (due to reviewers/customers comments). The customer states they can't really tell what changed since the CN doesn't iterate. They want some way to distinguish that there have been updates to the change object. Yes you can put comments on the object that you updated it but if you were to resubmit the CN (for example) to the customer there is no indication on the CN or its history that it has been modified/updated. (For example on documents, during the review cycle, when you add attachments and make changes the document iterates until such time that you release it (Doc 123456 Rev A.1, A.2, A.3). Once it is released, you would then revise the document. (Doc 123456 Rev B.1)). Our users/customers would like the same concept for change objects (CN123456 Rev 1.1, 1.2, 1.3) and then once it is approved you would revise the change object (CN123456 Rev 2.1).
Hopefully it could be flexible enough that if some of your customers want to keep things as they are (Revisions only) there would be a preference to do that.