Aeon 5.2 Release Notes

Print Friendly and PDF Follow

Important Update Information

Released - May 16th, 2023

Highlights

As promised on the Aeon Product Roadmap, here are the main features/enhancements of Aeon v5.2:

There are over 50 bug fixes in this release.

Considerations Before You Update

Review Aeon 5.2 FAQ and Webinars

For frequently asked questions and additional information regarding the 5.2 features and fixes, please see the Aeon 5.2 FAQ. You can also view the Aeon 5.2 release webinars in the Video Training Library, which include a general Q&A session and two detailed sessions overviewing the new 5.2 Appointment Scheduling features and the updated ArchivesSpace Request Fulfillment plugin. For all other questions, please contact support at support@atlas-sys.com. 

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 Procedures

Before you begin updating, please review the Hardware and Software Requirements for Version 5.2. For specific instructions on updating, see Updating Aeon to the Newest Version. Please also review the Installing and Updating section of the release notes.

Warning! New System Requirements

  • The IIS 6 Management Console component must be installed on Aeon Servers using Windows Server 2022 prior to performing the Aeon 5.2 server upgrade due to a known issue affecting PowerShell. For installation instructions, see Installing Required Windows Server 2022 Components for the Aeon 5.2 Update
  • Aeon Server 5.2 requires Microsoft .NET Core 2.2 or higher. The Microsoft ASP.NET Core 2.2 Runtime bundle is now required for the Aeon API and can be installed via Microsoft's websiteTo prevent disruptions in the Aeon API after updating, please ensure that this bundle is installed on the Aeon Server prior to updating to Aeon 5.2.
  • .NET Framework 4.7.2 may be required to perform the Aeon 5.2 server upgrade. See the Installing and Updating section of the release notes below for more information.
  • Aeon Client 5.2 requires Windows 10 or higher. Due to the WebView2 changes included in this release, the Aeon Client will not successfully install on machines using earlier versions of Windows operating systems. Attempting to install Aeon 5.2 on an incompatible operating system will cause the Aeon Client Installer to return an error stating "there is a problem with this Windows Installer package." 

Troubleshooting Information

Some users may experience an "Upload Error" when using the Upload File feature in the Aeon Client after updating to Aeon 5.2. For information on resolving this error, please see Resolving File Upload Errors After the Aeon 5.2 Update.

Aeon 5.2 Features & Fixes

Aeon API | Addons | Administrative | Appointment Scheduling | ArchivesSpace Request Fulfillment Plugin | Customization Manager | Database | Email | Installing and UpdatingStaff Client | Staff Manager | System Manager | Web Interface

Aeon API

New

Added several new endpoints to the Aeon API:

  • Get Users: Returns a list of all users up to 2000 results. OData filtering options are available for use with this endpoint to specify and limit the type and number of results.
  • Post Note: Adds a note to an existing request
  • Get Note: Returns a list of notes associated with a given request
  • Update Request: Updates information for an existing request

For more information, see Aeon API.

Changed

The Create Request endpoint (/api/Requests/create/) will now perform validation to ensure that the request can be added to the associated appointment based on the timeframe configured in the associated reading room's Request Minimum/Maximum Lead Days settings in the Aeon Customization Manager.

Changed

The Create Request endpoint will now return detailed error messages when invalid values are submitted for the requestFor and customFieldValues properties. Bug# 13747

Fixed

Fixed an issue where validation would not be applied to ensure that users were properly associated with activities attached to requests created using the Create Request endpoint. The endpoint will now return an error if the specified activity is not associated with the user for whom the request is created. Bug# 11562

Fixed

Fixed an issue where the Create Request endpoint would return an error stating that the format, serviceLevel, and shippingOption field values were invalid if the specified requestFor or username values contained an invalid username. Bug# 13743/Bug# 17649

Fixed

Fixed an issue where the API would return incorrect or redundant error messages when validating transactions. Bug# 8889

Fixed

Fixed an issue where certain configuration changes such as updates to existing activities, users, and appointments would not be detected by the Aeon API until the IIS service was restarted. Bug# 13746


Addons

New

Added support for the Microsoft Edge WebView2 embedded browser within the Aeon Client and Client addons. Support for the WebView2 browser will include the following enhancements:

  • Easier updating process: The WebView2 browser is updated via the Windows Update process on your local machine, removing the need to update the version of the browser used by Aeon by manually updating the Aeon Client.
  • Accessible version tracking: The version of WebView2 currently installed on your machine and used by Aeon can be easily checked by navigating to the Resources tab located within the Aeon Options form in the Aeon Client. 
  • New cache clearing options for easier debugging: A Clear Cache button is available next to the WebView2 version number information on the Aeon Options form that will clear the cache for the WebView2 browser (cookies, logins, and browser history) on the local machine for the user currently logged into the Aeon Client.
For more information on the Aeon Client controls listed above, see Locating System Details and Clearing the WebView2 Cache in the Aeon Client. 
Addons developers can find complete information on implementing the WebView2 browser within addons in the addon documentation.
Note: This update will not remove support for the Chromium or IE browsers from the Aeon Client. However, due to Microsoft’s end of support for Internet Explorer, we cannot guarantee that addons using the IE browser will work indefinitely with Aeon. It is strongly recommended that addon developers update addons to include support for WebView2 and that users update their addons to the new WebView2 versions when available.
The WebView2 browser will only be used for browsers embedded within the Aeon Client. Any browser windows that open externally from the client will still use your machine’s default browser.
New

Updated the Aeon ArchivesSpace Client Addon to use the new WebView2 embedded browser.

For information on installing the addon, please see the addon's page in the Aeon Addon Directory.


Administrative

New

Added the collection of telemetry data to the Aeon Client and Web API. This feature will track the number of times each form and button is used in the Aeon Client and each time an endpoint is used in the Aeon API to assist with prioritizing features for future updates. Data collection will operate under the following restrictions and privacy considerations:

  • The data collected will not be associated with your institution and only a general number of total clicks by all Aeon users will be recorded and transmitted to Atlas (e.g., the total number of times the Activity tab is opened on a certain day by all Aeon users).
  • To protect user privacy, no personally identifying data including request, activity, appointment, staff, or user details will be collected.
  • All data collected will remain internal to Atlas Systems and will not be shared with third parties.

For more information on this feature, see Aeon Telemetry Data Collection.

Changed

Logs for the following Aeon components are now configured to use UTF-8 encoding by default to fix an issue where some characters, such as those with diacritics and non-Latin characters, did not display correctly (Bug# 21305):

  • Aeon Client
  • Customization Manager
  • Staff Manager
  • System Manager
  • Web Platform
This change will be applied automatically for new Aeon 5.2 installs only (i.e., those installing Aeon for the first time at version 5.2). If updating to Aeon 5.2 from a previous version of Aeon, the encoding change must be applied to each log's configuration file manually following the instructions in the documentation.

Appointment Scheduling

If you are updating from Aeon 5.1 and already have appointment scheduling features enabled, please review the appointment scheduling update checklist and make note of important changes and action items that should be performed before and after updating to Aeon 5.2.
New

Appointment Status and Confirmation Workflows

Reading rooms can now be configured to require that appointments booked in the room by patrons on the Aeon web interface are manually reviewed and confirmed by staff in the Aeon Client using new appointment confirmation workflow options:

  • All appointments will now have an associated appointment status that will be displayed in the Aeon Client and patron web interface. The status can be one of three values: Confirmed, Unconfirmed, or Cancelled
  • Appointments are no longer deleted from the database when cancelled and will remain accessible in the Aeon Client and patron web interface with a status of Cancelled
  • Appointments created by staff in the Aeon Client will be confirmed automatically by default
  • Appointments booked by patrons on the web will be unconfirmed by default unless the Auto-Confirm Appointments setting in the Aeon Customization Manager has been configured to automatically confirm appointments for the reading room
  • Both confirmed and unconfirmed appointments will be considered as occupied "seats" in the reading room when calculating reading room booking availability on the Aeon web interface
  • The number of unconfirmed appointments for each reading room will display in the new Appointments to Confirm List on the Home screen of the Aeon Client 
  • Unconfirmed appointments can be reviewed, confirmed, or cancelled from the new Appointment Confirmation form in the Aeon Client, which provides a central location for staff to view the list of all unconfirmed appointments for each room, a list of each unconfirmed appointment's associated requests, and a list of other appointments booked in the same room for the same date
  • New Confirm and Unconfirm buttons can also be used to update an individual appointment's status directly from the Appointment form
All existing appointments will be set to the Confirmed status upon updating. Existing reading room calendars configured in the Aeon Customization Manager prior to updating will have the Auto-Confirm Appointments option unchecked (disabled) upon updating to Aeon 5.2, meaning that appointments booked in the room from the web interface will be Unconfirmed by default.
New

Appointment Reminder and Notification Emails

To support appointment confirmation workflows, new email templates and notification options have been added for sending patrons additional appointment notification and reminder emails throughout the appointment booking and confirmation process:

  • Appointment Received: Sent automatically by Aeon when a patron books an appointment on the web if the new Notify Appointment Received setting has been checked (enabled) for the reading room in the Aeon Customization Manager
  • Appointment Confirmed: Optionally sent to the patron to notify them that their appointment is confirmed when the appointment is manually confirmed by staff in the Aeon Client
  • Appointment Reminder: Sent automatically by Aeon a configurable number of days before an appointment to remind patrons of their upcoming confirmed appointments if the new Reminder Days setting has been configured to send reminder emails for the reading room in the Aeon Customization Manager
Existing reading room calendars configured in the Aeon Customization Manager prior to updating will have reminder emails disabled and appointment-received emails enabled after updating. Enabling reminder emails for a reading room after the 5.2 update will also schedule reminder emails for upcoming appointments that were booked in the room prior to updating. 
New

Added a new Reading Room Description field to the appointment scheduling settings for each reading room calendar configured in the Aeon Customization Manager. This field can be configured with reading-room-specific policies and then added as a merge field on appointment-type email templates to customize them with information related specifically to the room in which the appointment has been booked.

Reading Room Description is only used on email templates and will not be displayed by default to patrons anywhere on the Aeon web interface. This field is limited to 1000 characters.
New

New and Improved Client Appointment Form

Updated the Appointment form used to display and edit information for individual appointments in the Aeon Client with the following new options and features:

  • Detail and History Tabs: Appointment change history will now be tracked in the new History tab that will display a grid containing detailed information for changes made to the appointment as well as a grid of all appointment-type emails sent to the user for that appointment. A separate Detail tab has also been added that will contain all other information for the appointment.

    Appointment-type emails that were sent before updating to Aeon 5.2 will not display in this grid and will continue to display on the User form.
  • Appointment Notes: Added a new Notes grid (located under the Detail tab) that gives staff users the option to add notes for individual appointments

    Appointment notes can only be added and viewed by staff users in the Aeon Client and will not appear to patrons on the Aeon web pages
  • Callslip Printing: Added a Print Callslips button to the Appointment ribbon that will allow staff to print callslips for requests associated with the appointment directly from the Appointment form. Options are available to print callslips for all associated requests or only for requests in the Awaiting Request Processing status
  • Reading Room Sign In Options: Added Sign User In, Sign User Out, and Away buttons to the Appointment ribbon that can be used to sign researchers in and out of reading rooms directly from the Appointment form
  • Form Customization Options: The layout of the form can now be customized for staff layout templates. For more information on the custom template feature, see Creating and Assigning Templates to Staff Users.
  • New Fields: Added new Creation Date and Status fields to the Detail tab that will display the date and time that the appointment was created and the current status of the appointment (these fields are read-only)
  • Redesigned Cancel Button: The Cancel Requests checkbox option that was previously located next to the Cancel button has been moved to a dropdown menu below the button. Options for sending and editing the Appointment Cancelled email have been moved into Send Email and Edit Email toggle options next to the Cancel button for a smoother user experience:

    Redesigned Cancel Button

New

Redesigned Reading Room Calendar Configuration Interface

The Appointment Scheduling tab in the Aeon Customization Manager has been redesigned so that appointment settings for each reading room are now configured in two separate Policies and Open Hours sub-tabs:

  • Policies: Contains general settings for the reading room (including Reading Room Name, Seats Available for Appointments, and Minimum/Maximum Appointment Length) as well as the tables used to configure the room's Associated Sites and Status-Specific Policies (see release notes entry below)
  • Open Hours: Contains the room's Open Hours settings and the Exception Dates table used to configure the reading room's hours, closures, and partial closures
For complete details, see Configuring Reading Room Calendars.
New

New Status-Specific Configuration Options for Reading Rooms

The following new and existing reading room appointment settings in the Aeon Customization Manager can now be optionally configured into separate sets of status-specific policies that will be selectively applied based on the status of the user requesting an appointment (e.g., staff, undergraduate, faculty, etc.):

  • Appointment Minimum Lead Days (new)
  • Appointment Maximum Lead Days (new)
  • Request Minimum Lead Days (new)
  • Request Maximum Lead Days (new)
  • Appointment Required 
  • Auto-Confirm Appointments (new) 
  • Reminder Days (new)
  • Notify Appointment Received (new) 

These settings are found and configured in the new Status-Specific Policies table that has been added to the Policies tab for each reading room calendar configured for appointments in the Aeon Customization Manager.

For complete configuration details, see Configuring Reading Room Calendars.

Each existing reading room calendar configured in the Aeon Customization Manager prior to updating will have the values contained in its Minimum/Maximum Lead Days and Appointment Required settings imported into a default, non-status-specific row in the Status-Specific Policies table after updating to Aeon 5.2:

  • Minimum/Maximum Lead Days values will be imported into both sets of the new Appointment Minimum/Maximum Lead Days and Request Minimum/Maximum Lead Days settings
  • Auto-Confirm Appointments will be unchecked (disabled)
  • Reminder Days will be set to -1 (disabling reminder emails)
  • Notify Appointment Received will be checked (enabled)
New

Separate Minimum/Maximum Lead Days Settings for Appointments and Requests

The Minimum Lead Days and Maximum Lead Days settings used when configuring reading room calendars in the Aeon Customization Manager have been split into separate Appointment Minimum/Maximum Lead Days and Request Minimum/Maximum Lead Days settings to allow patrons different time windows for booking new appointments in the reading room and for adding new requests to existing appointments:

  • Appointment Minimum/Maximum Lead Days: Determines how close to the current date and how far in advance of the current date that an appointment can be booked/requested for the reading room
  • Request Minimum/Maximum Lead Days: Determines how close to the appointment start date and how far in advance of the appointment start date that new requests can be associated with an existing appointment booked in the room

These settings are configured in the Status-Specific Policies table for each reading room calendar configured for appointments in the Appointment Scheduling tab of the Aeon Customization Manager.

The previous Minimum and Maximum Lead Days fields used in Aeon 5.1 will be removed from the database after updating to Aeon 5.2.

Action Required! Update Existing Status Lines and Email Templates

Sites updating from Aeon 5.1 must manually update Appointment-related email templates and status lines that were configured to use tags for the old Minimum and Maximum Lead Days fields to instead use the tags for the new fields after updating. For more information, see the Checklist for Updating Appointment Scheduling from Aeon 5.1 to 5.2. New installations of Aeon 5.2 will use the new fields by default in email templates and status lines.

New

Added two new status lines to the Aeon Customization Manager under Web Interface | Status Lines that will be displayed to patrons on the web interface after attempting to add new requests to an appointment outside of the timeframe allowed by the Request Minimum/Maximum Lead Days settings for the reading room:

  • SLRequestViolatesMinLeadDays: The web status line that appears when a request is submitted inside the Request Minimum Lead Days setting of the associated reading room
  • SLRequestViolatesMaxLeadDays: The web status line that appears when a request is submitted outside the Request Maximum Lead Days of the associated reading room
The SLInvalidAppointmentDate status line that was previously used to display this information in Aeon 5.1 has been deprecated and will no longer display to patrons on the Aeon web interface after updating to Aeon 5.2. 
New

Added a new SLEditAppointmentInvalid status line to the Aeon Customization Manager under Web Interface | Status Lines that will be displayed to patrons on the web interface when attempting to edit an appointment that has been cancelled or already occurred.

New

The Appointment Required setting configured on reading room calendars in the Aeon Customization Manager will now apply only to the individual reading rooms for which the setting is enabled instead of applying to all reading rooms on the site. Additionally, the Aeon DLL will now also properly validate and enforce the appointment requirement on the EAD Request form (EADRequest.html) according to the settings configured for the selected reading room in the Customization Manager.

Action Required!

To support this new functionality, additional web validation for the Reading Room field must be configured in the WebValidation table after updating. For instructions, see Configuring the WebValidation Table to Enforce the Appointment Requirement.

New

For multi-site instances of Aeon, the Aeon DLL will now perform additional validation when submitting requests from the Saved Requests web page (ViewUserReviewRequests.html) to ensure that the reading room selected is associated with the site value for each request:

  • If the reading room selected is not associated with the pre-existing site value for any selected requests, those requests will not be submitted and a new SLReadingRoomAssociationError status line will display explaining which requests failed validation due to the invalid reading room selection
  • If the reading room selected is associated with the pre-existing site value for any selected requests, all of those requests will be submitted and the SLSubmitUserReview status line will display indicating how many requests were successfully submitted for processing
  • If any selected requests did not have a pre-existing site value, the request(s) will be associated with the site selected from the Site dropdown when submitted

See Appointment Scheduling Web Interface for more details.

To implement this fix, please download the latest set of Aeon default web pages from the Aeon Downloads page and overwrite the KeepInReview.js file located in the js folder in your Aeon Web Directory with the updated file.
New

Appointment Scheduling 5.2 Web Pages

The feature-specific appointment scheduling pages were updated with a variety of new features and fixes to meet the latest web page accessibility requirements, provide a better experience for screen reader and keyboard-only users, and streamline the appointment scheduling process:

Implementation Instructions

  • Updated the web pages with a new fully accessible, in-line appointment scheduling interface that replaces the modal pop-up scheduler tool to provide users with an easier, more streamlined appointment booking process: 

    Aeon 5.2 Web Scheduling Interface

  • Added a Filter dropdown to the Appointments web page (ViewAppointments.html) that will allow users to filter the list on this page to display only active (upcoming, uncanceled) appointments:

    ViewAppointments Filter

  • Appointments are now sorted by newest first (i.e., the appointment with the start date furthest in the past will be listed last) on the Appointments web page (ViewAppointments.html). Users who are proxies for a researcher will now see appointments for their associated researcher(s) in addition to their own appointments on this web page by default. 
  • Added new functionality to update the Appointment field dynamically on request forms to add or remove "(required)" text according to the appointment requirement setting configured for the selected reading room in the Aeon Customization Manager
  • Added the Appointment Status field to the information displayed for each appointment on the Appointments web page (ViewAppointments.html) and on the Appointment Information web page (ViewAppointment.html)
  • Added new feature-specific DefaultRequest.html, GenericRequestManuscript.htmlGenericRequestMonograph.html, and GenericRequestSerial.html files, and their corresponding Edit files, to the appointment scheduling web pages. These files contain the appointment scheduling fields in place of the scheduled date field by default to ease the process of implementing the appointment scheduling functionality on the Aeon web pages
  • Added new feature-specific EADRequest.html and include_appointment_info_ead.html files to the appointment scheduling web pages to ease the process of implementing the appointment scheduling functionality on the EAD Request form

    For information on updating your existing EAD Request form with the new appointment fields, see Implementing 5.2 Web Page Changes.
For more information on the new features described above, see Appointment Scheduling Web Interface.
New

Added the Appointment Name and Status fields to all grids containing appointment-related information in the Aeon Client and to the information displayed for individual appointments on the Client calendar interface.

If updating from a previous version of Aeon, these fields will need to be manually added to any grids that had been customized prior to updating.
New

All fields from the Appointments database table and select fields from the ReadingRooms table (ReadingRoomName, MinAppointmentLength, MaxAppointmentLength) can now be added as merge fields to the print templates for requests and callslips (PrintRequest.docx and PrintCallslip.docx). For more information on adding these fields to the print templates, please see Appointment Scheduling Overview.

New

Added a GetAppointmentAvailabilities AJAX endpoint that will retrieve all available appointment slots for a reading room across a specified range of dates. For more information, see Appointment Scheduling AJAX Endpoints.

New

Deleting or anonymizing a user will delete all Appointment-type emails that had been sent to that user from the database.

Changed

The Appointment Rescheduled email template will now be sent automatically to the patron when an appointment is rescheduled from the Aeon web pages.

Changed

Changed the default behavior for the initial appointment start time when creating a new appointment in the Aeon Client:

  • When in the appointment calendar's Week, Month, and Agenda views, the start time will default to the beginning of the open hours defined for the selected reading room on the selected date
  • When creating a new appointment from the Request and User forms, the start time will default to the beginning of the open hours defined for the selected reading room on the current date 
  • If no open hours are defined for the selected reading room on the selected/current date, the start time will default to midnight
The appointment start time will continue to default to the time selected on the calendar interface when in the appointment calendar's Day and Timeline views.
Changed

Updated existing API endpoints to reflect new Appointment Scheduling features:

  • Updated the /api/ReadingRooms/ and /api/ReadingRooms/{id}/ endpoints to remove the deprecated Minimum and Maximum Lead Days settings from the data returned. These endpoints will now additionally return objects containing the settings configured in the reading room's Status-Specific Policies table in the Aeon Customization Manager.
  • Updated the /api/ReadingRooms/{id}/AvailableAppointments/{date} endpoint to ignore cancelled appointments when determining reading room availability and to add a new 'userStatus' parameter that will return the availability for a specified user status based on the status-specific policies configured for the reading room in the Aeon Customization Manager.  
Changed

Several improvements were made to the grid of appointments that is displayed while using the appointment association controls located on the Request form, Requests tab of the User Information form, and Request list grids in the Aeon Client:

  • Appointments are now sorted by start time with the patron's next upcoming appointment listed first
  • Added a Hide Completed/Cancelled checkbox control option that will hide all cancelled appointments and appointments that occurred in the past from the grid when checked
  • Added a column to display the information contained in the Appointment Name field for appointments in the grid
Fixed

Fixed several issues affecting the appointment scheduling web pages:

  • Removed unnecessary hidden <div> tags for the username field on include_appointment_info.html and ViewAppointments.html
  • Fixed an incorrect label for the 'ReadingRoomID' field on ViewAppointments.html that would prevent the field label from being read out to screen reader users Bug# 18913

To implement these fixes, please update your appointment scheduling web pages.

Fixed

Fixed an issue where using the Submit Request button to submit a saved request via the Actions dropdown menu or from the Request Details page would not enforce the appointment requirement for the reading room or site associated with the request. Bug# 13543

Fixed

Fixed an issue where the entire Aeon Client would become unresponsive if any appointments contained bad data. Bug# 15330

Any invalid appointment data in the Aeon database (e.g., an appointment with a start time later than its stop time or an appointment containing an improperly cased username) will now cause the appointment scheduling interfaces in the Client to display an error message directing the user to contact Atlas Support. Improperly cased usernames will no longer prevent the Appointment form from opening and will be corrected upon making and saving changes to the associated appointment. 
Fixed

Fixed an issue where an appointment could be created with invalid data and cause errors in the Aeon Client if a user created the appointment while logged into the web interface with a username containing trailing spaces or a different casing than the username associated with their user record. Bug# 15329

Fixed

Fixed an issue where appointments could not be saved using the Request form controls in the Aeon Client when the computer's time zone was set to Coordinated Universal Time (UTC). Bug# 15576

Fixed

Fixed an issue where the Appointments tab could be added to the Aeon Client using the layout customization tools even when no reading rooms were configured for appointment scheduling in the Customization Manager. Bug# 14767

Fixed

Fixed an issue where setting a Reduced Availability exception for a reading room in the Customization Manager would cause the appointment scheduling calendar on the web pages to show the entire day as unavailable no matter how many seats were still available after the exception. Bug# 16362

Fixed

Fixed an issue where a reading room could potentially be overbooked by a patron on the web under certain configuration settings. Bug# 16912

Fixed

Fixed an issue where appointments with only one associated request would display the incorrectly pluralized text "1 Requests" on the calendar in the Aeon Client. 

Fixed

Fixed an issue where changes to the name of an appointment in the Aeon Client would not be saved when the Appointment form was closed. Bug# 19121

Fixed

Fixed an issue where Appointment merge fields used in Transaction-type email templates would appear blank when emails were generated for the template. Bug# 17993


ArchivesSpace Request Fulfillment Plugin

To download and install the updated plugin, visit the ArchivesSpace Request Fulfillment via Aeon GitHub. If your ArchivesSpace repository is hosted by Atlas Systems, contact support@atlas-sys.com to request an update.
New

Updated the ArchivesSpace Request Fulfillment plugin to v20230302. This version of the plugin is only compatible with Aeon 5.2 and contains the following new features:

  • Clearer and more accessible presentation: When a record is not requestable in ArchivesSpace, the Aeon Request button will be removed and replaced by one of three customizable notes explaining why the request cannot be created
  • Support for new Archival Request box picker form: The plugin can now optionally direct users to the new box picker form, ArchivalRequest.html, which allows users to select only the boxes they wish to request rather than automatically attempting to request all boxes associated with a record
  • Additional data mapping options: The plugin supports eight new data mapping options that can be used to pull additional information from the ArchivesSpace record into the Aeon Request
For more information on these new features and options, see ArchivesSpace Request Fulfillment via Aeon.
New

Added new default and feature-specific Archival Request form web pages to the Aeon web directory to support the new plugin options. When the Archival Request form is configured to work with the plugin, clicking the Aeon Request button in ArchivesSpace will bring users to the new form containing the following new features:

  • Easier navigation: The top of the Archival Request form will display a breadcrumb trail indicating the location of the requested record in your ArchivesSpace repository to make it easier for users to navigate back and forth between Aeon and ArchivesSpace
  • Container selection: Users can use the checkbox controls next to each container/box on the Archival Request form to select the specific boxes they would like to request. An individual Aeon request will be created for each selected container when the form is submitted
  • Improved messaging: Customizable field notes will display under the name of a container on the form if it is located offsite or if it is restricted. Restricted containers will not be requestable.
  • Support for appointment scheduling fields: The Archival Request form can be configured with appointment scheduling controls so that users can associate an appointment with their request(s) directly from the form
The updated plugin will not use the Archival Request form by default. For more information on this form and for configuration instructions, see The Archival Request Form.
New

The Aeon Customization Manager's OpenURLMapping table will now contain several pre-configured, default mapping entries for the ArchivesSpace Request Fulfillment plugin to streamline the plugin configuration process. These default mappings can be changed or removed from the table as needed and will not affect any sites that do not use the ArchivesSpace Request Fulfillment plugin.

For more information on configuring OpenURLMapping table entries for the ArchivesSpace Request Fulfillment plugin, see ArchivesSpace Request Fulfillment via Aeon.
The new default mappings will be added to the OpenURLMapping table for all new Aeon installations and for existing Aeon installations upon update only if mappings were not configured for the ArchivesSpace plugin in the table prior to updating. The new default mappings will not be added to the OpenURLMapping table upon updating to Aeon 5.2 if mappings for the plugin were already configured in this table prior to updating. Pre-existing mappings for the plugin configured in the OpenURLMapping table will remain unchanged by the 5.2 update.
New

Added new AccessRestrictions and ContainerID fields to the Aeon Transactions database table. These fields can be configured in the OpenURLMapping table to import restrictions and container information from the ArchivesSpace record into the Aeon request.

See the Staff Client section below for more information on configuring these new fields in the Aeon Client. For more information on configuring OpenURLMapping table entries for the ArchivesSpace Request Fulfillment plugin, see ArchivesSpace Request Fulfillment via Aeon.

New

Added new files to the Aeon 5.2 default and feature-specific appointment scheduling web pages to support the new Archival Request box picker form:

  • Default Web Pages:
    • ArchivalRequest.html
    • DataRow_ArchivalRequestContainer.html
    • ArchivalRequest.js
  • Feature-Specific (Appointment Scheduling) Pages:
    • ArchivalRequest.html
    • include_appointment_info_no_site.html
For more information on configuring these files, see The Archival Request Form.
New

Added four new customization keys to the Aeon Customization Manager to support new plugin features:

  • ArchivalRequestContainerRestricted (Web Interface | Archival Requests)
  • ArchivalRequestOffsiteContainerMessage (Web Interface | Archival Requests)
  • ArchivalRequestOffsiteLocations (Web Interface | Archival Requests)
  • SLShowArchivalRequest (Web Interface | Status Lines)
For more information on configuring these keys, see The Archival Request Form.
Fixed

Fixed an issue where the plugin's language import field would not properly import language values from the ArchivesSpace record into the Aeon request. This field will now import the following information from the ArchivesSpace record into Aeon when it is configured as an import field for the plugin in the Aeon Customization Manager's OpenURLMapping table:

  • Archival object and resource records: The combined values of the lang_materials[*].language_and_script.language fields for the associated record will be imported
  • Accession records: The value of the language field for the associated record will be imported

Records with multiple language values will have those values imported as a semi-colon-separated list.

For more information on configuring import fields for the plugin in the OpenURLMapping table, see ArchivesSpace Request Fulfillment via Aeon.


Customization Manager

Changed

Changed certain hard-coded colors within the Customization Manager to instead adjust depending on the skin chosen by the user to provide better color contrast ratios. For example, fields that have been edited and not yet saved had been always highlighted in yellow, but will now adjust to different colors based on the selected skin.

Fixed

Fixed an issue where the WebFormValidationLinks table contained two default entries for the "AllRequests" and "ReadingRoomRequests" rule sets that used an incorrect form name to apply these rules to the EditEADRequest.html web page ("EditGenericRequestEAD").

The form name used in these entries will be changed to the proper name for the form ("EditEADRequest") for all new Aeon installations and for those updating to Aeon 5.2 from a previous version of Aeon if the default entries using the incorrect form name are still present in the WebFormValidationLinks table. If these default entries have been modified, then the form name will need to be corrected manually after updating. 

Database

New

Added new tables to the database to support new appointment scheduling features:

  • AppointmentNotes: Holds Appointment-type notes added to an appointment by staff in the Aeon Client
  • AppointmentHistory: Holds the history and tracking information for an appointment that is displayed under the History tab of the Appointment form Aeon Client
  • ReadingRoomPolicies: Holds the settings in the Status-Specific Policies grid for each reading room configured under the Appointment Scheduling tab of the Aeon Customization Manager

For details, see Aeon Database Tables.

New

Added new columns to the Appointments table:

  • CreationDate: Stores the appointment creation date
  • AppointmentStatus: Stores the current status of the appointment. Can be Unconfirmed, Confirmed, or Cancelled
  • ReminderSent: Tracks whether the Appointment Reminder email has been sent to the patron for the appointment. A value of 1 indicates that the reminder email has been sent, otherwise the value will be 0
New

Added new AccessRestrictions and ContainerID fields to the Transactions table. See the Staff Client section below for more information on these new fields.

Changed

The following changes were made to the ReadingRooms table:

  • Added the ReadingRoomDescription field
  • Moved the AppointmentRequired field from the ReadingRooms table to the new ReadingRoomPolicies table
  • Removed the MinLeadDays and MaxLeadDays fields
    • These fields have been replaced by the AppointmentMinLeadDays, AppointmentMaxLeadDays, RequestMinLeadDays, and RequestMaxLeadDays fields in the ReadingRoomPolicies table
Fixed

Fixed an issue where requests could be created with a null (empty) Transaction Status and cause issues in the Aeon Client. The Aeon Database will no longer allow a  null transaction status and will default the request to the Web Request Created status. Bug# 19511

Web Request Created is a transitory status that records the request's entry in the Transactions table. Requests are not meant to stay in this status and this status is not logged in the History or Tracking tables. If a request appears in this status in the Aeon Client after updating, please contact support@atlas-sys.com with the affected transaction number(s) for troubleshooting.
The name of this queue can be changed in the Queues tab of the Aeon Customization Manager. If the name of the Web Request Created queue was changed prior to updating, the queue that will be used as the default transaction status can be identified by locating the queue that has an internal state code of WebRequestCreated and a state code of 5. For more information on changing the names of queues and locating each queue's state code, see The Queues Table.

Email

Fixed

Fixed an issue where the From address specified on email templates would not be used when sending emails and would instead default to the value set in the LocalInfo table. The From address will now only default to the LocalInfo table value if this field is empty on the email template. Bug# 13531

Fixed

Fixed an issue where the From address would be inconsistent on emails sent from the Aeon Client and those sent from the Aeon web interface. Emails sent from the Aeon web will now have this information populated in the same way as those sent from the Aeon Client. 

Fixed

Fixed an issue where SMTP header information contained in the SMTP.config file would be overwritten by Aeon in some cases. Bug# 13531


Installing and Updating

Warning! New System Requirements

  • The IIS 6 Management Console component must be installed on Aeon Servers using Windows Server 2022 prior to performing the Aeon 5.2 server upgrade due to a known issue affecting PowerShell. For installation instructions, see Installing Required Windows Server 2022 Components for the Aeon 5.2 Update
  • Aeon Server 5.2 requires Microsoft .NET Core 2.2 or higher. The Microsoft ASP.NET Core 2.2 Runtime bundle is now required for the Aeon API and can be installed via Microsoft's websiteTo prevent disruptions in the Aeon API after updating, please ensure that this bundle is installed on the Aeon Server prior to updating to Aeon 5.2.
  • .NET Framework 4.7.2 may be required to perform the Aeon 5.2 server upgrade. See the release notes below for more information.
  • Aeon Client 5.2 requires Windows 10 or higher. Due to the WebView2 changes included in this release, the Aeon Client will not successfully install on machines using earlier versions of Windows operating systems. Attempting to install Aeon 5.2 on an incompatible operating system will cause the Aeon Client Installer to return an error stating "there is a problem with this Windows Installer package." 
New

Added several new default queues that will be installed to the Aeon Customization Manager's Queues tab for new Aeon installations:

  • Awaiting Staff Request Processing (Equivalent State: Awaiting Request Processing)
  • Item On Hold for Staff (Equivalent State: Item on Hold)
  • Item Checked Out to Staff (Equivalent State: Item Checked Out)
  • In Conservation/Preservation (Equivalent State: Item Checked Out)
  • In Cataloging (Equivalent State: Item Checked Out)
  • In Processing (Equivalent State: Item Checked Out)
  • New Reading Room Request (Equivalent State: Awaiting Request Processing)
For more information on the Aeon default queues, see The Queues Table.
Note: These queues will only be added for new Aeon installations. Existing Aeon installations updating to v5.2 from a previous version of Aeon will not have these queues installed upon updating.
New

Added several new default routing rules that will be installed to the Aeon Customization Manager's Routing tab for new Aeon installations:

  • New requests submitted by users who are currently signed into a reading room and not marked as Away will be automatically routed from Awaiting Request Processing to the new New Reading Room Request status
  • New requests submitted by users with the status 'Staff' will be automatically routed from Awaiting Request Processing to the new Awaiting Staff Request Processing status
  • Requests placed on hold for users with the status 'Staff' will automatically be routed from Item on Hold to the new Item on Hold for Staff status
  • Requests for items checked out to users with the status 'Staff' will automatically be routed from Item Checked Out to the new Item Checked Out to Staff status

For more information on:

Note: These routing rules will only be added for new Aeon installations. Existing Aeon installations updating to v5.2 from a previous version of Aeon will not have these queues installed upon updating.
New

Added the apiParentWebsite parameter to this server installation/update PowerShell scripts that can be used to modify the IIS website under which the Aeon API is installed (default value: "Default Web Site").

To modify the value of this parameter, please run the server installation/update scripts in advanced mode.
Changed

Updated the name of the default Awaiting Order Billing queue/photoduplication status to Awaiting Order Payment for new Aeon installations. The name of this queue will remain unchanged for sites updating from a previous version of Aeon.

Changed

The server installation/update PowerShell scripts are now signed with the Atlas code signing certificate, removing the need to set the system execution policy to "unrestricted" prior to running the scripts. 

Changed

Non-administrator user accounts on the Aeon Server can now run the server installation/update PowerShell scripts, removing the need to log into the server with an administrator account prior to opening PowerShell.

Note: PowerShell must still be opened via the Run as administrator option.
Changed

Increased the Internet Information Services (IIS) maxQueryString value set by the server installation PowerShell scripts to 4096 characters in order to prevent issues caused by OpenURL query strings that exceeded the previous default allowance of 2048 characters.

Changed

The following files used by the Aeon DLL are now installed to C:\Program Files (x86)\Aeon\WebDependencies by default instead of to the Aeon web directory (default location: C:\Program Files (x86)\Aeon\Web) in order to prevent these files from being removed or overwritten when changes are made to the web pages:

  • AtlasSystems.Interop.SpreadsheetGear.dll
  • AtlasSystems.Security.dll
  • AtlasSystems.Security.Interop.dll
  • log4net.dll
  • SpreadsheetGear2017.Core.dll
  • SpreadsheetGear2017.Drawing.dll
The default installation path for these files can be modified by changing the value in the webDependenciesDirectory parameter when running the server installation/update scripts in advanced mode.

If upgrading from a previous version of Aeon, a legacy copy of these files will remain in your web directory after updating (default location: C:\Program Files (x86)\Aeon\Web). As a best practice, these legacy files can be deleted once your upgrade is complete:

  1. After upgrading Aeon, confirm that the DLL files listed above have been installed in the WebDependencies folder (default location: C:\Program Files (x86)\Aeon\WebDependencies
  2. Locate and delete the legacy copies of the DLL files listed above from the Aeon web directory (default location: C:\Program Files (x86)\Aeon\Web)

    Warning! Please do not delete aeon.dll from this folder
Changed

Removed the SQL Server Native Client component from the Aeon 5.2 server hardware and software requirements due to the end of support for this component by Microsoft. The Aeon server will now use the Microsoft OLE DB Driver for SQL Server in place of the SQL Server Native Client.

The Microsoft OLE DB Driver for SQL Server will be installed by the Aeon 5.2 server installation/update scripts and does not need to be installed separately. 
Changed

The server installation/update PowerShell scripts will now use the SQL Server PowerShell Module during the Aeon 5.2 update/installation process. The scripts will use whichever version of the module is currently installed on the Aeon Server, if present. If the module is not yet installed on the Aeon Server, then the latest version of the module (v22.0.59) will be installed during the server installation/update process.

The most recent version of the SQL Server PowerShell Module (v22.0.59) requires that .NET Framework 4.7.2 or higher is installed on the Aeon Server. An error will be returned during the server update/installation process if the .NET Framework version is insufficient. For more information, see Resolving SQL Errors During the Aeon 5.2 Server Update.

Staff Client

New

Added support for the Microsoft Edge WebView2 embedded browser within the Aeon Client.

For more information on the impact of this change, please see the WebView2 entry in the Addons section of the release notes above.
New

Added support for setting Transaction context type custom field values when creating requests from file in the Aeon Client.

The column name for the Transaction type custom field in the Excel spreadsheet should be configured to match the short name defined for the field in the CustomFieldDefinitions table.
User and Activity context type custom fields are not supported for use with this feature. 
New

New Access Restrictions and Container ID text fields are now available to add on the Request form in the Aeon Client and on web request forms in the Aeon web interface. These fields are also available as merge fields for print templates. 

Note: These fields are not available on the Request form by default and must be added manually using the staff layout customization feature. For more information on this feature, see Creating and Assigning Templates to Staff Users.

These fields can be added to your web forms using the following code:

Access Restrictions:

<div class="form-group col-md-8">
<label for="AccessRestrictions">
<span class="<#ERROR name='ERRORAccessRestrictions'>">
Access Restrictions
</span>
</label>
<input type="text" class="form-control" name="AccessRestrictions"
id="AccessRestrictions" value="<#PARAM name='AccessRestrictions'>">
</div>

Container ID:

<div class="form-group col-md-8">
<label for="ContainerID">
<span class="<#ERROR name='ERRORContainerID'>">
Container ID
</span>
</label>
<input type="text" class="form-control" name="ContainerID"
id="ContainerID" value="<#PARAM name='ContainerID'>">
</div>
Changed

Updated the Aeon Citation control located within the Z39.50 search interface on the Request form used to display citation information in rich text format.

Changed

For enhanced security, an entry will no longer be added to the User Change History on the User form when a user's password is changed.

Changed

Changed certain hard-coded colors within the Client to instead adjust depending on the skin chosen by the user to provide better color contrast ratios. For example, fields that have been edited and not yet saved had been always highlighted in yellow, but will now adjust to different colors based on the selected skin.

Changed

Extra spaces are now trimmed from the username saved to the database when creating a new username or updating an existing username for a user in the Aeon Client.

Fixed

Fixed an issue where filtering or sorting requests in the grid view by either the appointment Start Time or Stop Time fields would break the results. Bug# 14166

Fixed

Fixed an issue where the current date could not be selected when adding attendance count to an activity. Bug# 13930

Fixed

Fixed an issue where request callslips could not be printed from an Activity Information record if any custom fields were defined in the Customization Manager's CustomFieldDefinitions table. Bug# 14570

Fixed

Fixed an issue where refreshing the Client would sometimes throw a multithreading error in the Client logs and lead to slowness issues. Bug# 16762

Fixed

Fixed an issue where the Client would sometimes attempt to use a bad database connection when refreshing user or reading room information. Bug# 17093

Fixed

Fixed an issue where any custom fields added to a custom tab group created on the Request, User, or Activity Information form would display highlighted yellow. Bug# 15993

Fixed

Fixed an issue where leaving the FutureRoutingDays customization key value blank would cause errors when attempting to import requests from file. Bug# 15791

The FutureRoutingDays key will now default to a value of -1 when left blank or when set to a non-numeric value and cause requests to immediately enter the Awaiting Request Processing status.
Fixed

Fixed a formatting error in the Aeon Client log entry added when a user signed into a reading room is set to away. Bug# 19730

Fixed

Fixed an issue where the controls located within the Aeon Options form were not aligned properly within the borders of each section of options on the screen. Bug# 18418


Staff Manager

Changed

Changed certain hard-coded colors within the Staff Manager to instead adjust depending on the skin chosen by the user to provide better color contrast ratios. For example, fields that have been edited and not yet saved had been always highlighted in yellow, but will now adjust to different colors based on the selected skin.

Changed Extra spaces are now trimmed from the username saved to the database when creating a new username or updating an existing username for a user in the Staff Manager.
Fixed

Fixed an issue where trailing and leading spaces would not be trimmed from the Username, First Name, and Last Name values when creating and/or editing staff users. Bug# 16655


System Manager

Changed

The setup and update installer files downloaded by the System Manager and used to auto-update the Aeon Client when a new version is available will now be placed in separate Install and Update subfolders within the AeonUpdates\Client folder in the web directory (default location C:\Program Files (x86)\Aeon\Web\AeonUpdates\Client).

For more information on this process, see "Obtaining the Client Installer Files" in Aeon System Manager.

Fixed

Fixed issues where the System Manager would not detect newly created or modified custom queues and fields for use with addons until the service was restarted. The System Manager will now check the Queues and CustomFieldDefinitions tables in the Aeon Customization Manager for changes and use the most up-to-date custom field and queue configurations each time an addon runs. Bug# 18405/Bug# 15370


Web Interface

New

The date picker calendar used for the Scheduled Date field in the default Aeon web pages has been updated to a significantly more accessible version for screen reader and keyboard-only users. In addition to the calendar's new accessibility features, unavailable dates will now be crossed out and displayed with a grey background:

Accessible Scheduled Date Calendar

As part of this change, the default web pages were also updated to remove the hardcoded Scheduled Date field on each request form and instead implement this field using new include_scheduled_date.html and include_scheduled_date_ead.html files. 

For complete details and instructions on implementing the new calendar tool in the Aeon default web pages, please see Implementing 5.2 Web Page Changes.

Updating Custom Fields

The updated date picker calendar can also be implemented for any custom Date fields used on your Aeon web forms. For instructions on updating the calendar tool for custom Date fields previously implemented on your forms in Aeon 5.1, see Updating the Date Picker Calendar Used for Custom Date Fields on Web Forms (Aeon 5.2 Web Pages). For instructions on implementing a custom Date field on your Aeon web forms from scratch, see Adding Custom Fields to Web Forms.

New

Several additional changes were made to the default web pages. The new web pages are not installed automatically to prevent overwriting any customizations your institution may have created. The complete set of v5.2 web pages are available for download on the Aeon Downloads page. For more information on implementing these changes, see Implementing 5.2 Web Page Changes:

  • Fixed an issue where hidden billing fields on request forms (such as those hidden by a customized photoduplication toggle on the EAD Request form) could become enabled and prevent submission of the form Bug# 16440
  • Removed unnecessary hidden inputs and <div> tags for the username field from various web pages to improve the efficiency of the code Bug# 13641
  • Fixed an issue where fields marked with the "data-persisted-value" attribute would not persist their values in the Safari web browser
  • Removed an unnecessary "required" attribute from the ItemSubTitle field on EditEADRequest.html Bug# 18920
  • Corrected outdated information on the default FAQ page regarding web browser and cookie requirements for using the Aeon web pages Bug# 18264
  • Added missing 'type' attributes to buttons used in various places on the Aeon web interface to fix issues including those where order payments sometimes would not be correctly processed through a payment provider gateway (Bug# 13028) and where all requests could be inadvertently selected on the Saved Requests web page without being announced to the user (Bug# 19801)
  • Improved color contrast against the default Aeon web pages for several buttons and dropdown menu items in the DataRow template files
  • Fixed a broken 'aria-labelledby' attribute on webAlerts.js to address an accessibility issue affecting the modal dialog for web alerts Bug# 18686
  • Removed a broken 'aria-describedby' attribute affecting the 'Current Password' field on ChangePassword.html Bug# 18687
  • Changed the default color used for hyperlinks added to the cookie consent banner to address contrast issues Bug# 18486
  • Changed the default label color used for fields that fail server validation when a form is submitted to address contrast issues against the default web page background colors Bug# 18758
  • Added additional formatting for the search box on ViewSearchResults.html to address color contrast issues and to improve the layout of the web page for a better user experience Bug# 19937
  • Fixed an issue where the transaction menu (include_TransactionMenu.html) was not fully visible on smaller display sizes and added an underline on hover to its enabled menu buttons for better consistency with other buttons on the Aeon web pages Bug# 18917
  • Realigned the Actions menu dropdown options contained in the DataRow template files to fix an issue where this menu was not fully visible on smaller display sizes Bug# 18915
  • Fixed an issue where text was not properly responsive and could become unreadable on some web pages when viewed on smaller display sizes/high zoom levels 
  • Updated the hardcoded copyright year on Logon.html to 2023
  • Added Transaction Number and Site information to requests displayed on the Saved Requests web page
New

Added a new WebHomePage customization key (located in the Aeon Customization Manager under Web Interface | Defaults) that can be used to set the home page of the Aeon web interface to one of three options:

  • Outstanding Requests (ViewOutstandingRequests.html)
  • View Appointments (ViewAppointments.html)
  • Main Menu (MainMenu.html) - Pre-existing Aeon Installations Only
For more information, see Configuring the Aeon Home Page.
The web page set as the home page will display wherever the Main Menu had previously been shown by default when using the Aeon web interface (e.g., upon logging in, upon submitting a new request, etc.). 

MainMenu.html has been deprecated and removed from the default web pages as part of this change:

  • New Aeon installations will have the WebHomePage key default to Outstanding Requests
  • Existing Aeon sites upgrading from a previous version of Aeon will have the WebHomePage key default to Main Menu until the value of the key is changed to either Outstanding Requests or View Appointments
    • Note that updating to Aeon v5.2 will not remove MainMenu.html from your web directory, but that this page will not be supported in future web page updates if it is kept as the Aeon home page
New

Added a WebCookieSameSite customization key to the Aeon Customization Manager under Web Interface | System that will set the SameSite property value on the Aeon session ID cookie in order to fix an issue where users would be forced to log back into the Aeon web interface when submitting requests from an external website (i.e., from a website outside of the Aeon web pages, such as a library catalog or finding aid).

For more information on configuring this key, see Configuring Login Persistence Options for External Websites.

The default value of this key will be set to None, which will set the SameSite cookie property to None, allowing users to skip the Aeon login screen when requesting from an external website using an HTTPS connection or when requesting from an external website using an HTTP connection that is hosted under the same domain as your Aeon web pages.
This key will not set the SameSite value on session cookies generated by the Atlas Authentication Portal. A new version of the Atlas Auth Portal is now available that will handle setting the SameSite property on this cookie once implemented. If you are using the Atlas Auth Portal on your web pages, please see the Atlas Authentication Portal v1.3.2 release notes below for update instructions and for more detailed information on this new feature.
Changed

Changed the web page redirect behavior when submitting requests from the Saved Requests page:

  • If all selected requests were submitted successfully, the user will be redirected to the Aeon home page and a status line will display indicating that the requests were submitted for processing
  • If any of the selected requests could not be submitted (e.g., due to validation errors, an unmet appointment requirement, request limit constraints, etc.), the user will be redirected back to the Saved Requests page and status lines will display indicating which requests were successfully submitted and which requests failed submission 
Fixed

Fixed an issue where the <#OPTION> web tag could not be used to automatically generate a list of checkbox options for CustomDropDown type custom fields on web forms. Bug# 14532

For more information on configuring this feature using custom fields, see Automatically Generate Checkbox Selections for a CustomDropDown Group.
Fixed

Fixed an issue where the web pages would display a blank space if no title was provided for an item, causing issues for screen readers. Bug# 17579

The web pages will now display the text configured in a new WebNoTitleText customization key added to the Aeon Customization Manager under Web Interface | Defaults. The default value is [No Title Provided].
Fixed

Fixed an issue where the Request For dropdown on request forms was not properly validated to ensure that the researcher or activity selected was associated with the user submitting the request. Bug# 11699

Fixed

Fixed an issue where cloning a photoduplication request on the web would create a non-photoduplication request. Bug# 14459

Fixed

Fixed an issue where status lines would not display on photoduplication request pages when accessed using the Clone to Copy button. Bug# 15485

16 May 2023 (1.3.2) Atlas Authentication Portal Release

Atlas Authentication Portal version 1.3.2 was released on May 16th, 2023. This release includes several changes to the session cookie generated by the Atlas Auth Portal upon login that will allow Aeon to persist the user's login when placing requests through the portal from an external website (i.e., from a website outside of the Aeon web pages, such as a library catalog or finding aid) in most instances.

Atlas Auth Portal 1.3.2 requires .NET Framework 4.7.2 or greater, which is higher than the minimum .NET framework version required by the Aeon Server. Please ensure that the upgraded version of this component is installed on the Aeon Server prior to upgrading to/installing Atlas Auth Portal v1.3.2.

Update Instructions

The Atlas Auth Portal files can be obtained from the Aeon Downloads page. For step-by-step instructions on implementing the 1.3.2 release, see Atlas Auth Portal 1.3.x Release Configuration.

New 

The session cookie generated by the Atlas Auth Portal will now include SameSite and Secure properties that will allow Aeon to persist the user's login when placing requests through the portal from an external website (i.e., from a website outside of the Aeon web pages, such as a library catalog or finding aid) in most instances. By default, the SameSite and Secure cookie properties will be set as follows:

  • When a user places a request from an external website using HTTPS:
    • The SameSite property on the session cookie will be set to None and the Secure property set to True allowing currently logged-in Aeon users to skip the Atlas Auth Portal login page when placing the request
  • When a user places a request from an external website using HTTP: 
    • The SameSite property on the session cookie will be set to Lax and the Secure property set to False allowing currently logged-in Aeon users to skip the Atlas Auth Portal login page when placing the request only if the external website is under the same domain as the Aeon web pages. If the external website is not under the same domain, then the user will need to log back into the Aeon system to place the request.
For more information, see Using an Authentication Portal Landing Page.

06 July 2023 (5.2.4) Aeon Server/Web DLL & (5.2.2) Server Installer Scripts Release

The Aeon Server has been updated to a new version (v5.2.4) to install a new version of the Web DLL (v5.2.4) that will implement new configuration options to prevent bot-driven account creation spam through the user registration pages on the Aeon web interface. This release also includes new options for configuring a photoduplication toggle on web request forms and important appointment scheduling bug fixes. The Aeon Server Installer Powershell scripts have also been updated to v5.2.2 and must be used to perform the server update. 

Update Procedure

The newest version of the Web DLL will be installed when updating to v5.2.4 of the Aeon Server. Please perform or request a server update to implement the updated DLL.

Note: Self-hosted sites will need to visit the Installing the Aeon Server page and download the new Aeon v5.2.2 Server Installer Powershell scripts to perform this update. The new installer scripts will include an additional prompt to determine if the SQL connection is encrypted when running the update. 
New

The following new configuration options are available for the Aeon web interface to prevent bot-driven spam account creation via the New User Registration form (NewUserRegistration.html):

  • Aeon can now integrate with one of three supported third-party captcha providers to add a captcha challenge requirement to the New User Registration form (NewUserRegistration.html). The captcha challenge will provide extra security against bot-driven account creation by requiring new users to solve the challenge in order to submit the form and create their accounts. The following captcha providers and plans are supported by Aeon (note that a separate account must be created with your chosen captcha provider to implement this feature): 

    • Google reCAPTCHA: reCAPTCHA v2 (both the "invisible" and "checkbox" variants) and reCAPTCHA v3
      • Note that reCAPTCHA Enterprise is not supported by Aeon
    • hCaptcha: Free "Publisher" plan
    • MTCaptcha: Free plan
  • As an alternative to implementing the captcha requirement, user registration can now be completely disabled for accounts created through standard Aeon authentication (AeonAuth) from the New User Registration form (NewUserRegistration.html) using the new AeonAuthUserRegistrationEnabled customization key. This option will prevent the creation of spam accounts by completely blocking account creation for users who are not pre-authorized for an Aeon account via an Aeon Exclusive, LDAP, PatronAPI, or Remote Authentication configuration. This option should not be chosen if you only allow users to register for accounts through the standard Aeon account creation and authentication process.
For complete details and configuration instructions for these options, please see Preventing Account Creation Spam in Aeon.
New

Added the following new customization keys to the Aeon Customization Manager to support the new spam prevention options in the Aeon web interface:

  • AeonAuthUserRegistrationEnabled: Determines if new user registrations can be created via standard Aeon authentication (AeonAuth)
  • SLUserRegistrationDisabled: The web status line that appears if registration has been disabled using the AeonAuthUserRegistrationEnabled key
  • CaptchaProvider, CaptchaSecret, CaptchaSiteID: These keys are used to configure the captcha integration for the user registration form
  • SLCaptchaFailure: The web status line that appears if a user fails the CAPTCHA challenge during user registration.
New

Added the <#CAPTCHA> web DLL tag to the Aeon web interface. This tag is used to display the captcha challenge requirement on the New User Registration form (NewUserRegistration.html) when a captcha integration has been configured in the Aeon Customization Manager. 

For more information on this tag, see Aeon CAPTCHA Tag.
New

Added new options for configuring a photoduplication toggle control on Aeon request forms. The photoduplication toggle control will allow patrons to toggle between submitting a reading room request or a photoduplication request from the request form(s) on which it has been configured:

  • Add the PhotoduplicationEnabled customization key to the Aeon Customization Manager under Web Interface | System. When set to Yes, this key will display the photoduplication toggle control on any requests form on which the <#PHOTOTOGGLE> tag has been configured. The default value for this key is No.
  • Added the <#PHOTOTOGGLE> web DLL tag to the Aeon web interface that is used to display content on the web form based on the setting configuring in the PhotoduplicationEnabled key:
    • When the PhotoduplicationEnabled customization key is set to Yes, the <#PHOTOTOGGLE> tag will display the photoduplication toggle control and either the reading room request fields or the photoduplication request fields (based on the request type selected by the user in the toggle control) configured in the new include_photodup_toggle_enabled.html HTML file
    • When the PhotoduplicationEnabled customization key is set to No, the <#PHOTOTOGGLE> tag will only display the reading room request fields configured in the new include_photodup_toggle_disabled.html HTML file
    Note: The new HTML files are available in the Aeon 5.2.4 default/feature-specific web pages release. To learn how to update your web pages to support the <#PHOTOTOGGLE> feature, see the 5.2.4 web page release notes below.
Changed

Users will no longer be able to register for an Aeon account from the TestWeb directory to prevent bot-driven spam account creation from the Aeon TestWeb web pages. TestWeb user registration will be disabled by default upon update and cannot be re-enabled.

Fixed

Fixed an issue where users could not view appointment details on the Aeon web interface for appointments with start dates in the past or with start dates exceeding the Minimum Lead Days setting for the reading room. Bug# 22857

Fixed

Fixed an issue where appointments were sometimes visible to unrelated users on the Aeon web interface. 

Fixed

Fixed an issue where the Aeon DLL would sometimes apply the incorrect set of appointment scheduling policies configured for the reading room in the Aeon Customization Manager when users booked or managed their appointments through the Aeon web interface.

06 July 2023 (5.2.4) Default and Feature-Specific Web Pages Release

New versions of the default and feature-specific web pages have been released to implement captcha support on the New User Registration form and to make several important bug fixes. The Archival Request form has also been updated to include the new <#PHOTOTOGGLE> functionality included in the Aeon Server v5.2.4 release.

The new default and feature-specific web pages are available for download on the Aeon Downloads page. To implement these changes:

  • Download the new Aeon v5.2.4 default and feature-specific (if using appointment scheduling features) web pages and replace your existing pages. 
  • If you have customizations, find and replace the code changes in Implementing 5.2 Web Page Changes.
New

Modified NewUserRegistration.html to include the new <#CAPTCHA> tag and added the following new files to the default web pages to implement captcha support on the New User Registration form:

  • include_captcha_none.html
  • include_hcaptcha.html
  • include_mtcaptcha.html
  • include_recaptcha_v2_checkbox.html
  • include_recaptcha_v2_invisible.html
  • include_recaptcha_v3.html
For more information on configuring these changes, please see Preventing Account Creation Spam in Aeon.
Note: The Aeon Server must be updated to v5.2.4 following the server update instructions above before the new captcha web pages can be used to implement the captcha requirement on the New User Registration form.
New

The following web pages changes were made to implement support for the new <#PHOTOTOGGLE> functionality on ArchivalRequest.html and to make this feature available for configuration on other request forms:

  • Removed the feature-specific version of ArchivalRequest.html available in the appointment scheduling web page package and updated the default version of this file in the Aeon default web pages package to include the new <#PHOTOTOGGLE> tag. The default version of this file is now used for both Aeon installations using appointment scheduling features and Aeon installations not using these features.
  • Added new include_photodup_toggle_disabled.html and include_photodup_toggle_enabled.html files to both the default web pages and feature-specific appointment scheduling web pages. These files will be used to display content on the form when the photoduplication toggle functionality provided by the <#PHOTOTOGGLE> tag is disabled and enabled (respectively) in the Aeon Customization Manager.
  • Added a new include_photoduplication_archival_request.html file to the default web pages. This file is used to display the photoduplication fields on the request form when the photoduplication toggle functionality provided by the <#PHOTOTOGGLE> is enabled in the Aeon Customization Manager and a photoduplication request is selected by the user via the toggle option on the web form.
  • Updated the appointments.jsbillingAccountsOptionHandler.jsbillingContextHandler.js, duplicationPermissionToggle.js, and include_appointment_info_no_site.html files to support the new <#PHOTOTOGGLE> tag.
For more information on configuring these changes, please see Implementing 5.2 Web Page Changes.
Note: The Aeon Server must be updated to v5.2.4 following the server update instructions above before the new web pages can be used to implement the new photoduplication toggle features.
Fixed

Fixed an issue where clicking the Schedule a New Appointment button from the Aeon web pages would sometimes not display the appointment scheduling fields.

Fixed

Modified the Request For field on several web forms so that usernames are now consistently hidden within the list of users displayed in the dropdown selection across all web pages.

06 July 2023 (5.2.2) Client Release

The Aeon 5.2 Client has been updated to a new version in order to fix bugs affecting email templates and appointment scheduling functionality.

Update Procedure

Follow the Client Automatic Updater prompts within the Aeon Client, or download and run the 5.2.2 Client Installer from the Aeon Downloads page to install the new client applications.

Client Application Updates

Performing the Aeon Client update process will install the following new application versions:

  • Client v5.2.2
  • Customization Manager v5.2.2
  • Staff Manager v5.2.2
Changed

The Hide Completed/Cancelled checkbox option used with the appointment association controls located on the Request form, Requests tab of the User Information form, and Request list grids in the Aeon Client will no longer hide appointments currently in progress when checked. Appointments will now only be considered completed and hidden once the appointment's stop time is reached.

Fixed

Fixed an issue where Reply To addresses configured for email templates in the Aeon Customization Manager would not be added to emails generated by the Aeon Client.

Fixed

Fixed an issue where the <#Request.CancelNote> tag in the ItemCancellation email template would not be populated with a value for emails generated by the Aeon Client. Bug# 22789

12 July 2023 (5.2.3) Client Release

The Aeon 5.2 Client has been updated to a new version in order to fix an issue affecting email templates after the 5.2.2 update.

Update Procedure

Follow the Client Automatic Updater prompts within the Aeon Client, or download and run the 5.2.3 Client Installer from the Aeon Downloads page to install the new client applications.

Client Application Updates

Performing the Aeon Client update process will install the following new application versions:

  • Client v5.2.3
Fixed

Fixed an issue where tags used to populate the ItemCancellation email template with information about the user's request would not be generated with values for emails sent by the Aeon Client.

28 August 2023 (5.2.5) Aeon Server/Web DLL Release

The Aeon Server has been updated to a new version (v5.2.5) to install a new version of the Web DLL (v5.2.5) that will implement a bug fix for appointment scheduling functionality on the Aeon web interface.  

Update Procedure

The newest version of the Web DLL will be installed when updating to v5.2.5 of the Aeon Server. Please perform or request a server update to implement the updated DLL. Atlas-hosted sites should contact Atlas Support (support@atlas-sys.com) to schedule their server update. 

Note: Self-hosted sites must use the v5.2.2 of the Aeon 5.2 Server Installer Powershell scripts (available from the Installing the Aeon Server page) released with the previous version of the Aeon Server to perform this update. The 5.2.2 server update will not appear if using a prior version of the installer scripts to attempt the update.
Fixed

Fixed an issue in Aeon Web DLL where the last appointment availability for any month would incorrectly show as unavailable on the web if the associated reading room was configured to only offer all-day appointments. 

16 October 2023 (5.2.6) Default and Feature-Specific Web Pages Release

New versions of the default and feature-specific web pages have been released to make several minor fixes and improve the user experience on the Aeon web interface.

The new default and feature-specific web pages are available for download on the Aeon Downloads page. To implement these changes:

Fixed

Fixed various minor issues on the default web pages and the feature-specific web pages used with appointment scheduling functionality. The list of changes can be found below. For more information on implementing each fix, see Implementing 5.2 Web Page Changes

  • Removed unused image files from the images folder in the default web pages
  • Standardized the column widths used for the ItemEdition, ItemVolume, and ItemIssue field text inputs on the default and feature-specific edit form for monograph requests (EditGenericRequestMonograph.html) to match the widths for these inputs on the monograph request form (GenericRequestMonograph.html
  • Removed extraneous spaces from the code used in the edit forms for manuscript and monograph photoduplication requests (EditGenericRequestManuscriptPhotodup.html and EditGenericRequestMonographPhotodup.html) and from the code used in the default photoduplication request form (PhotoduplicationRequest.html)

07 February 2024 (5.2.6) Aeon Server/(5.2.7) Web DLL/(5.2.3) System Manager & (5.2.4) Client Release

The Aeon Server has been updated to a new version (v5.2.6) to install a new version of the Web DLL (v5.2.7) and System Manager (v5.2.3), and the Aeon Client has been updated to a new version (v5.2.4) to provide several bug fixes for appointment scheduling, addon, and email functionality.

Update Procedure (these steps can be performed in any order)

Atlas-hosted sites can see the Aeon Update Procedures and Best Practices for Atlas-Hosted Sites article for more information on minor point release update procedures.

  1. The newest versions of the Web DLL and System Manager will be installed when updating to v5.2.6 of the Aeon Server. Please perform or request a server update to implement the updated DLL/System Manager. Atlas-hosted sites will be contacted by Atlas Support (support@atlas-sys.com) to schedule their server update. 

    Note: Self-hosted sites must use the v5.2.2 of the Aeon 5.2 Server Installer Powershell scripts (available from the Installing the Aeon Server page) released with Aeon Server v5.2.4 to perform this update.
  2. Follow the Client Automatic Updater prompts within the Aeon Client, or download and run the 5.2.4 Client Installer from the Aeon Downloads page to install the new client applications.

Server Component Updates

Performing the Aeon Server update process will install the following new component versions:

  • DLL v5.2.7
  • System Manager v5.2.3
Changed

Updated the MS OLEDB SQL driver installed by the Aeon Server Installer/Update scripts to v19.3.2 for enhanced security.

Changed

Updated the scripting used by the Aeon System Manager to the latest version.

Fixed

Fixed an issue where the username associated with a user's record could potentially be stored in the Aeon Database using different casings when creating appointments for a researcher in the web interface, which could cause an error loading appointments in the Aeon Client. Bug# 25322

Client Application Updates

Performing the Aeon Client update process will install the following new application versions:

  • Client v5.2.4
  • Customization Manager v5.2.3
Fixed

Fixed an issue where the username associated with a user's record could potentially be stored in the Aeon Database using different casings when manually cloning requests, which could cause an error loading appointments in the Aeon Client. Bug# 25322

Fixed

Fixed an issue where tags used to import information from the Aeon database into emails (e.g., <#System.GeneralEMailAddress>) would not import the correct value when configured in the From or Reply To fields on email templates. Bug# 23764

Fixed

Fixed an issue where changing the status of an appointment in the Aeon Client would save any other changes made to the information on the appointment form without enforcing data validation, which could lead to an error loading appointments in the Client if an invalid End Date was entered for an appointment. Bug# 26376

Fixed

Updated the scripting used by the Aeon Client and Customization Manager to fix an issue affecting addons using WebView2 browsers where closing a request form for a request using the WebView2 browser and subsequently searching for a new request in the Aeon Client could open the previous request instead of the one for which the search was performed. Bug# 24181

 

Questions?

If this article didn’t resolve your issue, please contact Atlas Support for assistance:

Contact Support