It came to our attention that version 1 of an object "document" is already visible (and usable) in a valuelist property which selects from documents. Even though the version has not been checked-in yet.
The main issue occurs whenever you have the compliance kit configured which updates the metadatacard of (related) objects with the managed properties module.
For some reason Version 1 (or let's say "version 0" - since it hasn't been checked in before) can already be selected and whenever the compliance kit tries to (re)calculate it gives (the perhaps well known) error message: "Matching pairs".
The discussion is as followed: should this document be in the list and why - what are we missing? Because it feels like some sort of bug since in our opinion this version should never be in the list (?) before checked in once?
The question has been raised via MF support and an improvement ID has been created (ID: 171475). But I'd very much like to hear suggestions from other customers/clients who have might experienced the same.
Any thoughts on this one?
