Known Error handling is better aligned with ITIL4 practice. Reduced complexity allows faster processing of items by service desk agents/problem responsibles.

• Workflow, Wizard and journal entry (when, who, comment, flag/unflag) for flagging a Problem as Known Error.

• Adjustment of Known Error navigation item to support current and new way. Reports need to be checked if adjustments are required.

Matrix42 online help

Improved end user satisfaction due to additional step prior closing a ticket. Adds the possibility of accurate solution time reporting.

•Transfer of process for pausing a ticket with reason ‘Waiting for customer acceptance’ to closing a ticket with resolved status.
•Adjustment of Service Desk global settings to reopen tickets by adding a ‘reopen until x days after closing’ option to avoid customers having the need to write javaScript.

Matrix42 online help

The application navigation items depending on the nesting level are displayed either in Left Navigation or on Page menu

Left Navigation

Displays only the top 2 levels of the Navigation structure

Collapsed Left Navigation

Shows only top-level Navigation items as icons.
The second level items displayed as popup menus on hovering the "top navigation item"

Expanded Left Navigation

Page Menu

Renders all navigation items with nesting level "3" or lower

When the application has level 4 or lower, the UUX allows open popup menu under corresponding 3-level item

Dialog Tabs

The Recent Panel is removed and dialog navigation moved on top of the dialog page

Deep Linking

The deep link to open the pages in classic-UUX can be used for Modern-UUX.

https://www.figma.com/proto/FEmJWVybPYGrQSCe7iHOj0/UUX-improvement-2022-(25-11-2022)?page-id=0%3A1&node-id=29%3A9717&viewport=-129%2C326%2C0.06&scaling=scale-down&starting-point-node-id=29%3A9717&show-proto-sidebar=1

Remove Dataset Views filters from the Navigation and display them as chips on top of the Dataset view

"Migrating" Filters

In modern UI, Search Filters do not have the hiearachical structure, and displays all filters as flat list. From another hand for the Update Environments the filters in classic UUX shoud stay the same and keep working as before. Also the deep linking urls generated previously on classic UUX should work the same on Modern UI and apply the same conditions to filtered data

Navigation Default Filter

In Navigation Item is a possibility to specify the default Filters. Provide a posibiilty to specify multiple filters. If old UI is active and multiple fitlers are specified for the Application, apply only the first valid (allowed for old UI) one.

Editing Filters

https://matrix42-my.sharepoint.com/personal/darya_pochtennaya_matrix42_com/_layouts/15/stream.aspx?id=%2Fpersonal%2Fdarya%5Fpochtennaya%5Fmatrix42%5Fcom%2FDocuments%2FMicrosoft%20Teams%20Chat%20Files%2Fsearch%20Advanced%2Emov&referrer=Teams%2ETEAMS%2DELECTRON&referrerScenario=p2p%5Fns%2Dbim&ga=1

https://www.figma.com/proto/JH8llIosD4nvILVutnOvNz/UUX-improvement-2022-(02-11-2022)?page-id=0%3A1&node-id=356%3A161628&viewport=35%2C435%2C0.02&scaling=scale-down&starting-point-node-id=157%3A78935&show-proto-sidebar=1

The customer (enterprise administrator) should be able to manage existing service connections generated by approvals or from the DWP in the Matrix42 Accounts Management portal. This is important to remove permissions granted to external service provides by accident or when the service provider agreement is expired. All service connections should be rendered in a new tab called "Service Connections":

Every service connection represented by an oAuth Client in the ACS should be visualized as follows:

The customer has the right to execute a remove operation. This will remove the associated oAuth2 client and breaks the service connection in the referenced system. As this is a destructive operation, the user should be warned and needs to enter a verification challenge, e.g. Yes or the name of the extension or whatever.

The Flow Action Property value can be assigned dynamically in run-time from the Context variable.
Example: For the case when the order must be approved by the requestor manager, the Decision Maker User needs to be taken from Booking.Requestor.Manager

Extend Object(s) Control in Workflow Designer

On typing text in Object Picker or Multiple Object Picker, the Workflow Designer analyses the actor input and dynamically builds the dropdown panel in the following structure:

The Context shows only the variables from the current scope which potentially could lead to selecting a valid value selection. For example, in the picture above the BookingCount could not be an option, as it is not possible to turn the Interer value to reference to a Person, whereas the Object is always an option, as using the object's relations is always possible to select the right value

ASQL Builder

The Workflow Designer provides an easy and user-friendly and fully declarative way to build the Data Columns Queries (ASQLs).

The Builder allows to select of object property which fits the Object(s) Designer configuration. Taking in mind the Decision Maker Users property only the relations to a single Person or multiple Persons can be selected. Until the right relation is selected the "bound chip" stays in misconfigured position and has the appropriate highlighting. In this case the whole Flow Action is configured, and the Flow is invalid.
Relations that lead to target object, are highlighted in dropdown menu (e.g. Requestor or RequestoFor are relations to Person, what is a target for Control).
All
The DropDown shows all relations to other objetcs, and omits simple properties (int, strings) as the Property expects and object as result, and there is no way from simple type gets a relation.
For FLow Action Properties of type "Interger" the Builder omits strings, datetime, etc. Object properties

Introduce Flow Action Conext

See section "Workflow Context"

https://matrix42.sharepoint.com/:w:/r/sites/M42_Production/_layouts/15/Doc.aspx?sourcedoc=%7B0E65C78F-763E-47BD-880F-CD845A3224B9%7D&file=Workflow%20Designer.docx&action=default&mobileredirect=true

Strings are the most popular type for Flow Action Properties, therefore it is vitally important to have a Text designer which helps the Flow Author to design a proper string for a property for each concrete case

At first iteration focus only on the Plain Text editor without placeholder support.

Appearance in Workflow Designer Property Panel

As textbox with the extra icon-buttons:
"Localizations" icon when Property required localization, opens the Localization String Editor

"Extend" - collapse/extend the textbox to the whole propety panel. When multi-line is configured then on extended mode allow break lines

See section "Text Editor"
https://matrix42.sharepoint.com/:w:/r/sites/M42_Production/_layouts/15/Doc.aspx?sourcedoc=%7B0E65C78F-763E-47BD-880F-CD845A3224B9%7D&file=Workflow%20Designer.docx&action=default&mobileredirect=true

For the Approval Processed designed in Workflow Designer show in progress of the Approvals in Portal (the same way it is implemented for processed created in Workflow Studio)

For the Flow Action "Approval" introduce the new optional properties:

• Approval Step Title
  Type: String, Editor: Text, localizable, static, single-line, required

Transform to Xaml

On transformation, the order of "Approval" actions is analyzed, and Xaml Approval Workflow is generated in a way the provided Approval Titles and Icons build the corresponing Approval Process Steps, and proceeding with Approvals are correspondingly displayed in Approval Process Progress bar

Members of the Administrators role should be able to access a license monitoring dashboard that provides an overview of all valid, expired and overused licenses, including information about the license type, the number of users/assets covered by the license, and the expiration date of the each license. The dashboard should also display the current count of active users/assets in the system.

The Administration -> Home page should display a Quick Start link that, when clicked, directs the user to the Monitoring dashboard.

Available licenses should be displayed in a list sorted by Product Name (default sorting).

Every list item should contains the following information:

1. Color indication about any error, warning or info message available.

2. Icon that indicate that specific license in use.

3. Product name + Customer name ("Name" label).

4. License type ("Type" label).

5. Current usage + Available licensed number ("Usage" label).

Licenses check performed as a part of System diagnostic process.

Diagnostic rules:

1.Verify that integrity of the licenses

Status: Error

Condition: cert can't be read or unsigned

Message: Some licenses have been identified as corrupt. This may be the result of either a file access issue or as invalid signature.

2.Verify that licenses not reached their expiration date

Status: Error

Condition: License expired (expiration date plus at least one day). If multiple licenses presented for a single product, only license with latest "Create Date" should be considered.

Message: Some license have expired.

3.Verify that number of Managed Users or Assets in use has not exceeded the licensed limit

Status: Error

Condition: Current Managed Users/Managed Assets count exceed licensed count (license count plus at least one Managed User/Managed Asset). If multiple licenses presented for a single product, only license with latest "Create Date" should be considered.

Message: The licensed number of Managed Users or Assets has been exceeded.

4.Verify that licenses are not approaching their expiration date

Status: Warning

Condition: License expired in 28 days (4 weeks). If multiple licenses presented for a single product, only license with latest "Create Date" should be considered.

Message: Some licenses are approaching their expiration date.

5.Verify that number of Managed Users or Assets in use are not approaching the licensed limit

Status: Warning

Condition: Current Managed Users/Managed Assets number reached 95% of licensed count. If multiple licenses presented for a single product, only license with latest "Create Date" should be considered.

Message: The number of Managed Users or Assets is approaching the licensed limit.

6.Verify that licenses are not duplicated

Status: Info

Condition: Duplicated or multiple certs for specific product.

Message: Multiple licenses have been found for a specific product. This may be due to unused or outdated licenses.

User Problem

Data Queries may contain values with sensitive data.

Users from one role are allowed to see less than user from the role with higher privileges.

This can be achieved with the help of configuring audience for Data Queries and sharing only allowed information

Usecases:

IT can create multiple data queries for same entries in the UUX

Data Query can be share with action "Set Audience"

In case of multiple dataquiries availailbe for the user, one with highest priority becomes available

Modernized style and color for Dashboards

Members of the Administrators role should be able to observe license details by clicking on a specific list item.

This info should be displayed in a standard side panel.

List View item details should contains the following information:

1. • Product name + Customer name as a header

   • Product name

   • License type

   • Current number of Managed Users/Assets

   • Licensed number

   • Customer name

   • Create date

   • Valid until

   • License file name

   • Error/warning/info message if presented