Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
75:useprocessmodules [2020/12/07 18:05] – aibn75: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 [[:73:process_architecture|process architecture]]. A process module will contain generic process(es) to be inherited into an integrated standard process or even into an instance of a program or project. 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 [[:73:process_architecture|process architecture]]. A process module will contain generic process(es) to be inherited into an integrated standard process or even into an instance of a program or project.
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=b4fbf2&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/processarchitecture_module.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/processarchitecture_module.png?direct&900x306}}]]+{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/processarchitecture4.png?nolink&900x215}}
  
-In above example, each of the process workspace in bottom three layer of the process architecture will have to be set as a ''process module'' in order for it to be integrated into the workspace above.+In above example, each of the process workspace in bottom two layers of the process architecture will have to be set as a ''process module'' in order for it to be integrated into the workspace above.
 ===== Specify Workspace as Process Module ===== ===== Specify Workspace as Process Module =====
  
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 workspace does not have grouping set.+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 '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. // //*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. //