Update ISA audit logging


As an admin I want all changes to the ISA via upload process to have audit logging so that I know the system has a detailed log of what data was changed and when and by whom.

Acceptance Criteria:

  1. When changes are uploaded and saved to the system per ticket OLMIS-396, these changes are logged in the backend.

  2. Audit logging includes user name, facility name, product name, previous ISA, updated ISA, and date the change was saved.


Brandon Bowersox-Johnson
August 7, 2017, 10:57 PM

I updated the User Story to reflect that (using strikethrough and underscore to show my edit).

Mary Jo Kochendorfer
August 7, 2017, 10:55 PM

, at this time it would only be the backend piece.

Brandon Bowersox-Johnson
August 7, 2017, 6:59 PM

Open Question: Does this ticket include a way for end-users (admins/implementers) to view the audit log, meaning viewing the history of ISA edits over time? Just enabling audit logging will store this data in the back-end. If there is any question about who edited what, a tech support person can pull up the data and provide it upon request. But so far we have not done much to expose audit logging data to make it visible. The user story is phrased "so that I know what data was changed and when" and that might or might not be what is included in this ticket. Chongsun can definitely describe that more.

Sam Im
August 4, 2017, 8:13 PM

Here is the audit logging ticket we discussed.




Sam Im