Workflow Node Coloring enhances the visual readability and traceability of workflows by introducing configurable color semantics for workflow actions. It allows both default color definitions at the action level and instance-specific coloring on the canvas, with automatic color propagation to all related output references.

Problem Statement

As workflows grow in size and complexity, it becomes increasingly difficult to understand:

• Where specific data originates from

• Which workflow action produced a given output

• How outputs are reused across different branches

Today, this often requires mouse-hover interactions or deep inspection of node configurations, which slows down reviews, troubleshooting, and collaboration.

Key Capabilities

1. Default Action Coloring

Administrators can define default visual properties for each Workflow Action:

• Default Shape Color

• Default Outline Color

These defaults apply automatically whenever the action is used in a workflow.

2. Instance-Level Node Coloring

Workflow designers can override default colors for individual workflow action instances directly on the canvas.

This enables:

• Visual grouping of related logic

• Highlighting of critical actions (e.g., AI decisions, approvals, external integrations)

• Faster orientation in large workflows

3. Output Color Propagation

For workflow actions with outputs:

• The selected node color is automatically applied to all output chips derived from that action

• Any reference to that output elsewhere in the workflow inherits the same color

This ensures consistent visual traceability across the entire workflow.

User Value

• Instant data lineage recognition

  Reviewers can immediately identify the origin of data purely by color—without mouse-hover or configuration inspection.

• Improved readability of complex workflows

  Large, branching workflows become easier to scan, understand, and maintain.

• Faster reviews and troubleshooting

  Reduces cognitive load for architects, reviewers, and operators.

• Better collaboration

  Shared visual language improves communication between workflow authors, reviewers, and auditors.

Typical Use Cases

• Highlighting AI-generated decisions and outputs

• Distinguishing automation logic by responsibility (IT, HR, Security)

• Marking external system interactions

• Visual separation of main flow vs. exception handling

This enhancement introduces System Workflows, along with dedicated UUX actions for cloning and activation, enabling safer lifecycle management of out-of-the-box (OOTB) workflows while significantly reducing operational friction for administrators.

The goal is to:

• Protect delivered standard content

• Enable controlled customization

• Simplify activation and deactivation of workflows

Problem Statement

Workflow Designer increasingly delivers complex, high-value OOTB workflows (e.g., AI Agents, compliance automations). Today, customers face several challenges:

• No clear distinction between system-delivered and customer-owned workflows

• Risk of accidental modification of standard workflows

• Unnecessary friction when activating or deactivating workflows (requires opening editor)

• No standardized mechanism to safely customize OOTB workflows

Key Capabilities

1. System Workflows (OOTB)

Workflows delivered out-of-the-box are now marked as System Workflows.

Characteristics:

• Delivered and maintained by the platform

• Read-only by default

• Fully versioned and upgradable

• Clearly identifiable in the UI

Edit Restrictions:

• System workflows cannot be edited

This ensures platform integrity while still enabling expert-level extensibility where required

2. Workflow Cloning (New UUX Action: “Clone”)

A new UUX action “Clone” is introduced for workflows.

Behavior:

• Creates a full, editable copy of the selected workflow

• Removes system restrictions on the cloned version

• Preserves structure, logic, and configuration

Typical usage:

• Customize OOTB workflows without breaking upgrade paths

• Use system workflows as best-practice templates

• Accelerate implementation of customer-specific variants

3. Workflow Activation / Deactivation (UUX Actions)

New UUX actions allow administrators to activate or deactivate workflows without opening the Workflow Designer.

New actions:

• Activate Workflow

• Deactivate Workflow

Benefits:

• Faster operational workflows

• Reduced risk of accidental edits

• Improved usability for admins and operators

This is particularly valuable for environments with frequent testing, rollout, or temporary suspension of automations.

User Value

• Safe standard content delivery

  Protects OOTB workflows from accidental modification.

• Clear ownership model

  Distinguishes platform-delivered logic from customer-owned customizations.

• Faster administration

  Activation and deactivation without editor access reduces time and errors.

• Upgrade-safe customization

  Cloning enables local adaptations while keeping system workflows intact.

• Enterprise governance readiness

  Aligns with compliance, audit, and controlled change-management requirements.

Typical Use Cases

• Adopting AI Agent workflows delivered by the platform

• Customizing compliance or security workflows safely

• Temporarily disabling automations during incidents or maintenance

• Partner-driven solution extensions using Developer Certificates

The Hierarchical Picker improves accuracy, usability, and scalability when configuring workflow conditions and parameters by introducing a tree-based selection UI for hierarchical data structures such as Categories, Locations, Cost Centers, and Organizational Units.

Instead of selecting from long, flat lists, users can now navigate and select values in their natural hierarchical context.

Problem Statement

In complex enterprise environments, key reference data (e.g., Categories, Org Units) is inherently hierarchical.

Previously, Workflow Designer exposed these values as plain, flat lists, leading to:

• Poor discoverability in large datasets

• Higher risk of selecting incorrect or similarly named values

• Reduced readability and maintainability of conditions

• Slower configuration of complex workflows

This was especially problematic in condition builders and decision logic.

Key Capabilities

1. Hierarchical Selection UI

For supported attributes, Workflow Designer now provides a hierarchical picker that reflects the actual data structure.

Users can:

• Expand and collapse hierarchy levels

• Clearly see parent–child relationships

• Select the correct node with full context

2. Supported Data Types

The hierarchical picker is applied consistently across Workflow Designer wherever applicable, including:

• Categories (e.g., Service / Incident / Request categories)

• Locations

• Cost Centers

• Organizational Units

This ensures a unified experience across conditions, actions, and parameters.

3. Improved Condition Builder Experience

Within the Condition Builder:

• Hierarchical values are displayed and selected in tree form

• Selected values are rendered clearly in conditions

• Logic remains unchanged, while usability is significantly improved

This is particularly valuable for complex IF / ELSE logic and compliance-driven workflows.

User Value

• Faster configuration

  Users find the correct value more quickly without scanning long lists.

• Reduced configuration errors

  Clear hierarchy prevents accidental selection of incorrect or similarly named entries.

• Better readability and maintainability

  Conditions reflect real-world structures, making workflows easier to review and audit.

• Enterprise-scale readiness

  Designed for large organizations with deep and complex hierarchies.

Typical Use Cases

• Routing tickets based on hierarchical service categories

• Applying rules to entire organizational branches

• Location-based workflow logic

• Cost-center–specific approvals or notifications

Workflow Designer now supports ID (GUID) output from Configurable AI actions.

When an AI action returns an identifier, this value is exposed as a dedicated output property Result ID, which can be reused in subsequent workflow steps to reliably establish relations or update records.

This closes an important gap when AI is used to identify, classify, or resolve entities rather than only returning descriptive text.

Problem Statement

Previously, Configurable AI actions were primarily used to return:

• Textual insights

• Recommendations

• Classification results

However, many real-world automation scenarios require AI to return a reference to an actual system entity (e.g., CI, Service, User, Asset). Without a stable identifier:

• Relations could not be set reliably

• Follow-up actions required manual mapping or workarounds

• End-to-end automation was limited

Key Capabilities

1. Result ID Output

Configurable AI actions can now return a GUID as part of their output.

• The GUID is exposed as a dedicated output property: Result ID

• The value represents a concrete object reference in the system

• Fully type-safe and reusable across workflow steps

2. Native Reuse in Follow-up Actions

The Result ID output can be directly consumed by subsequent actions, including but not limited to:

• Update Record

• Create / Update Relations

• Set reference properties

• Other workflow actions expecting an object identifier

This enables clean, deterministic automation chains driven by AI decisions.

3. Seamless Integration with Property Picker

The Result ID appears in the dynamic property picker alongside other workflow outputs, making it easy to:

• Select the AI-generated identifier

• Assign it to reference fields (e.g., Service, CI, User)

• Combine AI-driven discovery with standard workflow logic

No additional configuration or scripting is required.

User Value

• True AI-driven automation

  AI can now identify what to act on, not just what to say.

• Reliable data relationships

  Eliminates ambiguity by using system identifiers instead of text matching.

• Simpler workflow design

  Reduces complexity and removes the need for custom glue logic.

• Broader AI use cases

  Enables scenarios like AI-based CI detection, service resolution, or entity matching.

Typical Use Cases

• AI identifies the most relevant Service or CI and links it to an Incident

• AI resolves a target object and updates relationships automatically

• AI-driven classification followed by structured record updates

• End-to-end AI Agents that both analyze and act

Maybe introduce new Data Set View, so we can still support new and old style.

Apply item template style for new Data Set View

Set it default for Catalog (customers can set manually old one in case of customizations made and so on)

Configuration:

introduce setting for Application in advanced (radio):

1. Show Wizard as Popup

2. Side Panel (default)

Set "Show Wizard as Popup" as default for Self Service

Runtime:

when activated, all wizard in the application will be opened as Popup

The Reporting Toolkit now supports an enhanced TV Mode, allowing reports and dashboards to be displayed sequentially on large screens with manual navigation or automatic rotation—ideal for team rooms, NOCs, and management displays.

What’s New

Manual Navigation

• Navigate Back and Next across all available reports

• Enables on-demand switching during meetings, reviews, or discussions

• Full-screen, distraction-free presentation mode

Automatic Report Rotation

• Enable Auto Switch to cycle through reports automatically

• Combine with Auto Refresh to keep data continuously up to date

• Ensures dashboards stay current without manual interaction

Customer Value

• Perfect for wallboards and TVs: Always-on visibility of key KPIs

• Hands-free operation: Ideal for service desks, operations centers, and offices

• Live insights: Automatically refreshed and rotated reporting views

• Flexible usage: Manual control when needed, automation when unattended

Typical Use Cases

• Service Desk or NOC wallboards

• Management KPI screens

• Daily operational stand-ups

• Executive or team overview displays

The Reporting Toolkit now provides a configuration toggle to prevent drilldown for Metric Cards. This allows dashboard designers to explicitly control whether a metric card is interactive or display-only, ensuring dashboards behave as intended for different audiences and use cases.

Problem Statement

Metric Cards are often used to present high-level KPIs or status indicators. In many scenarios, drilldown is either:

• Not relevant

• Not permitted due to governance or data-scope restrictions

• Confusing for business or executive users

Previously, metric cards always supported drilldown behavior, which could lead to:

• Accidental navigation

• Exposure of unnecessary or sensitive detail

• Inconsistent dashboard behavior

Key Capabilities

1. Drilldown Control Toggle

A new “Prevent Drilldown” toggle is available in the Metric Card configuration panel.

When enabled:

• Clicking the metric card does not trigger drilldown

• The card behaves as a pure informational KPI

• The visual appearance remains unchanged

2. Per-Widget Configuration

Drilldown behavior can be controlled individually per Metric Card.

This allows dashboard designers to:

• Mix interactive and non-interactive metrics on the same dashboard

• Align behavior with the purpose of each KPI

• Tailor dashboards for different roles and audiences

3. Improved Governance and UX Consistency

By explicitly disabling drilldown where appropriate:

• Dashboards become more predictable

• User experience is aligned with expectations

• Data access is better controlled

User Value

• Clear intent for KPIs

  Distinguishes between navigational metrics and executive indicators.

• Reduced accidental navigation

  Prevents users from unintentionally leaving the dashboard.

• Better dashboard design control

  Designers decide where exploration is allowed and where it is not.

• Governance-ready dashboards

  Supports role-based data exposure and compliance requirements.

Typical Use Cases

• Executive dashboards with read-only KPIs

• Wallboards and NOC displays

• Status summaries where drilldown is irrelevant

• Metrics based on aggregated or restricted data

Show top 3 actions, and hide rest to "more" menu

Starting with the 26.1 release (April 2026), legacy Microsoft SQL Server Reporting Services (SSRS) and SQL Server Analysis Services (SSAS) integrations will be fully discontinued. This step completes the modernization initiative.

What’s changing

Legacy SSRS reports will no longer be delivered with the product installer.

SSRS/SSAS components will no longer be configured or deployed via the Setup Wizard.

That also means that during New Installation in Cloud or OnPrem Matrix42 tools will not deploy SSRS/SSAS anymore.

For Updates, no SSRS/SSAS related configurations will be changed.

Those customers who have SSRS/SSAS already configured - can continue using and maintaining them at their own risk.

All default legacy reports entries will be removed from the user interface, ensuring a clean transition to the new Reporting Toolkit.

What's kept

SSRS Report Viewer is not yet removed from the product interface. You can still show reports from SSRS/SSAS hosted by your own.

We don't remove any reports that were already deployed to SSRS.

No custom report entries are removed from User Interface during update.

All custom SSRS/SSAS reports will continue working after update to 26.1 release (April 2026)

Report to File extension

Customers who use Report2File addon that sends SSRS based reports as PDF via Workflow Studio, will be provided with alternative technology called “Document Templates” with 26.1 release. This tool is a native tool owned by Matrix42 and has a similar look to Email Designer. It supports API and Workflow Studio/Workflow Designer integration.

What this means for you

Full removal of SSRS/SAAS integration capabilities for existing customers is planned with 26.2 (October 2026), and all migration from SSRS custom reports should be finished prior to this.

Customers are encouraged to migrate to the modern Reporting Toolkit and Document Designer (in case of Report2File use), which provides a unified, future-proof reporting experience prio 26.2 (October 2026).

Any custom SSRS reports and Workflows that use Report2File addon should be re-implemented.

The Reporting Toolkit now allows charts to be sorted by values, not only alphabetically, making visualizations clearer, more meaningful, and easier to interpret at a glance.

What’s New

Flexible Sorting Options

• Charts can now be sorted by:

  • Label (alphabetical)

  • Value (numeric)

  • Associated column (data-driven sorting)

• Sorting direction can be configured as ascending or descending

Clear Configuration

• Sorting behavior is explicitly configurable per widget

• Required sorting fields are clearly indicated, preventing misconfiguration

Customer Value

• Improved readability: Largest or most critical values are immediately visible

• Better insights: Trends, outliers, and priorities stand out naturally

• Professional dashboards: Charts follow common analytics and BI expectations

• Less cognitive load: Users no longer need to mentally reorder data

Typical Use Cases

• Ranking categories by ticket volume or incident count

• Showing top applications, services, or users by usage

• Highlighting highest-impact issues or bottlenecks

• Management dashboards focused on priorities rather than alphabetical order

The Reporting Toolkit now supports shared edit permissions, enabling teams to collaboratively edit and manage reports and dashboards while maintaining clear access control.

What’s New

Collaborative Editing

• A report or dashboard owner can grant edit permissions to selected user groups or roles

• Multiple users can collaboratively adjust widgets, layouts, and configuration without duplicating dashboards

Flexible Sharing Options

• Share reports with all users or with specific groups or roles

• Define allowed editors who can modify the report configuration

• Optionally propagate edit permissions to widgets included in the report

Clear Role Separation

• View-only users can still access shared dashboards without the ability to modify them

• Edit permissions are explicitly defined and visible, reducing accidental changes

Customer Value

• Improved collaboration: Teams can jointly maintain dashboards without workarounds

• Less duplication: Avoid creating multiple copies of the same dashboard for different owners

• Better governance: Controlled editing rights ensure consistency and accountability

• Faster iteration: Changes can be made by the right people without bottlenecks

Typical Use Cases

• Shared operational dashboards maintained by multiple service desk leads

• Management dashboards jointly owned by IT and business stakeholders

• Cross-team reporting where responsibilities are distributed

• Long-lived dashboards that evolve over time

The Reporting Toolkit now supports Quick Links and Quick Link panels that open edit dialogs directly, allowing users to jump straight from a dashboard to configuration or settings screens without manual navigation.

What’s New

Open Edit Dialog from a Widget

• Quick Links can be configured to open an edit dialog directly instead of navigating to a list or page

• Ideal for frequently used configuration or administration actions

Optional Static Object Selection

• When configuring a Quick Link, an optional static object can be selected

• If an object is defined, the system opens the Edit Dialog for that specific object

• If no object is defined, the dialog opens in a generic or selection mode (default behavior)

Quick Link Panels

• Multiple Quick Links can be grouped into a Quick Link panel

• Enables dashboards to act as a launchpad for common actions and settings

Customer Value

• Faster access to configuration: Reduce clicks and navigation steps

• Action-oriented dashboards: Move from insight to action immediately

• Higher productivity: Especially valuable for admins, service desk leads, and power users

• Flexible setup: Works with both predefined objects and generic dialogs

Typical Use Cases

• Open global or service-specific settings directly from a dashboard

• Quick access to SLA, OLA, or system configuration dialogs

• Admin dashboards with shortcuts to high-impact configuration areas

• Operational dashboards that combine KPIs with direct actions

The Reporting Toolkit now allows users to hide or show the welcome text on a per-report basis, enabling a cleaner and more focused dashboard experience when explanatory text is no longer required.

What’s New

Hide Welcome Text

• Users can hide the welcome or introductory text for a report or dashboard

• Creates a more compact, data-first layout, especially for operational or frequently used reports

Restore at Any Time

• The welcome text can be shown again at any time

• Ensures guidance and context are still available when needed (e.g. for new users or shared reports)

Customer Value

• Cleaner dashboards: More space for KPIs and visualizations

• Better usability: Reduce visual noise once a report is well understood

• Flexible communication: Keep explanatory text for onboarding, hide it for daily operations

• Consistent experience: Works seamlessly across predefined and shared reports

Typical Use Cases

• Operational dashboards used daily by service teams

• Management reports where context is already known

• Shared dashboards where layout clarity is critical

• Gradual onboarding: show guidance first, hide it later

To ensure continuity and transparency as part of our reporting evolution, we are introducing a limited, read-only version of Reporting Toolkit that remains available without a Reporting subscription.

What Customers Get (Without Subscription)

Customers without a Reporting subscription will retain visibility into existing reports and dashboards:

• View existing reports and dashboards in read-only mode

• Analyze data using interactive drill-down (where configured)

• Use reports for operational monitoring, audits, and reviews

• Maintain access to reporting insights they already rely on

This ensures customers do not lose access to reporting data they had before, even as the reporting model evolves.

What Is Limited in the Free Version

The following capabilities require a Reporting subscription and are not available in the limited version:

• Creating or editing reports and dashboards

• Adding charts or KPIs from data grids

• Modifying layouts, filters, or visualizations

• Saving new dashboards or report variants

• Advanced analytics and customization features

Full Reporting Capabilities (With Subscription)

A Reporting subscription unlocks the complete Reporting Toolkit, including:

• Full report and dashboard creation

• Custom charts, KPIs, and visualizations

• Advanced filtering, drill-through, and analytics

• Dashboard composition and personalization

• Ongoing enhancements and innovations

Customer Value

• No loss of visibility: Customers keep access to critical reporting insights

• Clear separation of value: Read-only access vs. full analytics capabilities

• Smooth transition: Existing reporting usage remains supported

• Predictable upgrade path: Advanced reporting available when needed

The Reporting Toolkit introduces clearer and more transparent handling of applied and required filters, making reports easier to understand, validate, and use correctly—especially in read-only scenarios.

What’s New

Required Filters Guidance

• Reports that depend on mandatory parameters (for example, Service ID or date range) no longer render incomplete or misleading data

• If required filters are missing, users see an empty state with a clear explanation of:

  • Which filters are required

  • Why the report cannot be generated yet

  • Where to set the missing parameters

Applied Filters Visibility

• All currently applied filters are now clearly displayed at the top of the report or dashboard

• Users can instantly understand which data scope the report is based on

• Improves trust, readability, and explainability of reports during reviews and audits

Customer Value

• No ambiguity: Users always know which filters are active

• Correct insights: Reports are only generated when mandatory context is provided

• Better usability: Especially important for shared, read-only, or management-level reports

• Reduced support questions: Clear guidance replaces “empty or broken” looking reports

Works Especially Well With

• Read-only reporting access

• Predefined dashboards shared across teams

• Management, audit, and compliance reporting

• Self-service analytics for non-technical users

The Reporting Toolkit now allows users to define a dedicated sorting criterion independently from the grouping logic, ensuring charts and dashboards are displayed in a logical, meaningful order.

What’s New

Independent Sorting Configuration

• In addition to selecting a grouping column, users can now specify a separate column for sorting

• Sorting can be based on:

  • A numeric value (e.g. duration, priority order)

  • An associated data column from the dataset

• Sorting direction can be defined as ascending or descending

Logical Ordering for Visualizations

• Charts (e.g. pie charts, bar charts) are no longer forced to follow automatic or alphabetical ordering

• Enables business-logical sequences instead of technical ordering

Why This Matters

Previously, grouping and sorting were tightly coupled:

• When grouping by calculated or derived values (e.g. ticket runtime buckets like 0–4h, 4–24h, 24–48h), charts were sorted automatically and often appeared arbitrary

• Users had to rely on naming workarounds (e.g. prefixes like “1–”, “2–”) to enforce order

With this enhancement:

• Grouping defines what is aggregated

• Sorting defines how results are ordered

Customer Value

• Clearer visual logic: Charts follow natural business progression

• Better readability: Especially for time buckets, SLA ranges, maturity levels, or priority scales

• No workarounds needed: Eliminates artificial naming conventions

• More professional dashboards: Matches expectations from modern BI tools

Typical Use Cases

• Ticket runtime or SLA duration buckets

• Priority or escalation levels with defined order

• Maturity stages or lifecycle phases

• Any grouped data where semantic order matters

Functional Worker fully replaces the Worker, including the case of remote (neither App Server nor Prod cluster) when the Functional Worker fulfill the role of the Data Gateway.

To simplify the migration the way Worker Host stays as it is, and support still fulfill the following functions:

• The installation can be downloaded and installed

• token can be updated

• Restart Function

• Registering in Workers and show the actual status

• Self-update

But the Worker Application are removed and the only application managed by Worker stays the Functional Worker Dispatcher which is started/stopped by Worker Host

Worker Capabilities

Each running Functional Worker Dispatcher contributes to the Worker cluster set of capabilities, which determines set of tasks capable been executed on the Worker. Some capabilities are detected and assigned automatically, whereas others can be assigned manually.
Example: "windows", "linux", "trusted" can be detected and assgined automatically on start.

Customer can create his own capabilities and assigne then Worker
Example: "Imagoverum VPN", "Empirum SDK" which shows the Worker running in DMZ, or Empirum SDK installed on the machine running the worker
Data Provide Pool is converted to "Worker Capability"

Configuring Navigation type

introduce setting on Application level to chose Navigation Type: Standard and Simple
we already have hidden configuration for it in application dialog - just restore it, and remove unnessary checkboxes. Dont introduced new field in db... als seems to be ready from front end side

When Navigation is of type Simple, show in the top of screen.

• in this mode, Filters are not shown in navgation (like Service Catagories) - navigation shows just navigation

However, when Simple Navigation of app is in use, Filter Panel with Categories for Catalog must be shown next to items (same for KBs)

Starting with the 26.1 release (April 2026), the Classic Look will be fully removed and no longer supported.

This step completes the major user interface modernization initiative that started several releases ago.

What’s changing

• The Classic Look will be automatically deactivated for all users.

• The switch to the New Look will happen automatically — no administrative action is required.

• All related configuration options and interface components for Classic Look will be removed from the product.

Why this change

Based on great customer feedback, the New Look has proven to deliver higher quality, improved performance, accessibility, and a modern experience with exclusive new features such as accessibility enhancements, personalization options, and AI-assisted workflows.

This change ensures a consistent and future-ready experience for all users.

Learn more:

Read about the advantages and unique features of the New Look in our article:

👉 Benefits of the New Look

This feature enables users to convert a Teams message into an actionable item inside the ESM system. Agents and employees can create new Incidents or Tasks from Teams messages or add comments to existing tickets — ensuring that important information is not lost in conversation threads.

Key outcomes:

• Rapid ticket creation based on real user conversations

• Accurate transfer of message context into structured ESM records

• Better capture of operational data from collaboration channels

Supported actions:

• Create Incident from a Teams message

• Create Task from a message

• Add a comment to an existing Incident

• Enrich tickets with message text and metadata

Introduce Persononization Menu in User Profile

M42 Assistant become part of ESM Platform Core

In the first iteration it integrates AI actions, that will show result of execution, and user will be able to Appy or Deny proposals

In second - Live chat will be integrated to Service DEsk

In next update CAI will be integrated to it too

User may chose between 2 options on how to show assistant: Side Panel (default), Float Over

--that the sync should be not only onetime

Sync of Services Intune <-> Service Catalog (Sync Version: (https://ideas.matrix42.com/ideas/SAM-I-274)

-> Developer & Owner is complete not imported / snycd (https://ideas.matrix42.com/ideas/SM-I-628)

-> Allow to select multiple groups for install and uninstalll (https://matrix42.aha.io/ideas/ideas/SWM-I-75)

Customer description: When provisioning the software service request for an Intune managed software the M42 provisioning should support adding or removing users/computers to/from multiple Entra ID groups and not only the "install" and "uninstall" group. There are software products which exclude each other. For example Acrobat Reader and Acrobat Professional. Only one can be installed on a given computer at the same time. So, it would be great if the provisioning workflow of M42 could add a user to for example the install group of Acrobat Professional AND the uninstall group of Acrobat Reader when a user orders the Acrobat Professional service in the M42 service catalog.

-- customer Magna need a function for filtering (that not all packages getting imported)

for example: only import Packages that the name contains / or the name not contains: AutoPilot (as example)

Starting with v26.1, Global Search supports deep linking via URL parameters, allowing users to open the application with a predefined global search query and optional scope—enabling direct navigation to relevant results from external links, bookmarks, notifications, or integrations.

What’s New

Deep Linking via URL

• Global Search can now be triggered directly through a URL parameter

• The search field is automatically prefilled and executed on page load

Configurable Search Scope

• Deep links can optionally restrict the search to specific Configuration Item (CI) types

• Only CI types enabled for Global Search (via Global Search Context) can be used

• If no types are specified, the search runs across the default search scope

Supported Parameters

globalSearch (JSON object):

• keyword

  • The search term to execute

  • Must contain at least two characters

• types (optional)

  • Comma-separated list of internal CI type names

  • Limits the search to selected object types

URL Pattern

<HOST>/wm/app-<AppName>/<LayoutType>/<LayoutID>?globalSearch=<GlobalSearchOptions>

Example

The following link:

• Opens the Self Service Portal landing page

• Prefills the global search with the keyword “print”

• Searches only within Knowledge Base Articles

https://wmpreview03.imagoverum.com/wm/app-SelfServicePortal/landing-page/14587d3e-63aa-e611-d99b-bc5ff41a70c0
?globalSearch={"keyword":"print","types":"SVMKBArticleType"}

Customer Value

• Faster access to information: Jump directly to relevant search results

• Better integrations: Use deep links from emails, tickets, portals, or external tools

• Improved self-service: Guide users straight to KB articles or specific object types

• Consistent experience: Uses the same Global Search logic and permissions

Typical Use Cases

• Links from notifications, announcements, or knowledge campaigns

• Self-service portals with preconfigured search shortcuts

• External systems linking into Matrix42 with contextual searches

• Bookmarks for frequently used search queries

https://docs.matrix42.com/1067925_esmp-integration/3463386_deep-linking?from_search=216532419#global-search-6

Administrators can now control the search engine per application, allowing AI Search to be enabled or disabled selectively—while still supporting a global default configuration.

What’s New

Per-Application Search Engine Setting

• Each application now includes a Search Engine setting in

  Administration → UI → Application

• Available options:

  • Use Global Settings configuration

  • Standard

  • AI

Optional Override with Clear Priority

• The application-level setting is optional

• When defined, it overrides the Global Search Engine setting

• If not defined, the application inherits the global configuration

Consistent Visibility Rules

• The application-level Search Engine option is shown only when:

  • The global Administration → Settings → Search Engine configuration is available

• Ensures a consistent and controlled admin experience

How It Works (Examples)

• Global AI, selective Standard

  • Admin enables AI Search globally

  • Sets Standard Search for a specific app (e.g. Assets)

• Global Standard, selective AI

  • Admin disables AI Search globally

  • Enables AI Search only for selected apps (e.g. Self Service Portal)

Customer Value

• Flexible rollout of AI Search: Enable where it adds value, disable where not needed

• Better user experience: Tailor search behavior to application context

• Controlled adoption: Gradually introduce AI Search without global impact

• Clear governance: Explicit precedence avoids ambiguity

Typical Use Cases

• AI Search enabled only in Self Service Portal for end users

• Standard Search retained in admin-heavy or data-sensitive applications

• Phased AI adoption across different business areas

• Application-specific compliance or performance considerations
  
  

Improve the Configuration Project automatic detecting and recording relevant changes mechanism to cover any possible modification in Objects which affects the System Configurations. It presumes not only creation of a new Object but also further updates. All changes are recorded to the active Project and could be later manually edited, or if the recorder is disactivated, then all changes can be from scratch added to Configuration Project

Automatic Changes Recording

The following objects need to be tracked (creation and update):

• Navigation

• Actions

• Control Descriptors

• Compliance Rules

• Data Queries

• Search Filter

• Structure

• Web Service , Web Service Operation (ONLY from None-Product DLLs)

• 
  

• Engines

• Engine Activation

• Data Gateway

• Workflow Activity

• Workflow Category

• Workflow Configuration

• Themes

• Localisation Strings

• Assembly

Warning: Not tracked objects

• - Connector

• - Workflow Instances

• - Workers

• - Emails

• - Global System Settings

• - Action Groups

• - Service Interfaces

• - Web Service Token

• Email Signatures

• Data Providers

• User Roles

• GDIs

Introduce a dedicated container in the Kubernetes cluster that hosts an S3-compatible storage service. The product adds a new File Storage Provider (“S3”), which becomes the default provider after cluster installation. Installed extension artifacts are stored in the S3-compatible storage.

ESM_Setup container whch handles in jobs all maintenace operations for Container installation, running in Linux container

Disable Change Request Lists and Annoucnment lists navigation items for new installation only in Self Serice Portal

When using the new dashboards and interactive filters, the filter is removed when you change pages.

It would be good if it were possible to save or “fix” the interactive filters in the new dashboards until you change or reset them again.

Enable agents to confirm, and directly apply AI-generated recommendations from the Assistant when executing AI Actions

Behavior

• AI suggestions appear in an Assistant after AI action executed

• Agent can:

  • Accept suggestion (auto-update ticket fields)

  • Review details before applying

  • Ignore or modify suggestion

Value

• Faster ticket classification

• Improved data quality (Impact/Urgency/Category consistency)

• Reduced manual effort

• Increased agent productivity

• Foundation for AI-assisted triage