I have quite heavily adapted the audittrial module to my needs.
First of all you should run a scheduled event once a month for example and remove old audittrial logs. In combination with the MxReflectionModel module I have specified the members/attributes of an entity that should be audittrialed. Achieved this by creating a boolean where the admin can specify whether a logline should be created for a particular attribute/member (some fields are used internally by the developer/under the bonnet and should not be audittrialed/visible for the user)
Using the mxreflectionmodel you can also specify user-friendly names for the attributes and associations. I have also managed to change the way certain values are displayed (old and new) especially in regard to associations and enumerations.
most of the things can be achieved by using microflows but I also used some java and manipulated a few audittrial classes/methods.
Thanks Karol,I understand. but I have a general concern for the way that auditing module works by using the inheritance of auditing-trial-super-class which will save many many records overtime if we apply auditing on many entities , we cant clear this super-class data(which will contain all the number of records of the sub classes)
You have to be very carefull with this module. It serves its purposes but is too technical to be used by business users and can easily clog up your database, hence needs quite some adaptations. A couple I implemented:
Hi Ivo,
Thanks for you reply.
If its possible with you can you help me with the implementation of same thing in JAVA ACTION or you can share that updated JAVA ACTION code with me.So it will be very helpful for me.