Thanks,
Mike
More troubling news. I have a dispatch that I wanted to fire on check in that would launch an external program that made changes to the file and save the changes before the file was actually checked in so the changes would automatically be applied to the file. No such luck. I guess I will have to write an add-in to do it.
I see what you mean Lee about it being flaky. It all has to do with what Joy said about which even gets fired, "Pre Undo Lock+ or "Pre Unlock". I still have not figured out the logic to when one or the other event gets fired. I did get lucky in that it works for my particular application.
My application is for an XML ECN/ECO form. I use a template to create the xml file, so the creation of the file is consistent. The user either fills out the form via the data card and attaches affected files to the xml document on the creation of the xml file or they can check out the file and make changes and or attach additional files or remove files, then check the file in.The application monitors the "Pre Unlock" event, get's the fileID, folderID, and fileName or all the files attached to the ECN/ECO xml file and adds them as elements and attributes to the xml file. In all the testing I done it works for my xml file.
I also tested other file extensions and different methods of adding the files to the vault. In some cases a "Pre Undo Lock" event would get fired where it looked to me like version tab of the file looked identical to the version tab of the xml file, ie version 1/1.
A shamless plug, this appliction is for an "Automating ECx Process' that I am doing at World this year.