Constituent -> Transactions -> Audit is showing our generic username for the Service Layer (tessApi) instead of the editing user. Is something set up wrong in the triggers? Is this a known issue in v11?
The triggers seem to use FS_USER, but this is old code. Apparently AP_SET_CONTEXT will set the correct user, but where is this missing?
We now have over 1700 records affected by this.
Hi David,
After seeing your post here, I checked our own audit data since 8/1/2013... I found similar results. There are a number of actions, like inserting/updating associations, updating salutations, and updating customer name data, that appear under the correct user. However, here are some activities that regularly show up in our audit trail as the generic services user:
Ironically, I'm also finding actual users for some of these same actions, although lower quantities. I'd say there is definitely a hole somewhere; having the generic services user tracked in the audit trail is not very helpful. It might be worth opening a ticket on that.
Thanks,David