Important notices

This page provides warnings about changes in the new version of the product that may cause problems when upgrading from the previous version or when running the new version. Please read this information carefully before upgrading to the new version.

It is also recommended that you read the list of subsequently identified issues in the released versions and their solutions, see Known issues.

Core features

Deprecated database views Query.Computer, Query.Node and Query.User has been deleted. (T142286ALVAO)
In case you have changed NLog.config files for WebApp, Asset Management WebService, or Custom Apps WebService, after the upgrade replace their content with the content of the corresponding SampleNLog.config file. After this, re-apply your custom changes, if necessary.
For the Alvao Service and the Intune Service, after the upgrade replace the content of the appsettings.json files with the content of the corresponding appsettingsSample.json file. After this, re-apply you changes (i.e., the database connection string) to the appsettings.json file according to Alvao Server - manual installation.
When importing users from Azure via SCIM, the value of Job information/Adress is now mapped to the tPerson.sPersonOffice column. (T154481ALVAO)
The AlvaoRestApi and AlvaoRestApiWinAuth server components now need .NET 6 and ASP.NET Core Module for IIS. Also both these components need to run in separate app pools. See installation and requirements for details. (T129741ALVAO)

ALVAO Asset Management

Asset Management Analysis – the Excel workbook was removed from the product. For reporting use the Power BI report templates. The Excel workbook from the ALVAO version 11.1 will still be usable with the ALVAO version 11.2 applications. This compatibility is not guaranteed in the next versions. (T139578ALVAO)

ALVAO Service Desk

Tickets – service team members of a parent ticket now see also all the child tickets, though they have assigned no explicit permission. (T139553ALVAO)
Service Desk Analysis – the Excel workbook was removed from the product. For reporting use the Power BI report templates. The Excel workbook from the ALVAO version 11.1 will still be usable with the ALVAO version 11.2 applications. This compatibility is not guaranteed in the next versions. (T139578ALVAO)
Service catalog – requesters can navigate to any service with SLA assigned to them even though they have no SLA for the parent services. The child services with SLA assigned are now accessible automatically without the need to set SLA to the parent services. If you want to hide some services from requesters, use the View in service catalog option. (T132815ALVAO)
Ticket – Communication - Detailed log – Ticket field value change records – ambiguous date and datetime field values (e.g., 2/1/2024 for British and US format) in the detailed log records may by interpreted in wrong format after the upgrade if the author of the change prefers a different than one of the supported languages or their preferred language changed over time. (T108857ALVAO)
Text of the custom notification for Ticket due date changed is saved in the ticket log instead of the system generated log record text. (T142106ALVAO)

Extension modules

ALVAO Standard HW/SW Request Forms

Both forms are now part of the WebApp. Use the system forms instead of the custom forms if possible. Migration includes several steps:
1. Import example service with custom columns or create custom columns manually.
2. Transfer settings from the code in HW form to service custom columns. Instead of category ObjectKind parameter change the type of the objects to Request for HW – category.
3. Set new custom form URL for the service.
4. For more information see ALVAO Standard HW/SW Request Forms. (T124138ALVAO)

ALVAO for Teams

REST API URL setting is removed. Configuration of Alvao tenants is managed by the ALVAO company. (T134042ALVAO)

ALVAO for Outlook

REST API URL setting is removed. Configuration of Alvao tenants is managed by the ALVAO company. (T134042ALVAO)

Did not find what you were looking for? Ask our technical support team.