Aeon 5.0 Release Notes

Follow

Important Update Information

Release Date: August 2019 

Highlights  

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 
VisualStudio_2013Blue.png   Office2016_Dark

To view the pictures on a larger scale, click the image to expand.

  • New, Fully Accessible and Responsive Web Pages   
aeon_webpage1.png aeon_webpage2.png

To view the pictures on a larger scale, click the image to expand. 

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. 

Updating from Version 4.0 

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.

For any questions on the Aeon 5.0.2 features & fixes, please see the Aeon 5.0 FAQ. For all other questions, please contact support at support@atlas-sys.com.

Bug fixes and new features are added periodically as point releases:

Aeon 5.0 Features & Fixes 

AdministrativeMiscellaneous | Printing & Email | Security | Staff Client | Staff Manager | Web Interface

Administrative 

New

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.


Miscellaneous  

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.

Security

New

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 support@atlas-sys.com for further instructions. 

New

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.  

Staff Client

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.

Staff Manager 

Fixed

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.

Web Interface 

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.
New

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:

  • ScheduledDateMinimumDays- Determines the minimum enabled date for the Scheduled Date calendar on web request forms in the terms of days. For example, if staff requires 48 hours to process a request the minimum should be set to 2. Default value 0.
  • ScheduledDateMaximumDays- Determines the maximum enabled date for the Scheduled Date calendar on web request forms in the terms of days. For example, if staff doesn't want patrons requesting items 6 months in advance, the maximum should be set to 180. Default value 0.
  • ScheduledDateDefaultSchedule- Determines the weekdays that should be enabled as operating days for the Scheduled Date calendar on web request forms. Default values Monday, Tuesday, Wednesday, Thursday, Friday.

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.

Changed

Improved ability to customize web alerts. For more information, see Performing an AJAX Request to View Web Alerts.

Aeon 5.0 Point Releases

19 Aug 2019 (5.0.2) Client Release

Fixed

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.

 

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback