The generation of the list of elements created in a directory is simply the default comment that goes with the checkin. To change this behavior, when a directory is checked in, the user just needs to provide a different checkin comment.
I mentioned that to the developers that one could simply provide a different (shorter) checkin comment but even the checkin process is scripted. There is such a big push to automate everything. Thus, the checkin is done by a script and not by a user. See my dilemma? Thus, they are pushing to see if the "default" can be changed to nothing in the comment.
I do see your dilemma. I would think you have two options. (1) have them change their script so that if the script is checking in a directory, that the script add a comment during the checkin, or (2) create a ClearCase trigger, set for postop checkin, that would test to see if the checked in element is a directory, and if it is a directory, run the command 'cleartool setevent' and change the checkin comment of the directory. I would think option #1 would be the easiest, but option #2 will work just as well.
Thanks for the idea. I also heard the idea of a preop checkin trigger.