Auditing the changes in BO's

weblike

Hi,

Has anyone created an audit system in your apps?

I want to create autid for 3 actions: Add new Record, Modify/Edit, Deleted Record

I don't want to use the GET_CHANGES to see old-new values, just a simple auditing to see like this:

I use a rule in the Invoice BO:

IF InvoiceBO WAS CHANGED Then
AuditRecord.ChangesType='Modified',AuditRecord.UserName=LoggedInUserName, Date=CURRENT_TIMESTAMP

The problem is that I have calculated values inside Invoice and everytime a Delete a invoice line the system creates 7 AuditREcords with same action.

Has anyone a better example of this?

thx,

pureist

It seems like you only want to create an audit record:

when the form of an object instance is saved,
..OR,
when the form of a reference atribute object instance is saved.
..and not create an audit record for every change of every attribute.
If so, why not run a process after the form of an object instance is saved, or after the form of a reference atribute object instance is saved, which creates an audit record?
Obviously this won't take into considerationc changes effected other than via a Form, and won't take into consideration in-line changes.

But you could easily change in-line editing of line items to editing them in a form which opens in an expanded row (rather than a pop up).
BUT, you will not be able to delete line items via a Delete Object button on the form which is in the expanded row because of a bug which will destroy the entire contents of the tab, and the webpage will then have to be reloaded.
To delete line items you would still have to have a delete button on the query row, or have a Delete button on the panel of the grid whose applicability is 'Applicable to Multiple'.
OR, have a pop up form to edit the item, in which case you can have the delete button on it.

BenHayat

George, don't take the lazy route of using Rules. Best to do auditing as part of process than BO rules. BO Rules should be small and singular, so it won't affect your performance.

hpl123

George,
I would take a look at rule priorities if I were you OR rewrite the rule and add some conditional flag and your other rules can change when all rules have executed (and then the audit log would be executed when the flag is changed).

weblike

Thank you guys for your replies.
I have tried all the scenarios you have suggested:

Via executing a process after the form is saved. Well this is not quite ok, because every time the user hits Save it creates a audit record, or if you have put on a attribute to save the form every time it changes values.
The most attractive was via processes, but when I create a process with "EDIT BoName" in current tab, if I clikc the menu buttons on the form I keep receiving this message on the screen "Do you want to cancel the operation?"
I have created a flag in Bo....flag=Attribute as type Timestamp and I created rules like: " If BoName WAS CAHNGED Then CREATE AuditBO WITH......"
This one works until now, but I wonder how much impacts the performance of my app?

On #2 I guess it's a bug or something is wrong because a normal appliction should not work in that way in real internet.

Thank tou guys again for your thoughts, were very helpful.

Cheers,