S40(24) Dev - eForm change log [jp-0003] #187
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MNP auditor observed that there was no eForm change log, which could lead to unauthorized/erroneous changes being made without being identified.
Question
-Should we create an eForm audit log similar to existing audit logs that tracks changes from the eForm queue?
Are our current audit logs and the Maintain Events table/process enough to meet the need and I just need to document.
We may not need to do more work on this and just focus on Nancy documenting.
April 28 - This is currently captured in the PECSF admin>system security section>Auditing> filter for Bank Deposit event form. James recommends to enhance with user/date stamp for create update details in PECSF Admin>Pledge Admin>Maintain Events (details). This note has been added to the FRCR audit tracking table.
Dev has suggested a created/updated (user/date) stamps in the PECSF Maintain Events details to enhance. See attachment, James or Nancy for details, if needed.
Ticket