This is a public Idea Center  publicRSS

Idea

    48 liked this

    [Under Consideration] Audit log does not provide enough...
    Idea posted June 7, 2013 by Ronald HilemanWhiz, last edited July 31, 2015 by Vimal ChopraApprentice, tagged Agent Desktop, Reporting, System Admin and Configuration 
    754 Views, 25 Comments
    Title:
    [Under Consideration] Audit log does not provide enough Details
    User Story / Description:

    We would like to be able to see what field(s) were edited and possibly the before and after values of these fields when an incident is edited.  Currently, we only have the message, "Edit"   and "Edited from : Incident Editor".

    The transactions table only has queue and status information in the attributes.

     

    We would like to know what field(s) were actually edited/modified.

    Thanks.

    Comment

    • Baxter

      I'd certainly like to see the transactions audit log reporting extended to cover edits to Mailbox, Disposition, Product, Category and also the incident's Contact.

      The ability to report on these would help us a lot in troubleshooting the cause of "bad data" - incorrect values selected - as we'd be able to see if the incorrect value was set by an agent not following best practice or by a mistake in business or workspace rules.

    • Colby Ross

      This would be a great add to the system!

    • Stephen Pickett

      Can we get an update on this please? It will be critical for proper implementation of GDPR from May 2018 onwards which is basically mandatory to all organisations - that's ALL of your customers and partners that will be needing this, and as previously mentioned your competitors are already doing this so it will be even more challenging for us to position Oracle Service Cloud above them!

    • Kincaid

      Agreed, more information is almost always better...but field tracking needs vary from biz to biz.

      Understanding that tracking additional details at the user/ticket transactions level may add heft to the db...it may also be worth considering to give admin's & architects the power to choose/config which incident field updates to track at that audit-able level of granularity....be they out of box standard fields (like queue & status), custom fields and/or incident attrs.

      -k

    • santhosh xavier

      Any update on this?

    • Stephen Pickett

      Chasing an update...

    • Stephen Pickett

      Can someone update us on this please? We are in the throes of preparing for GDPR and need to know what is happening with this.

    • Stephen Pickett

      Chasing an update again. Please can someone escalate this to senior management, this is critical.

    • eileen neulinger

      We would also like to have the attachment activity recorded in the log as to what user attached the file.

    • Pramod Vasudeva Murthy

      Need this enabled in next release, please.

      ~VIP