Making Use of the Audit Log

Thanks for implementing the audit log. I'm wondering, though, how exactly do we utilize the internal table ID for logged events? Is it possible to use that ID to see more in depth audit details than is provided in the log itself?

0

Comments

9 comments
  • The only ID#s that are useful would be Invoices and Payments, and you could then use the Find Transaction window to locate those transactions.

    0
    Comment actions Permalink
  • What about adjustments to punches or time clock? Along the same line as the Customer Change History window, is it possible to see side by side diff between the Old Value with the New Value?

    0
    Comment actions Permalink
  • Nope, and that will not be possible.

    As I recall, in both punches and time clock the individual whose record was modified is shown in the text description thus it should be plenty of information to locate the issue.

    The audit log is NOT meant to allow you to review every thing that happened in detail, but more to allow you to see a pattern of abuse by a particular employee.

    0
    Comment actions Permalink
  • So, does that mean the Old Value is completely purged?

    0
    Comment actions Permalink
  • Yes.

    0
    Comment actions Permalink
  • We've noticed a small issue with our Audit trail. When looking at stock adjustments and a few other reports some of the trails have not got a member of staff against them. These are for processes which require entry of a PIN on RGP. Is this by design?

    0
    Comment actions Permalink
  • Are these recent entries? If a staff member gets deleted, the entry will become blank.

    0
    Comment actions Permalink
  • Thanks for the prompt response! We did consider this, but we have had no changes to the management team within the last year and the blank entries run throughout 2015. As we understand it only PIN's/Employees with a permissions level of Manager or higher can make changes to stock levels and we have only had changes to the staff team.

    0
    Comment actions Permalink
  • Honestly, I'm not sure as I've never had anyone report this before. If I had to guess, it's because whomever was "logged in" during that time had their session logout for some reason... probably because they went away from the computer for a long time but left the Product Management window open. Without it being repeatable, it is unfortunately difficult to diagnose. If you can repeat it, it would be appreciated.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post