Introduce the possibility that allows configuring email setting with various Email parameters dynamically by configuration, not only by code. Such capabilities provides a possibility to configure different mails formating ("corporate identity") for different Departments. For example, the styling of mails from the IT department could be absolutely different.

The following Emal artifacts could be redefined for different departments:

• From Email Address

• Email Signature

• Header/Footer

Email Configuration

Keeps the Email setting for specific Emailing profile:

• sender

• Footer/Header (PDRPrintLyoutType)

• Signature

• etc

• Organisation Unit - reference to the department the Email Configuration is specified for.

Introduce new management area for "Email Configurations" under Administration/Emails

Usage

Email Configuration can be specified globally in the General Settigns, on the Email Descriptor level or in the Send Email UUX Workflow Activity

The extension author is able to upload screenshots and a one-pager pdf. In addition, he is able to set the categories for the extension in advance of the existing name and description option.

The author can use an "Integration from Marketplace" action to download Name; Description; Screenshots; One-Pager and Categories from Marketplace. The process fills out the form and this form can be adjusted from the customer.

During the publishing process, the publisher has the option to replace screenshots, One-Pager, and categories in advance to the existing field. Besides the author has the option to define screenshots and One-page via package.json

Before a release becomes publisher the publisher gets a visual preview of the advertisement page.

The Extension Gallery will render a new modal with advertisement information similar to the following idea:

<<TODO: Create Pic>>

(Title, Description; Screenshots; One-Pager; Version History with Release Date)

This now modal offers the option to start the installation process (executed as implemented today). When the user executes the Install button in the tile the process is the same as today!

More and more the Email Server vendors disable the legacy authentication mechanisms like Basic Auth. E.g. Microsoft Exchange Online can do it anytime:

https://docs.microsoft.com/en-us/lifecycle/announcements/exchange-online-basic-auth-deprecated

Once the Mail Server does not support the Basic Authentication it cannot be used.

To mitigate the risk to break the mail notifications and stop sending mails, introduce the alternative way to authenticate with Mail Server, using the Modern Authentication mechanisms. Modern authentication in Exchange Online enables authentication features like multi-factor authentication (MFA), smart cards, certificate-based authentication (CBA), and third-party SAML identity providers. Modern authentication is based on OAuth 2.0.

Use Service Connection to establish and maintain the connection to Mail Server

Service Connections must be free for Email sending configuration only! Means when there is no subscription, Workflow GDI can not use Service connections connectors

Introduce a multi-tenant audit service that can be used from every trusted application in the Matrix42 Cloud. A trusted application is reflected as on the oAuth2 client in the Access Control service. The DWP can establish a connection to the audit service via Service Connection and the simplified accounts integration. Multi-Tenant platforms like Extension Gallery, Matrix42 Cloud Accounts as self, Firescope or Fastviewer would request a global oAuth2 client from the Security & Compliance Manager.

AppFabric based service layer stopped being supported for all customers

By following the article, customers are able to uninstall the component and switch to supported technology ealier

https://help.matrix42.com/030_DWP/020_WFStudio/Workflows/Workflow_Engine/Deactivating_AppFabric_on_your_own_in_DWP_10.1.1_or_higher

The introduced advertisement page offers a star rating overview, allows to add ratings including a comment.

Requirements:

The Marketplace offers a feedback and star rating endpoint. The offered API allows to

• Send a comment and a rating

• Get all comments and ratings for a dedicated product

The Extension Gallery should offer feedback and rating for all products (independent if offered via marketplace or not)

• The Marketplace API is consumable via the existing federation between Marketplace and ExGA

Technical Hints:

• API specification

• A Screenshot rating system in Marketplace

Add possibility to add buttons to email descriptors that can act in similar way as link

It must be possible align it horizontally at canvas, and style due to customer indentity

The feature allows to extend the Solution Bulder Email Engine capabilites to design and render emails of any complexity which could follow the corporate identity.

Allow customers to design End User-friendly emails by styling the template

• add background colors for the template

• possibility define default apperance for all elelments used for formatting emails, like standart HTML tags (H1, H2, P, etc) as well as SoBu controls like Email Literal, Currency Literal ext

• possibility introduce new blocks which could be used for styling emails. E.g. block "Warning", which will be rendered as <div> with special styles.

• Style tables by coloring rows differently

All the email stylings are maintained in a new Configuration Item "Email Skin" which can be assigned to Email Descriptor either in dialog or directly in the Email Designer. On changing the Skin the styles defined in the Skin immeditely aapplied to the Email Designer WYSWYG designer. The custom blocks defined in the Skin extends the Email Designer Formetting blocks.

In runtime, on rendering Emails all the relevent styles from the related Skin are converted to the inline styles in the generated emails,

Customers expects that specific portals like the ACS admin port as self needs to authorize with a second factor. The second factor should not become implemented with its own technology, the ACS should enforce the external IDP to trigger an MFA flow. If MFA is not configured the system should interrupt the authentication flow.

Result of the Spike:

• oAuth Flow Version 2 supports MFA claim

Backlogs:

• Allow to filter out Myworkspace generate oAuth2/SAML2 Client (in ACS Admin Portal

• Support MFA requirement on oAuth2 Clients (configurable in ACS Admin Portal)

• Support MFA requirement on SAML2 Clients (configurable in ACS Admin Portal)

• Ensure the Azure AD IdP in ACS is announcing the MFA usage as session state

https://matrix42.aha.io/attachments/7077888439547899230/token/334332bd88c951d348e7f0b7fc18682ff2f1e20dad678366ea22f059bc665805?size=original

Change windows are created based on service time profiles and later assigned to assets and services as well as SKUs. In addition, change planning needs to be extended to include service time profiles as well to be able to identify the time zones. Once a change is planned and all assets and services are assigned the possible change window will be displayed in the planning view (recalculation is done on any change of asset/service assignments or time).

A warning message will be displayed In case the planned time doesn't fit the calculated change window. The feature extension will be made available using an extension in the Matrix42 Extension Gallery

Adapt/extend the current Outlook Plugin with new functionality comparing to MS Teams.

The Search Tickets action is a feature that allows searching through all types of tickets and obtaining search results in a matter of seconds. It does not influence overall performance of the system and ensures high performance that is independent from the data complexity.

You can run this action for the following objects: Ticket, Service Request, Problem, Task, Incident, and Change.

Additional Settings added to Email Robot:

• move ignored E-Mails (OOF & NDR) to specified folder

• marks moved ignored Mails as Read or Unread