Table of Contents

Key Expectations

What are the “Must Haves” in order for our customers to consider Logging to be vastly improved in Next Gen?

  • 100% of all changes made are logged, no matter where that change occurs - "Log Everything!"
  • Admins or end users with appropriate permission are able to drill down to see the log information they want to see
  • Quick and easy to find logged information

Changes & Differences from Existing Functionality

  • After every data change, users will have the option to enter a comment describing the reason for their change
  • There will not be a separate log for API requests since everything will be API driven
  • Log changes can be made available to end users, not restricted to just admins
  • There will be no way to bypass logging via the backend or other methods that would cause a data change to not be logged
  • Viewing of data will be logged in addition to changes

Wireframe Concepts

Here are some mockups of the Logging features. This first mockup illustrates entering a log comment when making a data change.

This mockup shows a timeline view which would displayed on a relevant page, in this case Student Information. The user will be able to see a high level view of changes, but be able to drill down to more details and view the full log from here. 

Users, with appropriate permissions, will be able to drill down into the full log details, and filter or export any of the data found.

Plan Summary

  • Who changed what and when? That is the focus of the Logging feature in Aeries today. This feature in Aeries NextGen will be taken to the next level, and made more transparent by allowing this information to be shared with those who may need it. The Logging feature in Aeries currently tracks all changes to data, however it can be circumvented by making changes via the backend (SQL) or even within certain processes within Aeries such as change queries. The new logging feature in NextGen will be more robust, and will not allow bypassing of business logic or circumventing in any way, because using the API will be the only way to make changes. In the future, when someone makes a change in Aeries it will be faster and easier than ever before to identify who made that change, what was changed, and when.