Skip to main content
Matrix42 Self-Service Help Center

Migration to UUX


Many customers, who used Classic UI in production, want to understand what they have to do in order to run their daily business on UUX, and replace Classic UI

This article explains what is automatically migrated, how to migrate customizing and what is the corresponding feature in UUX they used in Classic UI before



Classic UI to UUX features comparison

In UUX there were many changes done to existing functionality, some former known things that are no more used, and new ones appeared

"Configuration Items" and "Data Definitions"

Structure of Configuration Items and Data Definitions in the database in exactly same in Classic UI and UUX.  It is possible to change database in both systems in the same time

As for User Interface for Configuration Items, it is now configured independently in UUX->User Interface->Layouts->Dialogs. 
It is possible to create set of Dialogs for same CI. The dialog is designed in Layout Designer and can be limited by Application or Audience(User, Role…)

"Object Details"

Object details, in the past, was in most cases delivered only by Matrix42, and customization was hardly possible. In UUX, it is replaced with Previews, that support customization with Layout Designer


It is replaced by new Configuration Item "Application" in UUX.  All default application and navigation structure is available after update with same permissions as in ClassicUI as we do the migration for settings for default objects with an update. However, for migration of custom Workspaces and Navigation items Migration tool needs to be used
Workspaces in Classics UI


Global System Settings

In UUX, settings for business flow configuration uses exactly same data as in Classic UI, so can be configured in both places in same time. The difference is in the display. Now, Service Desk manager, for example, can configure Service Desk functions, without having access to Administration application
“Settings” navigation item is automatically shown in the application when there is at least one Object Preview for Global System Settings CI available for that application. That means it is possible to create settings for your custom application as well.

In Classic UI – only one dialog for changing settings is available in Administration


In UUX , in every application, there is Settings Navigation item, that opens Preview for dedicated Settings of current application. It is possible to customize/create new one in the same way as other Previews/Dialogs in UUX



"Tabulators" and "Search Pages"

In UUX this is replaced with several new Configuration items to have more flexibility. "Navigation Item" needs to be created to show application structure. However,  it can be configured to open "Dataset View", "Open some URL", "Landing Page", "Execute some Angular Controller" or "Behave  as simple container"

For instance "Search Page" is replaced with "Data Set View", which now can be shown not only as grid, but as List, Tile, Calendar.

"Dynamic Structure"

A structure with option "Dynamic"  is replaced with new Configuration Item "Structure", which looks almost same as in Classic UI. It is possible to define structure in Navigation Item that is based on Dataset view

Static Structures

Static structures, are replaced by Search Filters and are based on Condition Designer, which allows building filters even by End Users

"Column Settings"

Column Settings are replaced with new Configuration Item "Data Queries"

"User Roles"

User Roles are exactly same configuration item for UUX and Classic UI. Permission for CRUD operation can be done in both places in same time.  However, UUX delivers possibility to define Audience based on User Roles for "Dialogs", "Previews", "Search Filters", "Navigation Items",  "Actions"


Actions are replaced with new Configuration Item "Actions".  It has most of the configuration as in Classic UI by Configuration Items, Status, etc. However, it is also possible to filter by Application, Device. In the past, action had much less implementation types that in UUX now. Here it is possible to "Run Wizard" what can be also designed, "Open URL", "Open Dialog",  "Call service operation" or "Run Workflow"


Wizards are new Configuration Items, we can be designed in Layout Designer. It is possible to create Wizard that calls Service Operation or collect information and pass to workflow

They are customizable in the same way as Dialogs. Most of all default product wizards has been already migrated and are available in UUX. Custom wizards need to be created by a customer by his own


Dashboards are replaced with new Configuration Item "Landing Pages". It looks similar to Dialogs as can be designed in it. Chart controls are available for use in Landing Pages. 

E-Mail Designer for E-Mail sent by Compliance Rules

Compliance Rule got new E-Mail designer. The script for migration of custom Send Emails to it will be provided with the release. However, old emails can still be in use for now but can be configured only on Classic UI. A customer can enable new emails based on E-Mail designed by switching option


At the moment, in UUX, when you open Reports, an exactly same website is opened as in Classic UI

Service Forms for Service Catalog

In Service Catalog, form, that was created by Customer, needs to be migrated to UUX. That mean Dialog must be created with Layout Designer. Migration tool can be used to do migration faster


In UUX, we show help link, which is different for every application. As soon as migration for the specific application based on UUX will be available - links will be updated

Functionality which is same in UUX and Classic UI

Data Providers, Import Definitions, Domains, Compliance Rules(except new feature Email Designer), Data Gateways, Server Inventory, Workflows, Engines, and Activations, Sent E-mails and E-Mail signatures remain same. Most of business module function are going to be similar to those we have in Classic UI. However, new features, like support of Ticket and Service Request, for example, is available only in UUX.

Customizing the appearance of Portal

It Classic UI, it was possible to customer appearance of portal only. Now, this is standard administration functionality called Themes. It is possible to change styles, colors, avatar by configuration only

Migration of product configuration

Permissions will be automatically applied to product default objects, like Navigation Items, Dialog

Migration of customizing

Migration Tool,  which was released together with 8.1.5 release, comes together with the installer.

What is possible with Migration Tool

Custom CI Dialogs, which were generated with Form Designer in Classic UI , will be migrated to UUX Dialogs
Also, we will automatically create Previews in UUX base on that Dialogs
Custom tabs which were added to default Dialogs in Classic UI will be  migrated and added to default Dialogs in UUX
Grid Layouts which were created by you will be migrated (Colors, color/image pickups will be also migrated)
Workspaces you created will be automatically migrated to Applications in UUX
All  Tabulators, Search Pages you created will be migrated to corresponding Navigation Items, and DataSet Views in UUX
Static structures will be migrated to Search Filters in UUX
The dynamic structure will be migrated to Structures in UUX
Permission for Actions, Dialogs, Previews, Navigation Items, Service Operations will be copied from Classic UI to UUX for existing or new roles you added
Customization recorder will track of all items which were migrated (mean, you need to start recorder before migration, do the migration, change items after migration, export change with the recorder and install on the production system)

What is not Possible with Migration Tool

A tool will not migrate changes done in form designer for product default dialog tabs, only custom dialog tabs are migrated
A tool will not migrate custom controls (in such dialog You will see the message in UI that part of the layout was not migrated because control is custom)
A tool will not add/remove columns for default Grid Layouts/Data Queries you added
Actions/wizards we will be not migrated
Permissions will be not removed, from existing roles, only added. Disabling permission needs to be done manually
Quickstarts, Dashboards will be not migrated with the tool

Migration Tool installation

You need to install it as regular hotfix  by calling cmd file <InstallationFolder>/Config/Migration.bat
After installation you will find new management area in Administration->Integration->Migration

Migration Process

To start the migration process, you need to click on Migration link, which will open migration wizard
You are able to select Workspaces from old Console which will be mapped to Applications in UUX
Application, Navigation Items, SearchPages, GridLayouts, Static and Dynamic Structures will be migrated for Selected Workspace
Deselecting option "Migration all dialog", gives the possibility to migrated only selected Dialogs(Dialog and preview will be created). 
After pressing selecting option and press the "Migrate" button in the wizard  - you need to wait several minutes until Migration Summary page will be shown(see next image)
Here you can see what was changed in UUX. Click on links will show details and you can go through every change, open it in Layout Designer, adjust for your needs

 For now, in Migration tool (preview) you will see the results of default product migration and your customization together, This will not happen for 8.1.5 release, With 8.1.5 you will see the only customization you did, nothing about the product

In case some items are not shown in UI, after migration: do iisreset and clean browser cache and check them again

To analyze migration result, you also have access to Errors, Warnings in UI

To prevent unexpected behavior of the System, the Dialogs created by the Migration Tool are not published, and only the Person who initiated the migration process can see that. Each of them needs to be reviewed in Layout Designer, and tested, to assure it works as designed. Or in case of using Custom Control in old From Designer, which has not been migrated, the functionality needs to be manually recreated in a migrated Dialog. Once the Dialog is polished, it need to be published to make it accessible for the rest of the Organizaiton.

After the Migration, the migrated Dialogs are accessible only to a Person who initialized the Migration Process. To make them available for others, they need to be reviewed and published

How to migrate the same Dialog one more time

To migrate dialog and preview from classic UI to UUX You need to do following:

  1. Determine migrated Type ID. The easiest way is to copy ID from the dialog. To do that navigate to the proper Configuration Item (Schema -> Configuration Items) open it in Edit mode and click on 'Advanced' tab.
  2.  Remove an entry from migration history table by following SQL script.
    Declare @TypeID uniqueidentifier = '{0}' --where {0} is id of migrated configuration item
    DELETE FROM PDRMigrationHistoryClassBase WHERE [System] = 0 AND SourceEntityKey like CAST(@TypeID AS NVARCHAR(36))+'%'
    DELETE FROM PDRMigrationHistoryClassBase WHERE [System] = 0 AND SourceEntityKey IN (SELECT CAST([Expression-ObjectID] AS NVARCHAR(36)) FROM SPSContentClassObjectDialogTab WHERE ObjectType = @TypeID)
  3. Search the necessary Dialogs/Preview in UUX->User Interface->Layouts that you want to migrate again
  4. Remove Dialog/Preview from UUX->User Interface->Layouts using action Delete
  5. Start Migration wizard again

Note: Migration Tool should be re-installed after the application was updated by calling cmd file /Config/Migration.bat

  • Was this article helpful?