Clarity

Expand all | Collapse all

Reporting on Audit Trail (BOXI?)

  • 1.  Reporting on Audit Trail (BOXI?)

    Posted 02-17-2015 11:20 AM

    Before I started building it out myself, figured I'd check to make sure I wasn't missing something obvious. Recently got a request to be able to provide metrics on a couple specific object attribute changes (specifically idea and project status changes). Seems the only way to do so would enable auditing on the two objects/attributes, and report based on the audit trail records. This is part of a larger report that is being built in BOXI so ideally I'd like to get to the data in there but I dont see the Audit Trail in the Universes, is it available buried somewhere I just haven't seen? Has anyone else done anything similar? Knowing that BOXI is going the way of the dodo for us I'm not looking forward to building this all out and having to redo it in a few months. Here's to hoping the audit trail will be in the new datamart for JasperSoft



  • 2.  Re: Reporting on Audit Trail (BOXI?)

    Posted 02-17-2015 12:49 PM

    Hi L.Elias.

      What if the audit trail isn't a reporting tool? I recommend using the process engine to 'date stamp' the events you're interested in. Below is an example of where we date stamp when the investments move into stages and each night 'count up' business days in that stage (we stamp other events too). We use attributes to 'capture' this data - therefore it is available in Clarity on the object, easily available for portlets, reports and - once we have Jaspersoft - it's a checkbox away from being in the datamart.

    stages.jpg

     

       I think it's better to put the effort into getting the information into the right spot vs. building reports against something that's not built to report from (and - is not supported to report from).

    FYI - We built all this first out of the Audit trail (built a nightly job to 'datamart out' the dates and days), but then the next layer of this onion was that, in order to get at this data everything was custom reporting. Then CA changed the audit trail... shame on me - again, this was not/is not a supported integration/reporting point.

     

       The above approach is so much better since the data is now in a fully supported spot in the datamodel that all user can get at (above is the project list!) and do with it what they wish.