We are currently using LLBLGenPro v2.0 Jun/18/2007 release, Adapter Two Class Model
We need to audit even if someone viewed a customer record plus other typical audits for Insert/Update/Delete.
We have a separate AppAuditLog table with these fields:
AuditLogID (Identity column), UserID, UserName, CustomerID, CustomerName, AppModuleName, RecordID, ActionTaken, ActionDate
E.g., User viewed customer record 1234
Audit info would be:
AuditLogID: 1
UserID: 101
UserName: Test User1
CustomerID: 555
CustomerName: Test Customer
AppModuleName: CustomerChart
RecordID: 1234
ActionTaken: VIEW CHART
ActionDate: 1/12/2006
Other examples for ActionTaken would be "ACCEPTED DEPOSIT", "CLOSED ACCOUNT", "INCRESED CREDIT LIMIT", etc.
Q1: What is the recommeded way to implement this requirement?
2.5 Beta talks about Auditing support
Auditing support. You can now define auditors which record audit information during the entity's life cycle and can provide audit entity objects (of the type you provide) to the framework to be persisted automatically when the audited entity is part of a transaction with the database. This gives great flexibility what to audit and when and frees the developer from the hassle to persist the audit entities at some point in time.
Q2: Assuming we can wait, are we better off waiting for 2.5 release and use the audting support provided in v2.5?
Thanks in advance!
