Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision |
| 261:useprocessmodules [2026/03/13 16:58] – created - external edit 127.0.0.1 | 261:useprocessmodules [2026/04/27 12:04] (current) – [Integrate Process Modules] Geupel, Christian |
|---|
| ===== Integrate Process Modules ===== | ===== Integrate Process Modules ===== |
| |
| In order to integrate a process from one workspace to another, use the ''Add Module'' function. Refer [[:261:process_architecture|Integrate a Process]] section of Process Architecture on steps to integrate a process module. | In order to add a process from one workspace to another as a module, use the ''Add Module'' function. Refer [[:261:process_architecture|Integrate a Process]] section of Process Architecture on steps to integrate a process module. |
| |
| An important consideration when importing a module in a new workspace is the impact on process interfaces. | An important consideration when importing a module in a new workspace is the impact on process interfaces. |
| |
| All local associations are retained in the imported process but process interfaces with other worskpaces are retained only when, either the interfacing workspaces are within the same workspace group* or both the interfacing workspaces does not belong to a workspace group. | All local associations are retained in the integrated process but process interfaces with other workspaces are retained only when workspaces containing matching elements (either identical elements or elements matching by name and parent name) are in the same workspace collection(s). Multiple matches will lead to multiple interfaces. In addition to this, local associations will be created if matching target elements can be found locally - even for associations that were process interfaces in the module. Additional process interfaces will be created from originally local associations, if matching target elements can be found in the workspace collection. |
| | |
| //*Group is one of the properties that can be applied by admin at workspace level. When applied for a workspace, that workspace and any other workspace beneath it in the tree are considered as a 'group'. This helps to keep the associations created through process interfaces within the group only. If similar process elements exist outside the group, they are not linked through process interface with elements in the group. // | |
| ===== Update Process Modules ===== | ===== Update Process Modules ===== |
| |