From what I can tell, presently what's available through the PDMWorks API (BTW Advanced Server is required in order to use it) is insufficient to pull off the type of automation routine you're talking about. I've spent some time looking into doing something similar to this recently and found that the PDMWorks API is still immature right now. It seems to be mostly setup for reporting and such and does not have much in the way of exposed methods, etc. from what I've seen.
However, I will share with you what I think the algorithm to do what you're after ought to look like (in case I'm wrong and it is possible). Basically it should a macro/application that does the following:
[ul]
[li]Launches with the "checkin" event of PDMWorks[/li]
[li]Waits for the user to enter the notes[/li]
[li]Detects when the user completes their checkin routine (i.e. clicks "checkin"

*[/li]
[li]Suspends PDMWorks checkin routine actions*[/li]
[li]Fires a sequence of SW API commands (enters revision and note info in rev block, saves the drawing)[/li]
[li]Resume PDMWorks checkin routine actions*[/li]
[li]Exits allowing PDMWorks to complete checkin sequence[/li]
* The PDMWorks API doesn't appear to give us a way of doing this right now
[/ul]
So automationbabe is correct in that it really isn't a very complicated API but without being to give the application a way of "knowing" when a checkin occurs it's not currently feasible IMO. It's not an impractical request to make (ability to link PDMWorks and Revision table) either IMO. I imagine that the capability will be available at some point.
Chris Gervais
Sr. Mechanical Designer
Lytron Corp.