Skip to main content

Aeon 6.0 Release Notes

Important Update Information​

Released May 15th, 2024

Highlights​

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

  • Lightweight Web-based Staff Client

There are over 15 bug fixes and several underlying component updates in this release.

Considerations Before You Update​

info

Review Aeon v6.0 FAQ​

For frequently asked questions and additional information regarding the 6.0 features and fixes, please see the Aeon 6.0 FAQ. You can also view the recording of the 6.0 pre-release webinar from May 7th, 2024, and the recorded demo for the new Staff Web Client from the February 2024 Aeon User Group meeting in the VTL. 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 6.0. For specific instructions on updating, see Updating Aeon to the Newest Version.

Warning! New System Requirements

Action Required: Changes to the Aeon API URL

The Aeon API will now be installed to a new default location in IIS during the server update and will use the following API URL: https://servername/AeonApi/. This is the new default installation path for the API and this URL cannot be customized. Previous installations of the Aeon API will be removed during the server update process. To prevent disruptions in API-based integrations after updating, please ensure that these integrations are updated to point to the new base URL for the Aeon API (https://servername/AeonApi/) during or directly after performing the Aeon 6.0 server upgrade.

Caiasoft integrationswill be updated automatically during your Aeon 6.0 server upgrade. Please contact support@atlas-sys.com if you have any questions or experience issues after updating to Aeon 6.0.

Action Required: Update Addons

This update removes support for the embedded Chromium browser from the Aeon Desktop Client. To prevent compatibility issues after updating, please ensure that browser-based client addons have been updated to versions supporting WebView2. See the Addons section below for details.

Aeon 6.0 Web Page Update Information

The Aeon 6.0 default and feature-specific web pages include all the latest changes and fixes first released in the Aeon v5.2.11and Aeon v5.2.13default and feature-specific web pages. The Aeon5.2.11 web page update included the removal of the jQuery UI JavaScript Library from the Aeon web pages for security purposes.It is highly recommended to update your web pages to implement this change to ensure the best possible security on the Aeon web interface.

To update your web pages:

info

Point Releases​

Bug fixes and new features are added periodically as point releases. See 6.0.x point releases below:

  • 03 July 2024 (6.0.10) Default & Feature-Specific Web Pages Release
  • 11 July 2024 (6.0.3) Desktop Client Release
  • 03 September 2024 (6.0.4) Desktop Client Release
  • 29 May 2025 (6.0.4) Aeon Server/(6.0.1) Web DLL Release

For a list of current known issues, see UserVoice.

Aeon 6.0 Features & Fixes​

Aeon API | Addons | Administrative | Appointment Scheduling | Database | Email | Installing and Updating | Staff Desktop Client | Staff Web Client | Web Interface

Aeon API​

danger

Action Required: Changes to the Aeon API URL

The Aeon API will now be installed to a new default location in IIS during the server update and will use the following API URL: https://servername/AeonApi/. This is the new default installation path for the API and this URL cannot be customized. Previous installations of the Aeon API will be removed during the server update process. To prevent disruptions in API-based integrations after updating, please ensure that these integrations are updated to point to the new base URL for the Aeon API (https://servername/AeonApi/) during or directly after performing the Aeon 6.0 server upgrade.

Caiasoft integrationswill be updated automatically during your Aeon 6.0 server upgrade. Please contact support@atlas-sys.com if you have any questions or experience issues after updating to Aeon 6.0.

warning

Action Required: New System Requirements for the Aeon API

The Microsoft ASP.NET Core 8.0 Runtime Bundle is now required for the Aeon API. This bundle can be installed via Microsoft's website:

  • To prevent disruptions in the Aeon API after updating, pleaseensure that this bundle is installed on the Aeon Server before updating to Aeon 6.0.
  • Once the update has been run, Microsoft .NET Core 2.2 should be manually removed from the server, if present, as .NET Core 2.2 has been deprecated by Microsoft and is no longer receiving security updates. See Microsoft's documentation for instructions on this process.
NewChanged the default URL for the Aeon API from https://servername/aeon/api/ to https://servername/AeonApi/. The Aeon 6.0 API will be installed to this new default path in IIS during the 6.0 server update. This installation path isnot customizable.




:::danger

See the Action Required: Changes to the Aeon API URL note above for for more information on the impact of this change.

:::
NewThe Aeon API now uses the Microsoft .NET 8 framework in place of the deprecated Microsoft .NET Core 2.2 framework used in previous API versions for enhanced security.




:::warning

See the Action Required: New System Requirements for the Aeon APInote above for more information on the impact of this change.

:::
NewUsers can now authenticate to the Aeon API with their Aeon staff accounts through the generation of staff tokens via several new Token endpoints. This method allows users to use the API directly or through a third-party application without needing an Aeon API key. When this method of authentication is used:

  • Actions taken by users via the API will be attributed to their username in the History and Tracking tables, instead of to the "System."

  • Certain API endpoints will be restricted only to users with specific permissions (as configured for the user's staff account in the Aeon Staff Manager).

  • Time-based authentication will be enforced via access and refresh tokens (as opposed to API key authentication, which never expires).





:::tip

For more details on the new Token endpoints and the staff token authentication process, see Aeon API.

:::






:::warning

The new Token endpoints replace the Token endpoint used in the Aeon 5.1 and 5.2 API which has been deprecated due to timeout issues.

:::
NewIn addition to the new Token endpoints noted above, significantly expanded the functionality of the Aeon API through the addition of new endpoints, including:

  • An Activities endpoint used to retrieve a list of activities.


  • Appointments endpoints used to manage appointments and appointment notes and retrieve appointment history.


  • Customization endpoints used to retrieve customization key and CustomDropDown table values configured in the Aeon Customization Manager.


  • Emails endpoints used to retrieve and send emails.

  • New ReadingRoom endpoints used to retrieve reading room history, retrieve currently signed-in users, sign a user into or out of a reading room, and to update a signed-in user's status to present or away.


  • Sites endpoints used to retrieve a list of sites and to manage the site groups configured in the Aeon Web Client.


  • Staff endpoints used to retrieve a list of staff accounts and manage site groups and profiles assigned to staff users in the Aeon Web Client.


  • Users endpoints used to create users, update user records, retrieve user history and images, manage a user's notes, set a user's clearance status, and change a user's password.


  • WebSession endpoints used to manage a web session for a specific user.





:::tip

Developers can find the complete documentation for new and existing API endpoints in the Aeon Swagger documentation.

:::
NewExpanded the number of endpoints supporting OData query options. These endpoints are listed in the odata section of the Aeon API Swagger documentation.




:::tip

For more information on using OData with endpoints in the Aeon API, see Aeon API.

:::
NewAdded support for the new ReshelvingLocation field to the Requests/<transactionNumber>/reshelved and Requests/batch/reshelved endpoints.


For more information on this field, see the Database section below.




:::info

The ReshelvingLocation field can be added to the request body for these endpoints using the following format:



<br>{ "newStatus": "<new queue name or ID>", "reshelvingLocation": "<reshelving location>"}<br>


Note that if a non-blank value is present in a request to either endpoint, it will overwrite any existing value in the ReshelvingLocation field of the affected transaction(s).

:::
ChangedRemoved the /api/RequestBarcodes/{barcode}/reshelved and /api/RequestBarcodes/{id}/reshelved endpoints, which were deprecated and replaced with the /api/Requests/Batch/ endpoints in the Aeon 5.0 API.




:::warning

Any existing implementations of the RequestBarcodes endpoints should be updated to use the /api/Requests/Batch/ endpoints.

:::
ChangedChanged the data type of the Appointment ID property returned by the GET /api/Users/{username}/appointments endpoint from a string to an integer value. The new data type for this property will also be used in all new endpoints in the Aeon API in which it is included.
FixedThe Aeon API will no longer log an unnecessary invalid X-AEON-API-KEY header message when the Swagger interface or other public endpoints that do not require API key authentication are accessed. Bug# 10273
FixedFixed an issue where new requests created via the /api/Requests/create endpoint could not be associated with an activity. Bug# 27495
FixedFixed an issue where calling the /api/Users/{username}/requests endpoint to retrieve a user's requests could return an HTTP 500 error when the activeOnly parameter was set to 'true'. Bug# 27501
FixedFixed an issue where attempting to associate a researcher with a request created via the /api/Requests/create endpoint could fail in that the RequestFor field would be set to the username associated with the request when the request was created instead of to the researcher's username.Bug# 27503
FixedFixed an issue where attempting to associate a request created via the /api/Requests/create endpoint with a nonexistent researcher username would return inaccurate validation messages that did not clarify why the process failed. The endpoint will now return a single validation message explicitly stating that the username is invalid. Bug# 27504

Addons​

ChangedRemoved support for the embedded Chromium browser from the Aeon Desktop Client. Client addons that use a Chromium browser interface will now load using a WebView2 browser. To prevent potential compatibility issues, addons should be updated to versions supporting the WebView2 browser.




:::warning

Install Updated Addons


The following Atlas-authored addons have been updated to include support for the WebView2 browser and should be installed before or after updating to Aeon 6.0 to prevent potential compatibility issues:




Addon developers should update Chromium-based addons to include support for the WebView2 browser to prevent compatibility issues with the Aeon 6.0 Desktop Client. Information on implementing the WebView2 browser is available in the addon documentation.



:::

Administrative​

FixedUpdated the third-party Newtonsoft dependency used by the Aeon Desktop Client, Aeon Customization Manager, Aeon Staff Manager, and Aeon System Manager to patch a security vulnerability found in the previous version of this component.

Appointment Scheduling​

FixedFixed an issue where appointments with invalid data would appear on the User Information and Request forms in the Aeon Desktop Client but would throw an error when opened. These appointments can now be opened, but the invalid data must be fixed (e.g., by ensuring the appointment's stop time occurs after its start time) before the Appointment form can be saved. Bug# 17378
FixedFixed an issue where the System panel on the Aeon Desktop Client dashboard did not include information for pending or failed appointment-type emails. These emails are now included in the System panel and can be managed via the Failed Email and Pending Email tabs. Bug# 26272


See Troubleshooting Email for more information on accessing and managing failed and pending emails.
FixedFixed an issue where rescheduling an appointment in the Aeon Desktop Client could result in an error if another user edited that appointment at the same time using a different start or end time. Both the start time and end time on the Appointment form will now be saved to the database when the appointment is saved to avoid potential invalid data, even if only one of these values was changed during editing. Bug# 17181
FixedFixed an issue where the auto-confirm appointments setting for a reading room in the Aeon Customization Manager would not automatically confirm/re-confirm an appointment after it was edited or rescheduled on the web interface. Bug# 24074

Database​

NewAdded a new ReshelvingLocation field to the Transactions table. This field can be added to grids and the Request form in the Aeon Desktop Client and to Transactions grids in the Aeon Web Client. It is also available as a merge field for print and email templates.




:::warning

Note: This field is not available on the Request form in the Aeon Desktop Client 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.


Aeon administrators must also manually add this field to Transactions grids in the Aeon Web Client. For more information on the web client layout customization process, see Managing Staff Accounts and Web Client Layouts Using the Staff Administration Page.

:::






:::info

Information for Developers


The ReshelvingLocation field can be added as a body parameter to the Requests/<transactionNumber>/reshelved and Requests/batch/reshelved endpoints in the Aeon API. See the API section of the release notes above for more information.

:::
NewAdded new tables to the database to support the Aeon Web Client features:


  • RestrictedFieldGroups: Holds data for the restricted field groups configured on the Staff Administration page.


  • RestrictedFields: Holds data for the fields assigned to the restricted field groups configured on the Staff Administration page.


  • SiteGroups: Holds data for the site groups configured on the Staff Administration page.


  • SiteGroupSites: Holds data for the sites assigned to the site groups configured on the Staff Administration page.


  • StaffProfiles: Holds data for the profiles configured on the Staff Administration page.


  • StaffRestrictedFieldGroups: Holds data for the restricted field groups assigned to each profile configured on the Staff Administration page.


  • StaffSiteGroups: Holds data for the site group(s) assigned to each staff account on the Staff Administration page.


  • StaffWebClientSessions: Holds data for staff user web sessions in the Aeon Web Client.


  • WebClientFields: Holds data for the fields assigned to the layouts configured on the Staff Administration page.


  • WebClientGroups: Holds data for the field groups assigned to the layouts configured on the Staff Administration page.


  • WebClientLayouts: Holds data for the layouts configured on the Staff Administration page.



For details on the columns in each table, see*Aeon Database Tables**.*
NewAdded two new columns to the Staff database table to support Aeon Web Client features:
FixedAdded triggers to the Aeon database that will automatically adjust the casing for the username value associated with new appointment or transaction records to match the casing used for that value in the Users database table to prevent issues caused when the casing of these username values did not match.




:::warning

Any existing database records that were affected by the username casing mismatch issues will be automatically corrected during the Aeon 6.0 server update.

:::

Email​

FixedFixed an issue where an invalid BCC address on an email would be logged in the Aeon System Manager logs as an "Invalid From Address" error. The System Manager will log an "Invalid BCC Address" error message in these cases.

Installing and Updating​

danger

Warning! New System Requirements

The Aeon 6.0 release includes several new system requirements and recommendations. Please review the Updating Procedure section of the release notes above before updating to ensure the required components are in place.

ChangedChanged the underlying third-party component libraries used to facilitate printing documents from the Aeon Desktop Client. No existing printing functionality will be affected or changed by this update, however, the files installed with the Aeon Desktop Client to support printing functionality will be modified as follows as a result of this change:




:::info

Files Removed


The following existing files will be removed from the Aeon Desktop Client installation directory upon updating:

  • SpreadsheetGear2017.Core.dll

  • SpreadsheetGear2017.Drawing.dll

  • SpreadsheetGear2017.Windows.Forms.dll

  • SpreadsheetGear2017.Windows.Forms.Integration.dll


:::






:::info

Files Added


The following new files will be added to the Aeon Desktop Client installation directory upon updating:

  • Syncfusion.Compression.Base.dll

  • Syncfusion.Licensing.dll

  • Syncfusion.XlsIO.Base.dll


:::
ChangedThe Aeon Server Installer PowerShell Scripts will now install the Aeon API to a new default file path location on the Aeon Server (C:\Program Files (x86)\Aeon\AeonApi). The API will be moved from the previous installation location to the new default installation path upon update.

Staff Desktop Client​

ChangedRemoved support for the embedded Chromium browser. To prevent potential compatibility issues after updating, browser-based client addons should be updated to versions supporting the WebView2 browser.




:::warning
Please see the Addons section of the release notes above for more information on updating these addons.
:::
FixedFixed an issue where an error would occur when using the Clone to Current User option from the request list for a queue or request search results. Bug# 26834
FixedFixed an issue where an error would occur when using the Print Callslips option from the Activity or Appointment form if any custom fields defined in the Aeon Customization Manager's CustomFieldDefinitions table were present on the print template. Bug# 26639
FixedFixed an issue where the panel on the left side of the Aeon Options window did not update its color based on the client display skin selected, which could lead to poor color contrast. Bug# 22246
FixedFixed an issue where creating requests from an Excel spreadsheet file would fail if any custom fields defined in the Aeon Customization Manager's CustomFieldDefinitions table were included in the spreadsheet. Bug# 23597
FixedFixed an issue where errors could occur when applying service packages to photoduplication requests. Bug# 23473

Staff Web Client​

NewA lightweight web-based ** version of the Aeon Staff Client is now available. The ** Aeon Web Client ** is a web-based version of the existing Aeon Desktop Client application and is installed via the Aeon 6.0 server installation/update. Once installed, the web client can be accessed via the URL *https://servername/aeonstaff/***on any standard web browser application (e.g., Google Chrome or Safari) on the user's computer or mobile device, including macOS and iOS devices:


Web Client Home


The%20initial%20release%20of%20the%20Aeon%20Web%20Client%20includes%20many%20of%20the%20user%20management,%20reading%20room%20sign-in,%20and%20appointment%20scheduling%20features%20available%20in%20the%20desktop%20client%20application,%20as%20well%20as%20several%20brand-new%20customization%20options%20and%20security%20features%20exclusive%20to%20the%20new%20web%20application:




:::info

 Note%20on%20Future%20Updates


Support%20for%20the%20full%20range%20of%20features%20included%20in%20the%20Aeon%20Desktop%20Client%20application,%20such%20as%20request%20and%20activity%20processing%20functionality,%20will%20be%20added%20to%20the%20Aeon%20Web%20Client%20application%20in%20future%20releases.

:::






:::tip

For%20a%20detailed%20overview%20of%20the%20Aeon%20Web%20Client%20and%20links%20to%20relevant%20documentation%20for%20each%20of%20the%20features%20listed%20below,%20see%20Aeon%20Web%20Client%20Overview%20or%20click%20the%20Learn%20more%20link%20in%20one%20of%20the%20sections%20below.

:::






:::info

Navigation%20and%20Searching


  • Integrated%20Home%20Dashboard:%20View%20requests%20and%20manage%20signed-in%20users%20and%20appointments%20directly%20from%20the%20Aeon%20Web%20Client%20Dashboard%20on%20the%20home%20page.


  • Convenient%20navigation%20options:%20A%20navigation%20menu%20and%20toolbar%20are%20displayed%20on%20each%20page%20with%20various%20options%20for%20navigating%20the%20web%20client,%20performing%20page-specific%20actions,%20changing%20user%20settings,%20performing%20searches,%20and%20viewing%20alerts.


  • Searching:%20Simultaneously%20search%20for%20request,%20activity,%20and%20user%20records%20using%20the%20search%20button%20in%20the%20toolbar.



Learn%20more%20>>

:::






:::info

** Multi-Factor%20Authentication%20(MFA)%20Protection%20for%20Staff%20Accounts


  • Enhanced%20security%20for%20staff%20logins:%20By%20default,%20the%20Aeon%20Web%20Client%20will%20enforce%20multi-factor%20authentication%20(MFA)%20for%20all%20staff%20user%20accounts%20to%20provide%20an%20extra%20layer%20of%20security%20for%20logins%20to%20the%20web%20client%20application.%20MFA%20must%20be%20configured%20for%20each%20staff%20account%20using%20a%20third-party%20authentication%20application,%20such%20as%20Microsoft%20Authenticator%20upon%20first%20login.%20See%20<a%20href="/docs/aeon/staff-web-client/configuring-multi-factor-authentication-mfa-for-staff-web-client-accounts"%20target="_blank"%20rel="noopener%20noreferrer">Configuring%20Multi-Factor%20Authentication%20for%20details%20on%20this%20process.





 Configuring%20the%20MFA%20Requirement%20on%20the%20Aeon%20Server


Multi-factor%20authentication%20provides%20an%20important%20extra%20layer%20of%20security%20to%20your%20Aeon%20system%20by%20requiring%20all%20users%20to%20log%20in%20with%20two%20forms%20of%20authentication:%20their%20username%20and%20password%20credentials%20and%20a%20time-based%20one-time%20password%20(TOTP)%20code%20that%20is%20generated%20by%20an%20authentication%20application%20and%20is%20harder%20for%20potential%20attackers%20to%20obtain%20or%20duplicate.%20The%20TOTPs%20enforced%20by%20the%20MFA%20requirement%20are%20important%20in%20that%20they%20provide%20additional%20protection%20against%20potential%20security%20breaches%20to%20your%20Aeon%20system%20if%20a%20staff%20user’s%20username%20and%20password%20are%20compromised.%20Given%20these%20security%20implications,%20the%20configuration%20options%20for%20the%20MFA%20requirement%20on%20the%20Aeon%20Server%20will%20vary%20based%20on%20your%20hosting%20provider%20as%20follows:


  • Atlas-hosted%20Aeon%20sites:%20For%20security%20purposes,%20MFA%20is%20required%20for%20logins%20to%20the%20Aeon%20Web%20Client%20and%20cannot%20be%20disabled%20on%20your%20server.%20If%20you%20have%20any%20questions%20about%20this%20policy,%20please%20contact%20<a%20href="mailto:support@atlas-sys.com">support@atlas-sys.com.


  • Self-hosted%20Aeon%20sites:%20It%20is%20strongly%20recommended%20that%20the%20MFA%20requirement%20is%20left%20enabled%20on%20the%20Aeon%20Server%20for%20the%20extra%20layer%20of%20security%20it%20provides%20to%20the%20Aeon%20Web%20Client.%20If%20necessary,%20the%20MFA%20requirement%20can%20be%20disabled%20on%20your%20server%20following%20<a%20href="/docs/aeon/staff-web-client/logging-into-the-aeon-web-client"%20target="_blank"%20rel="noopener%20noreferrer">the%20instructions%20in%20the%20documentation,%20however,%20please%20note%20that%20disabling%20the%20MFA%20requirement%20will%20significantly%20reduce%20the%20security%20of%20your%20Aeon%20system.







Please%20see%20Troubleshooting%20Issues%20Configuring%20MFA%20for%20Staff%20Accounts%20After%20Web%20Client%20Installation%20if%20you%20are%20experiencing%20issues%20completing%20the%20MFA%20configuration%20process%20for%20staff%20accounts%20after%20the%20Aeon%206.0%20update.




Learn%20more%20>>

:::






:::info

 Enhanced%20Client%20Customization%20Options


  • New%20staff%20profiles%20feature:%20Aeon%20administrators%20can%20create%20and%20assign%20customizable%20profiles%20to%20staff%20accounts%20via%20the%20robust%20customization%20options%20available%20on%20<a%20href="/docs/aeon/staff-web-client/managing-staff-accounts-and-web-client-layouts-using-the-staff-administration-pa"%20target="_blank"%20rel="noopener%20noreferrer">the%20Staff%20Administration%20page.%20The%20profile%20assigned%20to%20a%20staff%20account%20determines:

    • The%20layout%20used%20for%20the%20customizable%20pages%20and%20grids%20in%20the%20Aeon%20Web%20Client.

    • If%20view%20and%20modify%20access%20to%20any%20fields%20or%20database%20tables%20is%20restricted%20for%20that%20user.




  • Easy%20site%20view%20configuration:%20For%20multi-site%20Aeon%20installations,%20the%20Staff%20Administration%20page%20is%20also%20used%20to%20configure%20and%20assign%20site%20groups%20to%20each%20staff%20user%20that%20will%20determine%20which%20individual%20sites%20that%20user%20will%20be%20able%20to%20see%20when%20using%20the%20web%20client.%20Users%20assigned%20to%20multiple%20site%20groups%20can%20quickly%20switch%20their%20active%20site%20group%20view%20using%20the%20Select%20Sites%20option%20in%20the%20web%20client%20toolbar.


    <div%20class="callout%20callout--danger">

    Initial%20Site%20View%20Configuration%20for%20Multi-Site%20Aeon%20Installations


    The%20site%20groups%20that%20initially%20appear%20on%20the%20<a%20href="/docs/aeon/staff-web-client/managing-staff-accounts-and-web-client-layouts-using-the-staff-administration-pa"%20target="_blank"%20rel="noopener%20noreferrer">Site%20Groups%20tab%20of%20the%20Staff%20Administration%20page%20upon%20installation%20of%20the%20Aeon%20Web%20Client%20will%20be%20based%20on%20the%20existing%20views%20configured%20in%20your%20Aeon%20database%20at%20the%20time%20the%20Aeon%206.0%20update%20is%20performed.%20Modifying%20the%20site%20groups%20within%20the%20Aeon%20Web%20Client%20will%20not%20alter%20the%20views%20configured%20in%20your%20database.


    Action%20required:%20After%20updating,%20Aeon%20administrators%20for%20multi-site%20installations%20should%20review%20and%20adjust%20the%20site%20groups%20on%20the%20Site%20Groups%20tab%20of%20the%20Staff%20Administration%20page%20as%20necessary%20and%20then%20assign%20each%20staff%20account%20to%20at%20least%20one%20site%20group%20using%20the%20controls%20on%20the%20Profiles%20tab.%20See%20the%20Assigning%20Profiles%20and%20Site%20Groups%20section%20in%20the%20<a%20href="/docs/aeon/staff-web-client/managing-staff-accounts-and-web-client-layouts-using-the-staff-administration-pa"%20target="_blank"%20rel="noopener%20noreferrer">Profiles%20tab%20documentation%20for%20step-by-step%20instructions.%20Note%20that%20errors%20will%20occur%20if%20a%20staff%20user%20logs%20into%20the%20web%20client%20without%20any%20site%20groups%20assigned%20to%20their%20account.





  • Per-user%20customization%20options:%20Each%20staff%20user%20can%20set%20the%20display%20theme%20for%20the%20web%20client%20(light%20or%20dark),%20switch%20between%20their%20active%20site%20group%20view%20(if%20assigned%20to%20multiple%20site%20groups),%20and%20configure%20several%20additional%20accessibility%20preferences%20in%20the%20user%20settings%20for%20their%20account.



Learn%20more%20>>

:::






:::info

 User%20Record%20Management


  • Easy%20user%20creation:%20Conveniently%20create%20a%20new%20user%20record%20from%20anywhere%20in%20the%20web%20client%20using%20the%20Create%20User%20option%20in%20the%20navigation%20menu.


  • User%20record%20management%20via%20the%20User%20Information%20page:%20View%20existing%20user%20records%20(including%20user%20history%20and%20notes),%20change%20a%20user's%20information,%20update%20a%20user's%20clearance%20status,%20send%20emails,%20use%20the%20logon%20to%20web%20feature,%20and%20more%20from%20<a%20href="/docs/aeon/users/working-with-user-records-in-the-client"%20target="_blank"%20rel="noopener%20noreferrer">the%20User%20Information%20page.%20



** Learn%20more%20>>**

:::






:::info

 User%20Sign-In%20and%20Reading%20Room%20Management


  • Reading%20room%20management%20options:%20Sign%20users%20into%20and%20out%20of%20reading%20rooms,%20assign%20seating%20locations,%20and%20mark%20signed-in%20users%20as%20present%20or%20away%20using%20the%20reading%20room%20management%20options%20available%20on%20the%20Dashboard%20and%20the%20User%20Information%20page.


  • Enhanced%20sign-in%20security:%20A%20warning%20will%20display%20when%20an%20uncleared,%20blocked,%20or%20disavowed%20user%20is%20signed%20into%20a%20reading%20room,%20providing%20an%20extra%20layer%20of%20security%20to%20the%20user%20sign-in%20process.



Learn%20more%20>>

:::






:::info

 Appointment%20Scheduling


  • Multiple%20appointment%20calendars:%20Access%20the%20full%20appointment%20calendar%20for%20each%20reading%20room%20from%20the%20web%20client's%20Calendar%20page%20or%20conveniently%20view%20a%20list%20of%20each%20day's%20appointments%20from%20the%20mini-calendar%20agenda%20tool%20on%20the%20Dashboard.


  • Appointment%20form:%20Create,%20modify,%20cancel,%20or%20confirm%20appointments,%20manage%20appointment%20notes,%20and%20view%20an%20appointment's%20history%20and%20associated%20requests%20using%20the%20web%20client%20Appointment%20form.%20


  • Manage%20appointments%20for%20individual%20users:%20View%20and%20manage%20a%20user's%20existing%20appointments%20or%20create%20new%20appointments%20for%20a%20user%20directly%20from%20the%20Appointments%20grid%20on%20the%20User%20Information%20page.



Learn%20more%20>>

:::






:::info

 Accessibility%20Information


  • WCAG%202.1%20&%20Section%20508%20compliance:%20The%20Aeon%20Web%20Client%20adheres%20to%20WCAG%202.1%20&%20Section%20508%20compliance%20standards.%20Please%20see%20the%20<a%20href="/docs/getting-started-with-atlas/archivesspace/voluntary-product-accessibility-template-vpat"%20target="_blank"%20rel="noopener%20noreferrer">Voluntary%20Product%20Accessibility%20Template%20(VPAT)%20for%20full%20details%20and%20exceptions.


  • Robust%20keyboard%20control%20support:%20The%20web%20client%20supports%20standard%20keyboard%20controls%20typically%20used%20to%20navigate%20web-based%20applications%20and%20also%20supports%20a%20<a%20href="/docs/aeon/staff-web-client/additional-supported-keyboard-controls-for-navigating-and-using-the-aeon-web-cli"%20target="_blank"%20rel="noopener%20noreferrer">range%20of%20additional%20keyboard%20controls%20for%20various%20tools,%20menus,%20and%20fields.


  • Per-user%20accessibility%20settings:%20Users%20can%20toggle%20loading%20animations%20on%20or%20off%20and%20change%20the%20duration%20used%20to%20display%20notifications%20on%20the%20screen%20within%20their%20user%20settings.



Learn%20more%20>>

:::






:::warning

 Notes%20for%20Server%20Administrators


The%20Aeon%20Web%20Client%20will%20be%20installed%20on%20the%20Aeon%20Server%20during%20the%206.0%20server%20installation%20process.%20After%20the%206.0%20server%20upgrade%20is%20completed,%20the%20web%20client%20will%20be%20accessible%20using%20the%20following%20URL:%20 https://servername/aeonstaff/**.%20This%20location%20is%20***not%20customizable***.


Several%20additional%20files%20will%20be%20installed%20in%20the%20Aeon%20API%20application%20directory%20on%20the%20server%20to%20support%20the%20multi-factor%20authentication%20requirement%20for%20the%20web%20client.%20See%20 Installing%20the%20Aeon%20Server for details.

:::

Web Interface​

NewFor increased security against potentially untrusted XML files, the expansion of XML document type definitions (DTDs) can now be prohibited during EAD processing via the new EADProhibitDTD customization key in the Aeon Customization Manager (located under **Web InterfaceEAD**).


:::warning


  • Existing Aeon installations will have this key set to No upon update (i.e., Aeon will continue to allow DTD expansion during EAD processing) to prevent breaking existing EAD implementations. For security purposes, changing this key to Yes is recommended if your EAD XML does not rely on DTDs for processing.


  • New Aeon installations will have this key set to Yes by default (i.e., Aeon will prohibit DTD expansion during EAD processing).





See Submitting Requests via EAD Finding Aids for more detailed guidance on setting the value of this key.



:::
ChangedChanged the underlying third-party component libraries used to facilitate Activity exporting from the Aeon web interface. Activity information will now be exported in the .xlsx file format.
FixedThe Aeon 6.0 default and feature-specific web pages include all the latest changes and fixes first released in the Aeon v5.2.11and Aeon v5.2.13default and feature-specific web pages. For detailed instructions on implementing each of these changes, please see the Aeon 5.2.11 web page release implementation instructions and the Aeon 5.2.13 web page release implementation instructions:


  • Removed the jQuery UI JavaScript Library from the web pages for security purposes.




    :::warning

    The jQuery UI JavaScript Library is no longer necessary for the functionality of the web pages and should be removed to ensure the best possible security on the Aeon web interface.


    However, please note that removing this library may break existing implementations of the date picker calendar dropdown tool used with various date fields on the web pages if you have not updated these date picker components to the new version first released with the Aeon 5.2 web pages. See the 5.2.11 web page implementation documentation for more information on updating these components.


    :::



  • Changed the default password reset instructions on the FAQ web page (FAQ.html) to first direct patrons to use the Forgot Password web form to reset their password before contacting staff. For security purposes, patrons should be encouraged to reset their own passwords.

  • Updated the appointments.js file to fix an issue where the Aeon web interface would only consider the current date and would not consider the current time when determining whether an appointment could be scheduled in a reading room based on the room's Appointment Minimum Lead Days value in the Aeon Customization Manager. Aeon will now also consider the current time when making this calculation after the appointments.js file is updated. Bug# 19633

  • Fixed an issue where manually entering a date when making an appointment on the web interface could cause a JavaScript console error in the web browser in some cases. Bug# 19926

  • Fixed an issue where form fields using a date picker calendar dropdown tool would not initialize correctly when placed inside a photoduplication toggle.

  • Changed underlined text used for emphasis on the search results web page (ViewSearchResults.html) to instead use bolded text to adhere to W3C HTML5 guidelines. Bug# 17985

  • Removed non-functional popup text for file size and added missing transaction number and file size information to the requests displayed on the Electronically Delivered Items web page (DataRow_ElectronicDelivery.html). Bug# 18112

  • Updated the hardcoded copyright year on Logon.html to 2024.

  • Fixed an issue where manually entering invalid data into the Appointment Date field (e.g., letters or a string of numbers) when making an appointment on the web interface would cause a JavaScript console error in the web browser.

  • Fixed an issue where disabled action buttons for transactions on the Aeon web interface could still be activated using keyboard controls, allowing users to perform actions such as editing cancelled requests. Bug# 15246

  • Removed unused CSS properties from the aeon.css file.

  • Encoded ampersands used in the code for HTML attribute values on various default and feature-specific web pages.

FixedPhotoduplication status will no longer be set for requests sent to user review to fix an issue where these requests could become uneditable if the photoduplication status was set to Awaiting Order Processing by the SkipOrderEstimates parameter. Bug# 12663

03 July 2024 (6.0.10) Default & Feature-Specific Web Pages Release​

A new version of the default and feature-specific web pages has been released to 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:

FixedFixed various issues on the default and feature-specific web pages. The list of changes can be found below. For more information on implementing each fix, see Implementing 6.0 Web Page Changes.

  • Added the license and copyright statement for the third-party date picker code library to the datepicker.js file.

  • Reformatted the "Important Copyright Information" and "Aeon FAQ (Frequently Asked Questions)" section headers on NewAuthRegistration.html as buttons to fix an accessibility issue where these sections could not be expanded or collapsed using keyboard controls.

  • Updated atlasUtility.js to fix an accessibility issue with the "Other" dropdown javascript feature where when the "Other" option was chosen from the dropdown, the associated text field was unhidden and focus was moved to it automatically, failing WCAG criterion 3.2.2. Keyboard focus will now stay on the dropdown field until the user manually navigates to the text field after making the dropdown selection.

  • Updated buildSiteMap.js to fix an issue where empty hyperlinks would be generated in the site map (SiteMap.html) if a hyperlinked image was added to the footer (include_footer.html).

  • Fixed issues where Boolean checkbox fields configured on the web pages would not correctly load their values from the database and would not submit a value to the database when unchecked in some cases.

  • Adjusted the styling of the buttons contained within the DataRow_ElectronicDelivery.html file to improve the responsive accessibility of these buttons and to make the styling consistent with other DataRows containing three or more buttons on the Aeon web interface.

ChangedUpdated the Aeon default and feature-specific web pages to rename some of the account management-related features for clarity and to ensure naming consistency across the web pages:

  • The My Profile dropdown in the navigation menu was renamed Account Info

  • The option within the My Profile dropdown menu to navigate to the ChangeUserInformation.html page was changed from Change User Information to Update User Information

  • The page title and page header on ChangeUserInformation.html were changed to Update User Information to match the new name for the navigation link



For more information on implementing these changes, see Implementing 6.0 Web Page Changes.
ChangedThe following changes have been made to the layout and style used to format the Aeon default and feature-specific web pages when they are printed from the web browser to improve the readability of the printed material and to increase focus on essential information:

  • The following elements are now hidden when the web page is printed:

    • Action buttons (e.g., Edit, Cancel, etc.) on web pages containing transaction details

    • Most buttons included in the DataRow template files (e.g., Details, Action, etc.)

    • The "Skip to main content" link

    • Web alerts

    • Form controls on the search results web page



  • The summary of charges will now appear before the list of orders when the ViewOrderEstimates.html, ViewOrderApprovals.html, and CreditCardPayment.html pages are printed

  • Form fields are now formatted with a black border color and black text when printed to enhance color contrast

  • Buttons and badges are now formatted with a white background color and black text when printed to enhance color contrast

  • Set the font size used for body text on print layouts to 11pt

  • Implemented missing print styling on the Logon.html web page so that this page is now properly formatted when printed



For more information on implementing each change, see Implementing 6.0 Web Page Changes.
NewAdded new minified versions of most default JavaScript and CSS files used in the Aeon web pages and updated all relevant web page files to use the new minified files in order to optimize the performance of the Aeon web interface and reduce page load times for users. The minified files will have the extension .min.js or .min.css and will be present in the js or css folder of the default and feature-specific web page downloads alongside the original un-minified version of each file.


For more information on implementing these new files, see Implementing 6.0 Web Page Changes.

11 July 2024 (6.0.3) Desktop Client Release​

The Aeon 6.0 Desktop Client has been updated to a new version to fix an issue affecting the printing process in Aeon Desktop Client v6.0.1 that could lead to incorrect values printed for certain fields and to fix a separate error that occurred when the Appointments to Confirm form was opened in the desktop client.

info

Update Procedure

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.

Follow the Client Automatic Updater prompts within the Aeon Desktop Client, or download and run the 6.0.3 Desktop Client Installer from the Aeon Downloads page to install the new client application(s).

Client Application Updates

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

  • Desktop Client v6.0.3
FixedFixed an issue where field values containing numeric data could be improperly formatted in some cases when printed and would not match the value displayed for the field on the related record in the Aeon Desktop Client.
FixedFixed an issue that could cause an error message when opening or reloading the Appointments to Confirm form in the Aeon Desktop Client.

Desktop Client Only Release​

03 September 2024 (6.0.4.0) Desktop Client Release​

The Aeon 6.0.4.0 Desktop Client has been updated to a new version to prevent a necessary DomainLogic library file from being removed during updates from Aeon 5.2.5 to 6.0.3.

Aeon users already on version 6.0 will receive a prompt indicating there is a client update available. If you wish to run the update, you can do so from the prompt. There are no associated client updates aside from the version number.

If you do not wish to update the client, you can continue to dismiss the message.

info

Update Procedure

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.

Follow the Client Automatic Updater prompts within the Aeon Desktop Client, or download and run the 6.0.4.0 Desktop Client Installer from the Aeon Downloads page to install the new client application(s).

Client Application Updates

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

  • Desktop Client v6.0.4.0
  • Customization Manager v6.0.2.0
  • Staff Manager v6.0.2.0
FixedThe DomainLogic library was reversioned for the Client, Customization Manager, and Staff Manager to prevent a necessary library file from being removed during some client updates. Bug# 29609

29 May 2025 (6.0.4) Aeon Server/ (6.0.1) Web DLL Release​

The Aeon Server and Web DLL have been updated to new versions to fix a bug with user custom fields and remote authentication where the username in Aeon vs. the Remote Authentication system had different casing.

info

Update Procedure

Please perform a server update to implement the fixes in the Aeon 6.0.1 server release. Atlas-hosted sites will be updated automatically by Atlas Support (support@atlas-sys.com) and will receive an email with more details about the update.

Note: Self-hosted sites should refer to the update procedures at the top of this page to perform this update.

FixedFixed an issue for User Custom Fields. Aeon would throw an error during remote authentication and login if an Aeon username had different casing than the remote authentication username. For example, researcher@site.edu vs RESEARCHER@site.edu.