×

Metadata-driven audit reporting system

  • US 10,108,917 B2
  • Filed: 03/07/2014
  • Issued: 10/23/2018
  • Est. Priority Date: 09/11/2013
  • Status: Active Grant
First Claim
Patent Images

1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to report audit data comprising a history of modifications made to data in a software application, the reporting comprising:

  • defining metadata for an attribute of a business object of the software application stored in a base database table, the metadata including;

    a business object identifier,an attribute identifier,an auditing enabled flag that identifies whether auditing is enabled for the attribute,a shadow database table name that identifies a shadow database table associated with the base database table, anda shadow database column name that identifies a column of the shadow database table associated with the attribute of the business object;

    configuring the metadata to enable auditing for the attribute of the business object, including setting the auditing enabled flag of the metadata to a value that indicates that auditing is enabled for the attribute;

    during execution of the software application and in response to a modification to data stored within the base database table, generating first audit data for the attribute of the business object only when the auditing enabled flag of the metadata is set to the value that indicates that auditing is enabled, the first audit data including a history of one or more modifications to the attribute of the business object;

    storing the first audit data for the attribute of the business object within the shadow database table identified by the shadow database table name and the shadow database column name, the first audit data comprising data stored within the base database table prior to the modification and data stored within the base database table after the modification;

    during execution of the software application and in response to an event occurrence at the base database table, generating second audit data and storing the second audit data in an event database table, wherein the event comprises a login failure event of the software application and wherein the event database table has a different format than the shadow database table; and

    displaying the first audit data and the second audit data within a user interface using a single format for the first audit data and the second audit data.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×