Skip to main content
Version: Aeon 7.0

Aeon 7.0.1831

Released August 24, 2026. API key masking and templates, rule-driven dashboard categories, and field restrictions that cover custom fields everywhere

Highlights​

  • Dashboard activity categories can now carry rules: give a category a filter (like Activity Info 1 equals "Exhibition") and matching activities are placed into it automatically, with manually dragged activities staying put. Activities no rule claims can be grouped by a field of your choice — Activity Type as before, or Status, Location, or any Activity Info field. Both work per-user on the dashboard and institution-wide through Activity Designer templates.
  • Reusable endpoint templates for API keys. The API Keys page has a new Endpoint templates tab where you can save a named set of endpoints — create your own, or duplicate one that ships with Aeon — and apply it to any key's grants in one step with the new Apply template button, instead of ticking the same boxes for every key. Applying copies the endpoints onto the key, so editing a template later never changes keys that already used it. A built-in Caiasoft template ships with the endpoints the offsite-storage integration needs.
  • Web Platform Config keys are now hidden once they are saved. Stored API keys show only their first and last few characters, and can no longer be revealed or copied from the list. When you add a configuration or generate a new key, the full key appears once in a dialog with a copy button — save it then, because it is not shown again. Leave the API Key field blank to have one generated for you, or enter a specific GUID when an integration already has a key it expects.
  • Vertical lines in the Print Designer. A new Vertical Line element joins the palette for dividing columns on callslips and invoices, existing lines can be flipped from the properties panel, and printed output renders them correctly.

Fixes​

  • Advanced search now honours field restrictions on custom fields. A custom field a role was blocked from seeing still appeared in advanced search — its values came back in the results, and it could be used in filters. Restricted custom fields are now hidden from the search field list, refused in filters, and left out of the results, matching how the grids, record pages, batch updates and printing already treated them.
  • The print designer's field list no longer offers custom fields a role can't see. A custom field blocked from a role by field restrictions was still listed in the print-template field palette (its values were already blanked on the printed output). It is now left out of the palette too, matching the advanced-search field list.
  • Custom fields can no longer be named after the field that identifies the record. A User custom field called Username, or a request one called TransactionNumber, could never be added to a field group — so its values stayed readable, filterable and sortable for every role however the restrictions were configured. Those names are now refused when the field is defined, and the field-group picker no longer offers them.
  • The user and request card designers now offer the institution's custom fields. User cards and the users grid display their values, and custom-field definitions that relabel User Info 1–5 show their configured names in the card designers too.
  • The users list can now filter and sort on the institution's custom fields in card view. Custom fields were already available from the grid's column headers but were missing from the card view's Filter and Sort menus, on both the Users page and the Search page's Users tab. They now appear there under Custom Fields with their configured names, dropdown fields offer their options, and the Search page's Users tab hides fields the role isn't allowed to see — picking one used to make the whole tab fail to load.
  • Requests from File now saves spreadsheets that include custom field columns — previously any custom field column failed the whole batch, and numeric or date custom field values typed by Excel were dropped.
  • Customization Manager search now finds every page by name. Searching "SSO" or "single sign on" now surfaces the Single Sign-On page, and the Field Customizations, API Keys, Logs, and Multi-Site pages are findable by their menu names too. Page-name matching now ignores punctuation and spacing.
  • Searching for a record from the screen it already lives on now opens it. Looking up a staff member from the Staff screen, or a role from the Roles screen, used to leave the page unchanged — the record only opened when the search was started somewhere else. Staff, Roles, Field Groups, and API Keys now open the record wherever the search was run from.
  • A new search no longer reopens the previous result. Starting a second search left the last search's hit on screen and still selected, so pressing Enter straight after typing reopened the record you had just been looking at. Results now clear the moment you start typing, and the list shows a searching indicator until the new matches arrive.
  • The Staff section now follows the Staff permission. Customization Manager search no longer returns staff names and usernames to roles that hold Roles & Permissions but not Staff, and the Staff entry in the navigation now follows the Staff permission that the page itself requires. A role with Staff but not Roles & Permissions gets a working Staff page: the fields that need the other permission — email address, sign-in method, SSO invitations, and role assignment — are shown read-only instead of failing when saved.
  • Multi-site: empty site groups no longer cause a silent login lockout. A staff account whose site assignments all resolve to no sites (an empty site group, or a direct assignment to a since-deleted site) was refused sign-in with "no site assignment", sending administrators hunting for a missing assignment when the real problem was the group itself. Login, the site picker, and the in-app site switcher now name the actual problem, and the Customization Manager flags empty site groups and stale direct assignments — in the group list, on staff assignments, and on the staff record — with what to fix.
  • Multi-Site contact information now falls back field by field. Anything left blank on a site's contact card inherits from the parent site and then the system Default on emails and printed slips, instead of going blank the moment the site overrides any one value. The editor labels inherited values explicitly. Because blank fields now inherit, a site that relied on leaving its contact email blank will send staff email from the first address configured up its chain — worth checking your Default row's contact email after upgrading.
  • Signed-in user info now reports every assigned site. The sites list on the current-user endpoint reflected only the site group flagged active on the account — a bookkeeping flag sign-in never updates — so it could disagree with the site switcher. It now lists the user's full entitlement: every site in every assigned site group.
  • Removed the deprecated site-group switch endpoint. The old site-context/actions/switch API changed only the account's recorded active group without re-issuing the session token, so the caller's actual site scope never changed. The switch-site action, which the client already uses, is the one way to change site context.
  • Expired-password reset now works for MFA-enrolled accounts. The reset screen asks for the authenticator code when the account has one enrolled, instead of failing with no way to enter it.
  • Authenticator-code fields now announce their helper text to screen readers. The hint under the code input (which code to enter, or that recovery codes are accepted) was previously visible but never read aloud.
  • Signing in now returns you to the page you were on, in two cases where it didn't. On installs hosted under a subfolder, being sent back after signing in could land on a "page not found" instead of the page you left. And if you were on a list filtered by a domain account — a value containing a backslash — signing back in dropped you on the dashboard rather than returning you to that filtered view.
  • The Activities list now shows the Activity ID. The grid gains a sortable Activity ID column, activity cards (Activities list, dashboard, and search) show the number next to the name, and the Card Designer can place it on activity card layouts. If you have any saved column layout (including saved views), the new column appears at the far right until you reorder it.
  • Inactive staff are now hidden in a role's Members tab. A "Show inactive" toggle reveals them, and inactive accounts are badged in both the member table and the Assign Staff picker.
  • Scheduled Date always shows the full date. Scheduled Date now displays as a full date with the year (e.g. "Aug 20, 2026") in queue lists, grids, cards, and the clone-activity dialog, instead of switching between a bare time for today and a year-less month/day for other dates.
  • The appointment detail panel now shows the other appointments in the same reading room that day — with overlapping times flagged — so staff can see the room's schedule before confirming, like the desktop client's Confirm Appointments screen.
  • Reading room closure exceptions save again when older exceptions hold legacy data. Validation errors now actually highlight the offending field — including revealing a hidden past exception when it's the one blocking the save.
  • Route by Access Restrictions. The routing rule builder's Transaction field list now includes Access Restrictions, so rules can route requests by their access-restriction text.
  • The Emails tab on a user record now loads and filters far faster on installations with large email histories. Previously it could take 10+ seconds per page because the sent-email table had no supporting indexes. The database upgrade builds three indexes on that table (large installations should expect the upgrade step to take correspondingly longer), which also speeds up outgoing-email processing.
  • Billing history shows real dollar amounts. Billing history entries (charges, payments, invoices) and invoice email amounts now show the dollar currency symbol instead of the generic "¤" placeholder, matching printed invoices.
  • Email template fields are no longer listed multiple times in the variable picker. On databases carrying same-named tables in extra schemas, Request and other fields appeared once per schema; the picker now reads only the schema the application itself uses.
  • Customization Tables column lists no longer duplicate on multi-schema databases. The Tables editor and implementation-module row updates now read column metadata from the same single schema the application itself uses.
  • Editor forms across Customization Manager no longer cram columns into narrow panes. Multi-column form layouts in the billing defaults, Z39.50, reading rooms, routing rules, and mapping editors now key off their own pane's width instead of the window's, so fields stack cleanly when the pane is narrow.
  • The Transaction Queue and Photoduplication Queue dropdowns no longer overlap. The email template editor now sizes its columns from the editor pane's own width, so the routing selectors stack instead of colliding when the pane is narrow.
  • Text typed into a Print Designer text box is now kept when you click away — it no longer reverts to "New Text". The floating toolbar's Bold/Italic/alignment buttons also show a clearly visible pressed state.
  • Delete buttons are readable again. Delete confirmation buttons across the app now render white text on red instead of hard-to-read dark text — the destructive color token was never defined, so those buttons failed contrast.
  • Corrected the Single Sign-On Advanced (JSON) description. It referred to a "Configuration tab" that no longer exists; it now explains that saving replaces the provider document wholesale without touching settings stored outside it.
  • The Alma/Primo Catalog Search addon (v2.4.1) now shows Alma's actual error reason — for example "UNAUTHORIZED: API-key not defined or not configured to allow this API" — instead of just the HTTP status when a holdings lookup or import fails.
  • Photoduplication tour copy corrected. The Photoduplication Workflow guided tour no longer describes the status badge as teal — the badge is colored by the order's current status; the tour now describes it by its copy icon and status coloring.