Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
75:useprocessmodules [2020/12/07 18:05] – aibn | 75:useprocessmodules [2021/12/30 19:05] – aakr | ||
---|---|---|---|
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 three layer of the process architecture will have to be set as a '' | In above example, each of the process workspace in bottom three layer of the process architecture will have to be set as a '' | ||
Line 18: | Line 18: | ||
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 group* or when both the interfacing | + | 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 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 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 ' |