Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
75:useprocessmodules [2020/12/01 08:11] – aakr | 75:useprocessmodules [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
In Stages, a process modeled in a workspace of the type process module can be inherited into other workspaces. The content of a process module is dictated by the [[: | In Stages, a process modeled in a workspace of the type process module can be inherited into other workspaces. The content of a process module is dictated by the [[: | ||
- | [[https:// | + | {{https:// |
- | In above example, each of the process workspace in bottom | + | In above example, each of the process workspace in bottom |
===== Specify Workspace as Process Module ===== | ===== Specify Workspace as Process Module ===== | ||
Line 16: | Line 16: | ||
In order to integrate a process from one workspace to another, use the '' | In order to integrate a process from one workspace to another, use the '' | ||
+ | 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. | ||
+ | |||
+ | //*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 ' | ||
===== Update Process Modules ===== | ===== Update Process Modules ===== | ||