Differences

This shows you the differences between two versions of the page.

--- 261:releasenotes [2026/04/10 18:29] – [MCP Server available as beta version] Meier, Erich
+++ 261:releasenotes [2026/04/16 11:41] (current) – [MCP Server available as beta version] Iseler, Marc
@@ Line 7: / Line 7: @@
 The main feature of Stages 26.1 is its completely new backend platform. End users should not notice any differences, but modelers will benefit from its improved handling of process interfaces and faster data transfers, e.g. during process module updates. Also, the new technology platform allows us to release future product innovations quicker and perform upgrades easier than before.
-We also announce the availability of the Stages MCP Server as part of a beta program. This MCP Server allows you to include process data managed in Stages to be used in other AI systems like chatbots, AI search, and other AI-based applications.
+We also announce the availability of the Stages MCP Server as part of a beta program. This MCP Server allows you to include process data managed in Stages to be used in other AI systems like company chatbots, AI search, and other AI-based applications.
 Release 26.1 is currently **only available for Stages Managed Service instances**. On-premise usage will be made available later this year.
 ===== Process interface handling =====
@@ Line 15: / Line 16: @@
 When process modules are integrated into other workspaces or whole processes or single elements are copied into new workspaces, the creation of process interfaces is now solely controlled through workspace collections. Only processes in any workspace collection of the current workspace are being searched for potential process interface target elements. If a target is found in multiple workspaces, multiple interfaces are being created. If a workspace is updated that is not contained in any workspace collection, no process interfaces will be created.
-The handling of process interfaces via workspace groups and common element workspaces has been removed.
+The ''group'' and ''common elements'' workspace settings do not have any influence on the process interface creation anymore.
 As a result, process interface creation should be much more consistent, transparent, and easier to control.
@@ Line 21: / Line 22: @@
 [[collectionMigration|See here for more info]] on how to transition to the new mechanisms.
-===== MCP Server available as beta version =====
-MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources.
+===== MCP Server available as beta version =====
-Through our new MCP Server, AI systems can access process data managed in Stages for various purposes and use cases.
+MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources. It's a common way to integrate Stages into your **enterprise chatbots**, so that your development processes are taken into consideration in those systems.
-**//TBD//**
+Through our new MCP Server, AI systems can access process data managed in Stages for various purposes and use cases. You can therefore adjust the MCP configuration to control the amount of information revealed via the MCP interface.
 [[mcpServer|See here for more info]] on MCP with Stages.
@@ Line 120: / Line 120: @@
 ===== Unified configuration metamodel changes* =====
-**New Element Subtype “Process Area”**
+=== New Element Subtype “Process Area” ===
 The new //Process Area// element subtype provides an additional way to structure workflows. Similar to the existing //Topic// element, multiple workflows can be grouped into a single unit.
 Unlike //Topic//, a //Process Area// contains automatic visualization of the workflows it contains, improving transparency and overview for complex process landscapes.
+=== Announcing our Future Standard Metamodel Strategy ===
+With this release, we share adjustments to our standard metamodel strategy. We strive to support new modeling requirements more quickly while minimizing the number of delivered standard metamodel variants.
+[[261:metamodelStrategy|Read here for details]] of the new strategy.