• Worker technology will replace AppFabric and Data Gateways covering the same functionalities with no extra costs and license certificates

• All custom workflows based on Matrix42 out-of-the-box Workflow Activities (except “Invoke PowerShell”) will be automatically migrated to Workers.

• Not supported Workflows will continue working as before, using AppFabric Engine with no impact to system functionality

• Setup Wizard will execute validation automatically and attach information about legacy usage as a warning to the Installation summary report

https://matrix42.aha.io/attachments/7018159161764072684/token/e0c995f123b941af14fd5acab375fe6173209a1f93f4ce862c57aff169dd1e51?size=original

What about new Installations?

• New Instances operate in Worker only mode

• AppFabric and a set of other 3rd party components are not required anymore

• AppFabric Workflow Engine, Data Gateway service, Alerting (Legacy Email Engine) are not installed anymore and therefore no configuration available at Setup Wizard or inside UUX

• Administrators can see warnings about legacy usage in the administration system status dashboard in real-time

• The Dashboard is automatically refreshed

The look and feel of Matrix42 applications is the (first) impression that the user gets of our low-code platform. So, it has to be attractive, properly organized, fast, and has to fit the company’s overall framework.

Unified Search Experience provides an optimized User Experience for End User application built with Matrix42 Low Code Platform

Every page in the application contains a new search component
Control replaces global search from the application toolbar
Control replaces “keyword” search for dataset views
Search contexts are now grouped by a root navigation item

Configuration

Unified Search Experience comes deactivated by default

Available with DWP subscription only

Unified Search Experience can be activated per application

The best background Image and color are set for default themes, however, it is possible to configure your custom ones

Enable the possibility to work with such Cloud API as "Adobe Cloud" (AEM) and "Google Cloud" (Google API - Service Accounts) extent the Service Connection with a new authentication type "JWT Authentication".

The key particularity of the Flow, the JWT token used for request the "Access Token" is signed with the Private Certificate.
JWT token format:

{
  "iss": "761326798069-r5mljlln1rd4lrbhg75efgigp36m78j5@developer.gserviceaccount.com",
  "scope": "https://www.googleapis.com/auth/devstorage.read_only",
  "aud": "https://oauth2.googleapis.com/token",
  "exp": 1328554385,
  "iat": 1328550785
}

Google API: https://developers.google.com/identity/protocols/oauth2/service-account#httprestAEM: https://experienceleague.adobe.com/docs/experience-manager-learn/forms/aem-forms-with-adobe-campaign/partone.html?lang=en

Extend the Service Connection Service dialog to support JWT Token:

For LayoutDesigner create a new non-visual control descriptor that will be responsible for showing the new Search component on Landing Pages (fixed top area). The same way it is shown for Unified Search Experience mode. The contexts of a search can be configured per control on a specific Landing page layout.

This will make obsolete the old search controls descriptor.

There is no need for the migration of existed layouts.

An option "User must change password at next logon" for the user account should be available in the General Settings.

Similar to the already existing Workflow to assign an AD account to an AD group, AAD group membership will be managed using the service catalog provisioning.

Assign account to AAD Group

• Maria is asking permission to a resource controlled by an AAD Group.

• Maria selects the service XY and places the order

• After approval, service provisioning starts

• Marias AAD account is assigned to the service-defined AAD group

Remove account to AAD Group

• Maria was asking permission to a resource controlled by an AAD Group.

• Maria no longer requires this permission and returns the service XY by placing a return-order

• After approval, service provisioning starts

• Marias AAD account is removed from the service-defined AAD group

Currently, global service catalog filters do only allow settings that get applied to all services and targets (account, computer); thus more detailed filters are not possible.

As a result accounts from AAD are available on AD-only services which lead to issues during automated provisioning.

Filter settings are applied directly at the service once the target selection is defined. To allow complex filters the setting will be done using A-SQL.

The author or manager of an extension is able to see the installation statistics by version and timeline.

In case of failed installation, the author can access the installation log