I've just installed and used this app. WAY better than my updates to Trigger Happy.



I found a couple of things that I needed to change.



Fixes:

Config db - form Trigger - global code - Install Agent

The code that deletes the agent failed with the error 'can't remove an agent belong to another user. I replaced the code with code found at:

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/a0f70fa9c9ce55a0852572ab00677aaa?OpenDocument&Highlight=0,agent,remove



Also fixed LS_AuditManager CreateLogDatabase to pull in the server name from the Trigger document so that the title of the log db can be properly set. The code used a value that was never set (eg had a variable for 'Server' that was null).



Improvement

Linking an audit log to a specific Notes doc using the doc ID is rather painful. I've added a field to every doc I intend to audit that I call 'HumanFriendlyID'. It's a text field that provides a clear human understandable reference to a specific document. For example, if I have a db that creates some kind of sequential key, I'll use that. For other dbs, I may concatenanate multiple fields into a string that has meaning. I added a sub to the Logger class to load in this value if it exists or 'Friendly ID not present' if the field isn't on a form.





One other interesting thing I ran across is the implementation of this in a template driven environment. AM is designed to push the agent into a defined production db. If that db is based on a template, the design refresh process removes the agent. I'm going to manually install the agent into the template and leave it connected to the AM Config template, then let design refresh push it to the production, and then set up triggers. If the agent is modified in the AM Config template, it'll propogate to the templates using it and then into the production dbs.

I was going to disable the code that handle installing the agent but left it in place to handle the case where I need to push AM into a non-templated db.