iDM uses lots of classes - whenever we create a new transaction, we have to populate three classes.

Well, this gets tedious after a while, so I just wrote a form in a discussion database that takes the transaction name and members, and churns out the three classes. Saved me about 10 days on the current development work. How does the form work ? Straightforward formula language to construct each class type in a form.

The moral of the tale. Use the simplest technology available to automate more mundane matters. Works every time. Oh - and never try to get it working exactly - the 80%/20% rule is sufficent (especially for an internal-only tool)