Aeon 6.0 Release Notes

Print Friendly and PDF Follow

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:

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

Considerations Before You Update

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 integrations will 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.11 and Aeon v5.2.13 default and feature-specific web pages. The Aeon 5.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:

Aeon 6.0 Features & Fixes

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

Aeon API

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 integrations will 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: 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, please ensure 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.
New

Changed 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 is not customizable.

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

New

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

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

New

Users 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).

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

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.

New

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

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

New

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

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

New

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

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

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

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

Changed

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

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

Changed

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

Fixed

The 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

Fixed

Fixed an issue where new requests created via the /api/Requests/create endpoint could not be associated with an activity. Bug# 27495

Fixed

Fixed 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

Fixed

Fixed 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

Fixed

Fixed 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

Changed

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

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

Fixed

Updated 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

Fixed

Fixed 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

Fixed

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

Fixed

Fixed 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

Fixed

Fixed 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

New

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

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.

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.

New

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

New

Added two new columns to the Staff database table to support Aeon Web Client features:

Fixed

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

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

Fixed

Fixed 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

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. 

Changed

Changed 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:

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

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
Changed

The 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

Changed

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

Please see the Addons section of the release notes above for more information on updating these addons. 
Fixed

Fixed 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

Fixed

Fixed 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

Fixed

Fixed 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

Fixed

Fixed 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

Fixed

Fixed an issue where errors could occur when applying service packages to photoduplication requests. Bug# 23473


Staff Web Client

New

A 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 initial release of the Aeon Web Client includes many of the user management, reading room sign-in, and appointment scheduling features available in the desktop client application, as well as several brand-new customization options and security features exclusive to the new web application: 

Note on Future Updates

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

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

Navigation and Searching

  • Integrated Home Dashboard: View requests and manage signed-in users and appointments directly from the Aeon Web Client Dashboard on the home page.
  • Convenient navigation options: A navigation menu and toolbar are displayed on each page with various options for navigating the web client, performing page-specific actions, changing user settings, performing searches, and viewing alerts.
  • Searching: Simultaneously search for request, activity, and user records using the search button in the toolbar.

Learn more >>

Multi-Factor Authentication (MFA) Protection for Staff Accounts

  • Enhanced security for staff logins: By default, the Aeon Web Client will enforce multi-factor authentication (MFA) for all staff user accounts to provide an extra layer of security for logins to the web client application. MFA must be configured for each staff account using a third-party authentication application, such as Microsoft Authenticator upon first login. See Configuring Multi-Factor Authentication for details on this process.

Configuring the MFA Requirement on the Aeon Server

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

  • Atlas-hosted Aeon sites: For security purposes, MFA is required for logins to the Aeon Web Client and cannot be disabled on your server. If you have any questions about this policy, please contact support@atlas-sys.com.
  • Self-hosted Aeon sites: It is strongly recommended that the MFA requirement is left enabled on the Aeon Server for the extra layer of security it provides to the Aeon Web Client. If necessary, the MFA requirement can be disabled on your server following the instructions in the documentation, however, please note that disabling the MFA requirement will significantly reduce the security of your Aeon system.

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

Learn more >>

Enhanced Client Customization Options

  • New staff profiles feature: Aeon administrators can create and assign customizable profiles to staff accounts via the robust customization options available on the Staff Administration page. The profile assigned to a staff account determines:
    • The layout used for the customizable pages and grids in the Aeon Web Client.
    • If view and modify access to any fields or database tables is restricted for that user.
  • Easy site view configuration: For multi-site Aeon installations, the Staff Administration page is also used to configure and assign site groups to each staff user that will determine which individual sites that user will be able to see when using the web client. Users assigned to multiple site groups can quickly switch their active site group view using the Select Sites option in the web client toolbar.

    Initial Site View Configuration for Multi-Site Aeon Installations

    The site groups that initially appear on the Site Groups tab of the Staff Administration page upon installation of the Aeon Web Client will be based on the existing views configured in your Aeon database at the time the Aeon 6.0 update is performed. Modifying the site groups within the Aeon Web Client will not alter the views configured in your database.

    Action required: After updating, Aeon administrators for multi-site installations should review and adjust the site groups on the Site Groups tab of the Staff Administration page as necessary and then assign each staff account to at least one site group using the controls on the Profiles tab. See the Assigning Profiles and Site Groups section in the Profiles tab documentation for step-by-step instructions. Note that errors will occur if a staff user logs into the web client without any site groups assigned to their account.

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

Learn more >>

User Record Management

  • Easy user creation: Conveniently create a new user record from anywhere in the web client using the Create User option in the navigation menu.
  • User record management via the User Information page: View existing user records (including user history and notes), change a user's information, update a user's clearance status, send emails, use the logon to web feature, and more from the User Information page

Learn more >>

User Sign-In and Reading Room Management 

  • Reading room management options: Sign users into and out of reading rooms, assign seating locations, and mark signed-in users as present or away using the reading room management options available on the Dashboard and the User Information page.
  • Enhanced sign-in security: A warning will display when an uncleared, blocked, or disavowed user is signed into a reading room, providing an extra layer of security to the user sign-in process.

Learn more >>

Appointment Scheduling

  • Multiple appointment calendars: Access the full appointment calendar for each reading room from the web client's Calendar page or conveniently view a list of each day's appointments from the mini-calendar agenda tool on the Dashboard.
  • Appointment form: Create, modify, cancel, or confirm appointments, manage appointment notes, and view an appointment's history and associated requests using the web client Appointment form. 
  • Manage appointments for individual users: View and manage a user's existing appointments or create new appointments for a user directly from the Appointments grid on the User Information page.

Learn more >>

Accessibility Information

  • WCAG 2.1 & Section 508 compliance: The Aeon Web Client adheres to WCAG 2.1 & Section 508 compliance standards. Please see the Voluntary Product Accessibility Template (VPAT) for full details and exceptions.
  • Robust keyboard control support: The web client supports standard keyboard controls typically used to navigate web-based applications and also supports a range of additional keyboard controls for various tools, menus, and fields.
  • Per-user accessibility settings: Users can toggle loading animations on or off and change the duration used to display notifications on the screen within their user settings.

Learn more >>

Notes for Server Administrators

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

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


Web Interface

New

For 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 Interface | EAD).

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

Changed

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

Fixed

The Aeon 6.0 default and feature-specific web pages include all the latest changes and fixes first released in the Aeon v5.2.11 and Aeon v5.2.13 default 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.

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

Photoduplication 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

Questions?

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

Contact Support