OLAP allows audit information to be stored for specific cubes. The storing of audit information is disabled by default. To enable it, the parameter “audit” has to be added to the configuration file palo.ini. It is a switch parameter and has no additional arguments. Additionally, audit storage has to be enabled for every database cube for which it should be kept.
- At least W rights are required for the rights objects “dimension element” and “audit” to make changes to the audit settings.
- You cannot enable the parameter “audit” together with the parameter “crypt” In the file palo.ini. The data storage for audit information currently cannot be encrypted, and so that storage would contain readable data information which would conflict with the purpose of the “crypt” option.
Enabling audit storage for a database cube
Open the Administration panel in Jedox Web and click on the Settings tab. Here you can select the cubes and the period for which the audit information should be stored:
The audit keeps track of all individual cell changes: it logs the cell path, time of change, user, new value, and operation (Splashing, Copy, etc.).
Note that auditing only stores the change for the cell that was directly modified. It will not store indirect changes, such as when a cell is affected by a splashing operation on a parent element. Also, mass data changes as performed by Jedox Integrator will not be logged.
You have two possibilities to display the stored audit information:
- With the Audit tab (see below)
- With context menu command “Drill History” in Jedox views (right click on a corresponding cell).
In the first line of the Audit tab, you can set the filter for the audit data you want to see. Click on Apply Filtering to see the selected audit data:
Most of the columns are self explanatory. The DETAILS column on the right indicates the mode of the cell change. The table below explains the results:
|mode=0||Base cell writeback|