AutoIt. Create mapkeys to handle most of the changes and then use AutoIt to open files, run the mapkeys, and save and close. Mapkeys because AutoIt is asynchronous and it is tricky to monitor exactly what Creo is doing from moment to moment, but is capable of monitoring significant changes easily.
Reason to like it - capable of much greater flexibility because it is a programming language, rather than a pre-recording. No need to pick through the trail files.
Reason not to - aside from IT policies, only works with the graphics operating version. Trail files will work with or without graphics. Because of its interaction with graphics, it can be a mouse hog, though it can also play very nicely if correctly written.
