Before we start to discuss Audit Trails and the complexities you might want to note that from what I know the information that is collected is pretty taxing on the system resources and in addition these audit trails could not affect you and your team, but other users in the system as well. One of the key question I would want to know about is - what is that you are looking for by attempting to track user details like this at a detail level such as you have explained above. If you are looking for 'who did what' and 'when was it done' there might be simpler ways of getting there with a little less overhead on the system. Now if you have a 'forensic' issue that you are trying to address - such as some is wrong and we need to figure out what is happening - and only for a short while - then I think Audit might work for you. If you are looking for something more long term, more than just your department and your shift centered, then you might consider looking at some external tools that would do as good or better job of gathering data and presenting the data in a useable format. We have been looking for a solution for some time to allow some of our government clients to 'audit' what is happening, and they even find that Audit is not the solution for them - but - have faith, we will find them something. Keep posting and learning - this is a good support community and one that is built on users like you that want to learn and who are willing to work to learn.
↧