Product Description
August 17th – September 7th
Development of the Audit process
We need to write back to the database an audit log that shows all the steps a user has performed inside the application. If a mistake is made, we need to be able to allow for an edit that will enable the user to fix the error. When a record is fixed, we want the old record to remain in the database but mark it as inactive. This way it can be displayed in an error log, audit table and not display on reports. This process means that the reports will all be based on the omission of the inactive field. (Reports were changed previously)
Sept 10th – 15th
A screen is needed to enable a user with security clearance the ability to open records and make changes to the values. Security permissions are already in place for allowing users to log into areas of the application so this would be an additional permission level.
This screen will allow the user to search for a specific entry and make the change. It will then save the r