Adding columns to the audit trail

If you expand the folder (or whatever the proper term is) for the table being updated in object explorer you will find a sub-folder called "Triggers", this is where they are kept.
For example look at t_phone, you'll find the Insert Delete and Update triggers.

I assume since these are not local tables they are hands off.

Yes, you are free to put triggers on local tables, but not on standard tables.  If you are looking at auditing updates to the constituent record, take a look at LP_CUSTOMER_RANK which is executed every time a constituent record is updated.  It was originally intended to update ranking values based on custom logic, but has been also used for custom work in other areas. 

This also can easily become a performance burden as this local procedure is executed every time a constituent is updated.  If you have performance issues, this is the first place we will look in a support ticket.  Heed the warning! :)

So, you are free to place code here, but it should be quick and concise!

And re-reading your post, it is a hands-off policy on altering existing triggers on standard tables.  Sorry for the lack of clarity in the previous post.

That being said, have a great weekend!

-Ryan

And re-reading your post, it is a hands-off policy on altering existing triggers on standard tables.  Sorry for the lack of clarity in the previous post.

That being said, have a great weekend!

-Ryan

Thanks for the repsonses.  I'll have to give some thought to how we want to proceed.  I'd be especially interested in hearing from consortium admins on what, if anything, you've done to enhance ta_audit_trail to perhaps resolve data management issues between organizations.

Ryan,

I'm always leery of adding to LP_CUSTOMER_RANK, but it is a nice avenue to have.  Just to make sure I understood you correctly, editing existing triggers on standard tables is out.  Is adding additional triggers also verboten?

I haven't worked with triggers much in the past so it may be a moot question if you can only have one trigger per action (i.e. update/add/delete)

Looks like LP_CUSTOMER_RANK it is then.

My immediate need is to audit T_EADDRESS.market_ind but I can forsee a need to do other fields as issues arise.