Server events is VERY useful if you extend it. One of the consultants that came to my job had a tool that he built for his own personal use that was insanely useful. It fires on submit into server events, and creates a copy in another table, you then build a translator table that takes your event codes and converts them to human readable events. What this gives us is every modification to the system (that's turned on in the server events tab) is logged with what was done (create, set, delete, etc) by who, and on what object.
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of John Sundberg Sent: Tuesday, March 25, 2008 7:23 AM To: arslist@ARSLIST.ORG Subject: Remedy server events table ** The "server events" table seems like it has good potential. Every once in awhile I see a comment like "you can see when filters were created using server events and then ....." -- but as I look at the table -- it does not seem as you could do much with it. So -- are people using it - and how do you use it? How have you extended it. Thanks -- just looking for some insight/brainstorming. Thanks, -John -- John David Sundberg 235 East 6th Street, Suite 400B St. Paul, MN 55101 (651) 556-0930-work (651) 247-6766-cell (651) 695-8577-fax [EMAIL PROTECTED] __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
