Differences
This shows you the differences between two versions of the page.
| 262:workspace_collections [2026/09/28 19:26] – created - external edit 127.0.0.1 | 262:workspace_collections [2026/11/19 12:40] (current) – Goetz, Sebastian | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| To manage complex process landscapes with many process owners, the processes should be modeled in separate process modules and then integrated into larger entities. Those process modules should have defined interfaces, e.g. via work products or roles. | To manage complex process landscapes with many process owners, the processes should be modeled in separate process modules and then integrated into larger entities. Those process modules should have defined interfaces, e.g. via work products or roles. | ||
| - | Workspace collections support this effort by automatically proposing interfaces from other process modules. Similar to elements in the same workspace, elements from all workspaces | + | A **workspace collection** groups workspaces that belong together, e.g. all process modules |
| - | [[https:// | + | * [[# |
| + | * [[# | ||
| + | * [[# | ||
| + | * [[# | ||
| + | * [[# | ||
| - | It is then possible to create an interface with a single click. | + | ===== Set up workspace collections ===== |
| Workspace collections can be set up by the administrator via '' | Workspace collections can be set up by the administrator via '' | ||
| Line 13: | Line 17: | ||
| [[https:// | [[https:// | ||
| - | If a workspace is part of multiple collections, | + | A workspace can be part of multiple collections. |
| + | |||
| + | ===== Association candidates ===== | ||
| + | |||
| + | Workspace collections support modeling by automatically proposing interfaces from other process modules. Similar to elements in the same workspace, elements from all workspaces in the collection are shown in the association dialog. | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | It is then possible to create an interface with a single click. | ||
| + | |||
| + | If a workspace is part of multiple collections, | ||
| + | |||
| + | ===== Impact on process interfaces ===== | ||
| + | |||
| + | When processes are imported, process modules are updated or processes are copied into a workspace, Stages automatically creates process interfaces. Interface targets are searched in **all workspaces of all collections** the current workspace belongs to. If a workspace is not part of any collection, no process interfaces are created. | ||
| + | |||
| + | Since Stages 26.1, workspace collections replace the former workspace settings **Group** and **Common Elements**. See [[262: | ||
| ===== Impact on Search ===== | ===== Impact on Search ===== | ||
| Line 21: | Line 41: | ||
| This can be used to optimize the experience for new users, by defining a collection with all workspaces that contain content for first-time users and adding the root workspace (or all other default user workspaces) to them. | This can be used to optimize the experience for new users, by defining a collection with all workspaces that contain content for first-time users and adding the root workspace (or all other default user workspaces) to them. | ||
| + | ===== Training scope of the Stages Assistant ===== | ||
| + | |||
| + | The [[262: | ||
| + | |||
| + | Use a workspace collection as training scope if the relevant process content is spread across several workspaces, e.g. the standard development process plus organizational processes. The Assistant is then trained on the valid versions of **all workspaces in the collection**. | ||
| + | |||
| + | Please note: | ||
| + | * Users need read permissions for **all workspaces in the collection** to use the view. | ||
| + | * Process interfaces to elements **outside** of the collection are ignored during training. Make sure the collection contains all workspaces needed to answer the expected questions. | ||
| + | * For collections, | ||
| + | |||
| + | See [[262: | ||
| + | |||
| + | ===== Scope for the MCP interface ===== | ||
| + | |||
| + | The [[262: | ||
| + | |||
| + | For this toolset, the collection must contain all workspaces whose process content the agents should follow, and the use-case model must be defined within the collection. See [[262: | ||
| + | |||
| + | Please note: | ||
| + | * Access through MCP is always governed by the permissions of the authenticated user, including the " | ||
| + | * The **Chatbot Process Data** toolset (scope '' | ||
| + | |||
| + | See [[262: | ||