Alemba - Alemba Service Manager version 10.2
Demo Contact

Alemba Service Manager version 10.2

Release notes

Information

X Notable Prerequisites

  • .Net Core Hosting Bundle 2.2
  • This may also require installation of C++ 2015 Redistributable on older versions of Windows
  • Dynamic Content Compression should be enabled
  • Full-Text and Semantic Extractions for Search for SQL Server
  • Valid subscription for the Azure Translator Text API.
    Only needed for on-demand translation of descriptions and search results in the Self Service Portal

New Features

X New Portal Landing Page

The portal can now be accessed using Portal.aspx.

Existing users will be redirected to this page when they try to access the portal in ASM 10.2.3 using bookmarks, MMA URLs, etc.

X New Portal System, Skin and Home Page

A new Portal System named “ASM 10 Default” is added during the upgrade to 10.2.2.

This system is configured to use the new portal Skin and the new Home Page.

The existing “Default” and “Classic” Home Pages have been renamed to “vFire 9 Default” and “vFire 9 Classic”.

You are now able to opt-in to the new portal styling using the new Portal System.

Skins

Dashboard

X New Grid Widget - Calls Awaiting Action By Your Organization

This widget is hidden by default and can be enabled via the screen designer.

The grid will show calls logged by anyone in your organization (subject to portal security settings) and where the Awaiting Action indicator on the Call Status is checked.

Calls awaiting action

This new widget uses the API for data access and uses server-side paging for optimal performance.

X New Grid Widget – Most Recent Calls

This widget is hidden by default and can be enabled via the screen designer.

The grid will show calls logged by anyone in your organization (subject to portal security settings) with newest calls at the top.

Most recent calls

This new widget uses the API for data access and uses server-side paging for optimal performance.

X New Grid Widget - FAQ

This widget is hidden by default and can be enabled via the screen designer.

The grid will show the 10 most popular FAQs.

FAQs

This new widget uses the API for data access and uses server-side paging for optimal performance.

X New Info Panel in Call, Request, Asset and Knowledge review screens

Info panel

We plan to make this section designable in future.

X New Rich Text Editor support in the Portal

Opt-in via the setting in Preview Features.

X Enhancements to Portal Home Page screen designer

Widgets can now be hidden and reordered via the designer.

You can also add any of the new widgets to the dashboard using the Dashboard Widget.

Home screen designer

We’re planning further improvements to this in future.

X New Image section in the Organization Details screen

Organization details image section

New image

X Change Collision Detection in Request screens

A yellow warning indicator if there is another Request related to the same CI or Service.

A red indicator will be displayed if there is another Request with an overlapping implementation date.

Conflicting Change Indicators

Enable “Conflicting Change Indicators” in preview features to opt-in to this new feature.

Security Enhancements

X Enhanced Password Complexity

We’ve added several new options for password complexity validation, including the ability to configure reCaptcha v2 on the portal change password screen.

Password complexity

X Enhanced Session Security

The Portal and Nano no longer transmit Session ID’s in query strings or forms. Both use a cookie for authentication instead.

This solves one of the most important security problems reported during penetration testing.

This also means that the login restrictions in Nano and the Portal are brought into alignment with the restrictions in Core.

X Enhanced Dashboard Permissions

We’ve repurposed the old Reporting Role. It’s now called Dashboard Management.

The Dashboard Role can be used to grant access to Categories that have been created through the Dashboard Designer.

Dashboard security role

There is also a new Portal Role that is used for the same purpose.

The categories and related dashboards will appear in the navigation menu in Core and the Portal based on the current user’s role.

This enhanced functionality replaces the original static menus.

New menus

Performance Enhancements

X ASM Core load speed

ASM Core now loads significantly faster and is significantly more reliable.

Dynamic Content Compression should be enabled in IIS for maximum performance.

Dynamic Content Compression in IIS

Other Improvements

X Improvements to Windows Authentication

A new web application (aka Virtual Directory) is created during the installation of ASM 10.2.3. The new web application is named Alemba.Web.Windows and is used during the windows authentication process when logging in to ASM Core.

This change should make windows authentication a little easier to configure and will resolve issues where the windows login prompt is occasionally displayed.

X Critical fixes to the API and Dashboard platform

It is now possible to select extension fields from subtypes when using navigation properties via the API.

For example, extension fields added to the Desktop screen set were not accessible when selecting from the Call entity. Select statements such as $select=ConfigurationItem.Ext_DesktopType are now supported.

This change also means that searches of a base entity (i.e. Call, ConfigurationItem, Person) will now support selects of extension fields from sub types (e.g. Incident, Desktop, User). There are also a handful of fixes in the dashboard platform that will improve performance when using the API Data Source.

In addition, the Dashboard user will no longer consume a named license.

X Improved Portal System Persistence

The selected portal system is sometimes lost when logging out or navigating to particular pages in the portal.

The selected portal system is now persisted using a cookie.

This means that the portal system selection will be maintained more reliably. It also means that you must explicitly select the default system (using portal.aspx?portal=DEFAULT) rather than selecting that system by omission.

X Additional SAML Trace Output

ASM will now write more information related to SAML login, to the traces for ASM and Alemba.Web.

This includes the SAML Response XML.

The XML in this response contains sensitive information so is not written to the trace unless tracing is enabled. This is done via the server console for Portal and Nano and via the web.config for Alemba.Web for Core and API login.