Important Update Information
Release Date: August 2019
As promised on the Aeon Roadmap, here are the main features/enhancements of Aeon 5.0:
- Staff Configurable Scheduled Date Calendar (Blackout dates)
- LocalInfo Support per Site
- Updated Staff Interface with Large Font Support and Ability to Change Themes
- New, Fully Accessible and Responsive Web Pages
Considerations Before You Update
Updating During Normal Working Hours
Please consider running updates and installations during standard support hours 8 am - 5 pm eastern time (business days Monday - Friday) so that help is readily available if any issues are encountered.
If you are updating from Aeon 4.0 or a previous version, please check out the Aeon 4.1 Release Notes and FAQ since all the password change requirements will impact you after updating to version 5.0.2. You will need to update the server and the client on each machine to 4.1 prior to updating the server and clients for Aeon 5.0. You don't need to login or change any passwords until after you've updated to 5.0.
Bug fixes and new features are added periodically as point releases:
- 19 Aug 2019 (5.0.2) Client Release
- 20 Jan 2020 Aeon Default Web Pages Update
- 27 Feb 2020 (5.0.3) Client Release
Aeon 5.0 Features & Fixes
Updated staff interface (Client, Staff Manager, and Customization Manager) with large font support and the ability to easily change the appearance by selecting one of the eight new themes from the main drop-down menu. For more information, see Theme Selector.
|Changed||All knowledgebase links in the Client, Customization Manager and Staff Manager have been redirected to new support landing page https://support.atlas-sys.com.|
|Fixed||Fixed the Azure database permissions by excluding the default 'sys' view that caused the update scripts to fail when granting permissions to sites. Bug# 3407.|
Printing & Email
|New||Added the ability for sites specific LocalInfo entries that would populate email and print templates. For more information, see The Local Info Table.|
Added support for FIPS (Federal Information Processing Standards) 4.1.0 compliance.
If you're an existing site that staff users from prior to the 4.1 update and are required to be FIPS compliant, please contact email@example.com for further instructions.
The SLLoginFailed status line Customization Key has been added to appear if a user attempts to login with an invalid username and password. The default verbiage is set to say "Login failed. Please check your username and password before trying again.".
The Customization Keys SLUsernameNotInDatabase and SLPasswordIncorrect have been removed and replaced with the new SLPasswordIncorrect key.
|New||The CloneScheduledDateInClient customization key has been added to the Customization Manager under System | General to determine if the scheduled date is copied over when cloning transaction in the staff client. Default value is set to "No".|
|Fixed||Enabled Group By Option on user search form (FormUserList). Bug# 3416.|
|When a Field Customization is removed in the Staff Manager, the Activity Requests Grid will reflect the changes (e.g., removed custom column names). Bug# 3638.|
|New||New fully accessible and responsive web pages that adhere to WCAG 2.1 AA compliance. The new web pages are not installed automatically to prevent overwriting any customizations your institution may have created. The complete set of webpages are available for download on the Aeon Downloads page. For more information, see Aeon 5.0 Fully Accessible and Responsive Webpages.|
|New||Added cookie notification in accordance with the EU cookie law to provide a link for institutional privacy policies. See the FAQ for instructions on setting up the link.|
Added support for a more configurable schedule date calendar with a new "Scheduled Closures" database table in the Customization Manager under Web Interface | Schedule Date | Scheduled Closures and 3 new blackout date customization keys:
For more information on how to utilize the new Customization Keys and the Schedule Closures database table to schedule blackout dates, see Blackout Date Calendar for Aeon Requests.
For more complex reoccurring closures, you'll need to modify the scheduled-closures.js. To support this change an AJAX endpoint was created to receive a JSON file containing all active scheduled closures. For more information, see Blackout Date Calendar Configuration for Aeon Request.
Improved ability to customize web alerts. For more information, see Performing an AJAX Request to View Web Alerts.
Fixed an issue where the "Download XLS" button would show the error message "Error processing method" after failed attempt to download the Activities from the Aeon 5.0 Web Pages. Bug# 4566
Aeon 5.0 Point Releases
19 Aug 2019 (5.0.2) Client Release
Fixed issue where the System Information tags (e.g., the site field value) from the LocalInfo table was not being pre-populated into email templates.
20 Jan 2020 Aeon Default Web Pages Update
A revised set of default web pages are now available for download in the Aeon Downloads article with the following change incorporated:
|Changed||Removed the Main.css page since the file is no longer used and moved the EAD CSS rules to the Aeon.css page.|
|Changed||Added a blank Custom.css page to the default web pages for site-specific custom CSS changes.|
|Changed||Updated the EditEADRequest.html page to have the same style as the rest of the default web pages.|
|Changed||Removed the RSS feature from the ViewNotfication.html page due to the notification option no longer being supported in web browsers.|
|Changed||Removed one of the duplicate include_footers in the default FAQ.html page.|
|Fixed||Fixed the Status drop-down on the NewUserRegistrationForm.html and ChangeUserInformation.html to populate with information. Bug# 4804|
|Fixed||Fixed the checkbox functionality for sharing research topics with the NewUserRegistration.html, ChangeUserInformation.html, and NewAuthRegistration.html pages. Bug# 4551|
|Fixed||Fixed a typo in the NewUsersRegistration.html page. Bug# 4542|
|Fixed||Removed the extra space in the ChangeUser.html that was causing the alternative address information section to ignore the settings in the Customization Manager. Bug# 4549|
|Fixed||Fixed an issue where the NewAuthRegistration page would not fully render because of a tag error. Bug# 4861|
|Fixed||Fixed an issue where the PayPal CreditCardPayment.html page would not properly submit payments. Bug# 4600|
|Fixed||Fixed an issue where the Aeon WebAlerts may contain HTML tags in both the title and the body of the message. Bug# 4540|
28 February 2020 (5.0.3) Client Release
|Fixed||Fixed a bug that would prevent custom layout changes in the Activities grid from saving/loading after the Client has been restarted. Bug# 4499|
|Fixed||Fixed an importing issue that would prompt a validation error if the Format, ServiceLevel, and/or ShippingOption fields were blank when importing a request from a spreadsheet. Aeon will now import those fields as NULL if they are left blank. Bug# 4369|
|Fixed||Fixed an issue where date values would be export as a plain text string instead of the date format when exporting transactions from the grid to Excel. Bug# 4432|
|Fixed||Fixed an issue where the "Modified By" field was being set to the username of the Staff User whose password was changed instead of the username of the logged-in user who reset the password. Bug# 4258|
|Fixed||Fixed an issue that would prompt an error message when Staff attempted to clone a request by clicking the arrow icon next to the 'Clone Request to Another User' button in the Client. In conjunction with this fix, the 'Clone and Finish' button will only be available when applicable. Bug# 4541 & 4022|
|Fixed||Fixed a searching issue in the Aeon Client's Activity form that wouldn't account for compound search terms when matching first and last names in a username search. For example, a search for 'Von Neumann' would return results if Von was in the FirstName and Neumann was in the LastName but a search for 'Von Neumann' would not match if Von and Neumann were both in the LastName.
The search algorithm has been fixed to correctly return matching users for compound searches provided all search terms were included in the user's FirstName or LastName. Bug# 3959