Differences

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

--- 261:releasenotes [2026/04/07 13:31] – [How to Upgrade to Version 26.1] 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.
-===== Major changes =====
-=== Process interface handling ===
+===== Process interface handling =====
-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 not contained in any workspace collection, no process interfaces will be created.
+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 23: / Line 22: @@
 [[collectionMigration|See here for more info]] on how to transition to the new mechanisms.
-=== MCP Server available as beta version ===
-TBD
+===== MCP Server available as beta version =====
-Who to contact
+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.
+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 37: / Line 39: @@
 This improves the support for organizational mergers and large multi-domain organizations.
+=== Permission changes only take effect upon next login ===
+To speed up page access, user permissions are now cached. As a consequence, permission changes do not affect current user sessions anymore, so users need to log in again to see the effects.
 === Attribute handling ===
@@ Line 49: / Line 55: @@
 Config property "''operation.list.filter.types''" has been renamed to "''operation.list.exclude.types''".
-**//TBD: are there other changes in config.xml, etc.? Multiple SAML IdPs?//**
 Most configuration changes are now recognized automatically and do not require a service restart anymore. The only exception are license changes, which still require a restart.
-The ''database.properties'' file is not needed anymore for setting up the database connection. The database connection parameters are now configured in ''config.properties'' and ''secret.properties''.
+The ''database.properties'' file is not needed anymore for setting up database connections. The database connection parameters are now configured in ''config.properties'' and ''secret.properties''.
 === Java Update ===
 Java SDK has been upgraded to the latest LTS version 25.
 ===== Not yet supported features =====
@@ Line 97: / Line 102: @@
   * The "mandatory flag" for core process elements, which was only available through explicit configuration, has been removed.
-===== New and updated integrations =====
-**//tbd//**
-===== Not yet supported Integrations =====
+===== Not yet supported integrations =====
 Due to changes in PTC partner agreements, the integrations with Windchill RV&S (ex Integrity) and Codebeamer are not yet included in this release.
@@ Line 117: / Line 120: @@
 ===== Unified configuration metamodel changes* =====
-**//tbd//**
+=== New Element Subtype “Process Area” ===
-===== New reference models available =====
+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.
-In addition to new product features, we also made new reference models available to manage compliance.
+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.
+===== New reference models =====
+We also made new reference models available to manage compliance.
 Please reach out, if you are interested to use one or more of the following standards in Stages.
-**//TBD//**
+  * REGULATION (EU) 2024/2847, also known as EU Cybersecurity Resilience Act (CRA)
+  * ISO/IEC/IEEE 12207:2017 Systems and software engineering - Software life cycle processes
+  * Automotive SPICE for Cybersecurity 2.0
+  * EN 50155:2021 Railway applications. Rolling stock. Electronic equipment.
 [[https://www.ul.com/sis/stages/process-compliance-management|See here for the full list]] of available reference models.
 Please let us know if you have additional compliance requirements. Our teams are ready to implement them for you.
 ===== How to upgrade to version 26.1 =====
@@ Line 136: / Line 154: @@
 Please [[stages-support@ul.com|contact our customer care team]] to request an upgrade of your Stages Managed Service instance.
+//Note: all process release automations have to be finished before an upgrade can be performed.//