You are viewing limited content. For full access, please sign in.

Question

Question

What LF tables do I link together to get the results of how many pages and documents are going per day and month on each repository? Please let me know. Thanks JET

asked on June 24, 2014

What LF tables do I link together to get the results of how many pages and documents are going per day and month  on each repository?   Please let me know.  Thanks JET

0 0

Replies

replied on June 24, 2014

Hi Jet,

 

It sounds like you might be making things a bit more difficult than they need to be!  Using Laserfiche Audit Trail, you should be able to keep tabs on how many pages/documents are being worked with in any repository.  Audit Trail uses a convenient wizard to configure everything, so you won't have to do any table linking or database work.

 

If I haven't answered your question, or Audit Trail won't work for some reason, just let us know a bit more about what you're trying to accomplish, and why Audit Trail isn't the solution.  Thanks!

0 0
replied on June 24, 2014

Hi Brett,

 

First of all, thanks.   How do you configure the date settings or date range in the report data of audit trail ==> entering a value date --(e.g. User "A"  would like a report for just one day, while User "B" would like a report for the period of 05/01/2014 through 05/31/2014)?    Let me know.Thanks!

0 0
replied on June 24, 2014

Check out the Admin Guide section on Audit Trail. It has information on the reporting capabilities included with Laserfiche. If that report generator doesn't meet your needs, you can look at the audit database schema and write your own reports, for example using SQL Server Reporting Services. Any application that can access the audit database can use the information stored there to generate reports.

0 0
replied on June 24, 2014 Show version history

Just as a note of caution. Think carefully about how much data you tell Audit Trail to extract. The reporting database can get quite big if you aren't careful.

 

Edit: As a second thought, if you need stats over a longer term, you could build a query that periodically gets you a snapshot and then store that in a different database. You can have a relatively short window of data, but you snapshot just the aggregated results you are interested in on a daily (or whatever you need) basis at a much lower storage cost.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.