Why doesn't the audit log always show what action triggered a change?

Rachel Lake

Hi there, 

I've noticed that certain actions (I'm thinking mainly of benefits) will trigger a change to a record, but when I go to the audit log to look at that change, the audit log doesn't reference the action that took place. I think it's helpful to know if I as a user manually updated a record, or if the running of a larger process updated the record. Does anyone else agree? 

For example - I've run both Mass Stop Enrollment and Mass Create Eligibility. When I go to a record affected by Mass Stop Enrollment, I can see in the audit log that the action was "MassStopEmployeeBenefitEligibleThread." However, when I go to the audit log for the record created by Mass Create Eligibility, the action just says "create." It makes it look like I manually modified the record.

I'm probably going to submit an enhancement request, but I wanted to throw this out there in case anyone had any thoughts, or struggles with this set up as well.

reaganr

Hi,

We select reasons when running the enrollment updates. The reason is available after the update an makes it a bit easier to see what's happened. I would support an enhancement on the mass create eligibility and mass create enrollment to have an indicator on the audit log that the record was created by one of these processes.

Thanks,