I am currently working on improvements in set of document types following working copy/published version concept. We have implemented our version of this concept using managed properties and creation of pdf documents on runtime that are then linked with working copies through managed properties (we haven't had enterprise license and haven't had full compliance kit in place). Our solution works well but I would rather use version control light as it provides the same feature and is more robust solution (also less code to maintain).
On the other side, we have our own migration tool developed during the time (I know about M-Files Importer but we haven't had resources to buy it, bottom line we would like to re-use our tool). Our migration tool takes excel sheet with metadata (simple + more complex metadata mapped into object types and value lists) together with working copies (words) and published version (pdfs) and import those documents through M-Files REST-based API. The concept based on managed properties then automatically link documents and populate link metadata. So it works quite well.
I have adapted our solution to use version control light and it looks very nice, less code, configurable, many benefits. Unfortunately, I see potential problem with our migration tool: how could I upload our working copy and published version and use VCL to link both documents? As I see, VCL enters linking metadata dynamically in configured workflow state. Also VCL is creating published version automatically. I need to bring my published version (our requirement). Is this possible with VCL?
What are your thoughts about this? Would M-Files Importer be able to migrate both working copy/published version and link it over VCL?