Axians
Key visual release notes

Axanto Portal 4.2 is here!

Author:

axantoDev

Tags:

Axanto Portal 4.2 is here. Data and users can now be separated by tenant, the setup supports Kerberos and group Managed Service Accounts, and an update that fails at the database leaves the previous version in place.

What’s new

Tenants

Data and users can be separated by tenant: a user only sees the tenants they belong to. One portal can thus serve several customers or organisational units without any of them seeing the others’ data.

Setup and operations

  • Kerberos: the setup switches Windows authentication on /api and /legacyapi to useAppPoolCredentials, so Kerberos works with an SPN on the service account.
  • gMSA: a group Managed Service Account can now be used as the service account.
  • Safer updates: if the database step of an update fails, the previous version stays installed with its configuration. Large databases no longer fail on the time limit of that step.
  • Troubleshooting: when an installation fails, the setup shows where its log file is and can open it. The log contains neither the database connection string nor the licence key.
  • Proxy: AI similarity search and indexing use the proxy configured for the portal, and the CVE synchronisation in Patch Manager also works through a proxy that requires a password.

More new features

  • The global search field in the top bar is easier to see and read.
  • The product help can be opened without signing in.
  • External Ingest: the key of an existing source can be renamed, and the configuration can be exported and imported as JSON.

What else we took care of

4.2 contains 34 fixes. Changes that Service Manager refuses – such as skipping an activity without permission – are now reported instead of appearing to succeed, and a failed save to Service Manager shows an error. Comments and attachments are no longer lost on save when a relation arrives empty. The portal no longer crashes when it runs over HTTP and you paste from the clipboard. And the database gets noticeable relief: user lookups no longer scan the whole table on every request, the scheduler no longer reloads its configuration twice a second, and the nightly change-history cleanup deletes in batches.

Upgrading

From 4.1, the update is a regular setup run; the database is updated automatically. 4.2 also fixes two faults in the database update from 4.0, including the abort with error 13539 when the executing login has no default schema. Upgrading from 3.72 is unchanged: please plan it together with your Axanto contact and read the Upgrade Runbook in the product help beforehand.

Changelog

The complete list of changes, as it also appears in the CHANGES.TXT of the delivery:

Feature

  • AX03025 Reviewer voting commits through a dedicated endpoint instead of the generic relation
  • AX03074 Data and users can be separated by tenant, so a user only sees the tenants they belong to
  • AX03127 Setup: enable useAppPoolCredentials for Windows authentication on /api and /legacyapi (Kerberos with SPN on the service account)
  • AX03133 Extend X-On-Behalf-Of to QuickSaveEntities and CreateEntityXml
  • AX03135 External Ingest: the key of an existing source can be renamed
  • AX03136 DBService: query the GUIDs of all SCSM objects of a class, including derived classes
  • AX03142 When an installation fails, the setup now shows where its log file is and can open it
  • AX03148 Release notes can be exported by product version for automated builds
  • AX03151 Global search field in the topbar is hard to see and read
  • AX03152 ReadSolrMetadata warning logs the owning list and column/alias

Bug

  • AX03023 Generic save deletes comments and attachments when a relation arrives empty
  • AX03036 Solr service: end the Solr process reliably on service stop
  • AX03041 User lookups no longer scan the Users table on every request
  • AX03042 The scheduler no longer reloads global configuration twice a second
  • AX03043 The nightly change-history cleanup now deletes in batches instead of one transaction
  • AX03115 An update whose database step fails now leaves the previous version installed, with its configuration
  • AX03116 Updating a large database no longer fails on the time limit of the database step
  • AX03117 The installer log no longer contains the database connection string or the licence key
  • AX03118 Service Manager selection lists are loaded in the legacy API, so reading a request offering with preset list values no longer fails there
  • AX03119 Service Manager items saved through the legacy API keep their AI similarity search data
  • AX03121 AI similarity search and indexing now use the proxy configured for the portal
  • AX03122 The CVE synchronisation now works through a proxy that requires a password
  • AX03123 Product help can be opened without signing in
  • AX03125 Default relation with a non-existent target is skipped with a warning instead of failing with a SQL error
  • AX03126 Switching an ingest rule's source mode no longer changes a different rule
  • AX03128 Portal shows an error when saving an entity to SCSM fails, instead of showing nothing
  • AX03130 Choosing a date filter condition ("is before", "is after") no longer opens the entity underneath
  • AX03131 On-behalf-of: comments saved with an entity are attributed to the service account
  • AX03132 Add JSON Import and Export for External Ingest Configurations
  • AX03134 Solr identifier filter migration: Apply did not save changes to tabs when run for a module
  • AX03137 Opening the create dialog of a notify message group fails with an error
  • AX03138 Setup: support a group Managed Service Account (gMSA) as service account
  • AX03139 Changes refused by Service Manager (for example skipping an activity without permission) are now reported to the user instead of appearing to succeed
  • AX03141 Corrected the manufacturer address and contact email in the license agreement and the license expiry message
  • AX03143 "crypto.randomUUID is not a function" error and crash when pasting from the clipboard while the portal runs over HTTP
  • AX03144 Detail view: form jumps for JavaScript fields with long content
  • AX03145 JavaScript field: script runs on every change detection
  • AX03146 Admin UI property editor: no textarea height for JavaScript fields, FieldType hidden after catalogue pick
  • AX03147 Admin UI list column editor: FieldType select never shown
  • AX03149 V4 upgrade fails with error 13539 when the executing login has no default schema
  • AX03150 Customization module tables (CustomizationModules, Tabs, Actions, NavigationItems) created without [dbo] schema prefix in upgrade script
  • AX03153 Review scheduler: an empty Count or Enabled cell in a record's review table no longer skips all of its reviews
  • AX03154 Fix silent 404 on request paths containing duplicate slashes
  • AX03155 Scheduled review creation fails when DateCreated is required on EntityReviewSchedules