Hey there,

This can be done using SDK script. The code is long and the rules are many... I've done this for a customer already.

Rather than check the full name, document names can have the entry ID in them when exported:

Contract - Oil Rig Project {12312}.docx

In our solution, the customer drops the document into a personal folder monitored by Import Agent. Workflow picks up the document and adds the document as the next version (in the example above, of a document with entry id 12312).

There are a couple of gotcha's though:

• Auditing the event. The version will be added by the workflow account.
• To attempt to give some meaningful audit trail information, workflow picks up the name of the monitored folder and inserts that into the version comments. As the monitored folders are personal, it's named after the user who has access to it
• Given that the name of the folder is the only real audit trail, the folder must be accessible by only one user. IT have a script that creates personal and secured network folders, so all OK.
• Finally, the process has potential to be require a lot of recourses on the workflow server. If you consider that most activities can milliseconds then the 5 to 30 seconds it takes to import a version is something worth monitoring any given environment.
• Handling exceptions, such as documents in use etc are messy. This script was provided as an addition to a solution and is not the main focus of the solution. It's for ad-hoc version control. "Users who regularly work with electronic documents must use full licenses not this method," was my caveat to the customer.

-Ben