Question

Audit Reports - tracking history of one entry

Version 9 Laserfiche Audit Trail

Updated March 26, 2015

asked on March 26, 2015

I am trying to get the history of one document using the Audit Reporting feature, but I'm getting nothing. Can anyone tell me what I'm missing in the report set-up? I know Entry ID 77389 was created Jan 6/15 and a template was added, and it was then moved to a specific folder. At least those 3 actions should be showing up in the results, shouldn't they?

0 0

Replies

replied on March 26, 2015

Hi Connie,

Please confirm that the proper audit event classes for the users, groups and/or Everyone has been set. For the user who was supposed to have created the entry or modified the field values for the entry, go into the Laserfiche Administration Console and view the properties for that user. Under the "Auditing" tab, confirm what event classes are selected. If it's set to "Group membership" then you can click on the "Audit Events..." button to see the effective audited events.

Regards

0 0

replied on March 26, 2015

0 0

replied on March 26, 2015

Connie,

Please also note to load the Audit logs under the configuration that would fall on those dates. If the audit logs for those dates are not loaded then you will no be able to bring up the data for those logs that fall on those dates. In order to do this go under the configuration of Audit Trail and go to date ranges.

0 0

replied on March 26, 2015

So, does this mean it is keeping only the last 30 days of data and dumping anything older? This must be why I've seen info that indicates people are regularly copying audit reports to another safe location. (?) What is recommended? I want to be able to go back and track who accessed any given document over a period of a year or two and what they did. That's what I was trying to learn to do (to make sure I could do it, before we have a case where I actually have to present this type of audit report).

Thx, Connie

0 0

replied on March 26, 2015 • Show version history

In order to report on audit data, the logs have to be loaded into a SQL database. Having the entire history of your repository loaded is typically not an option due to the sheer amount of data, so you tell AT what data you are interested in.

If you're not familiar with administering AT, the documentation can be helpful - this page talks about specifying date ranges.

0 0

You are not allowed to follow up in this post.

Question

Question

Audit Reports - tracking history of one entry

Replies

Sign in to reply to this post.