Stages Documentation

Differences

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

Link to this comparison view

Next revision		Previous revision
261:options [2026/03/13 16:58] – created - external edit 127.0.0.1261:options [2026/04/27 09:25] (current) – [Copy] Geupel, Christian
Line 17: Line 17:
 Note that when a folder containing a set of roles, work products, or guidance is copied, the contents within the folder are also copied. Note that when a folder containing a set of roles, work products, or guidance is copied, the contents within the folder are also copied.
  
-When elements are copied or moved, there are additional considerations that should be kept in mind before taking such an action. //In the case of copying a workflow/activity, if the associated process elements like roles, work products, and guidance from the same workspace are not manually copied to the target workspace, then those associations are not copied by default.// //However, process interfaces to elements in other workspaces are retained and will continue to be associated in the same way as they did in the source workspace.// +When elements are copied, there are additional considerations that should be kept in mind before taking such an action with regard to associations: //For example a workflow/activity has associations with roles, work products, and guidance.// The copy will only get the same associations if its workspace is in a collection that contains identical target elements or elements with matching types, names and parent element names. Multiple matches will lead to multiple associations. The previous target elements are not copied implicitly to the new location.
- +
-If the associated elements from the same source workspace should also appear in the target workspace, then they should also be copied from the source to the target workspace. When copied, the associations will be automatically re-created and will be the same as they were in the source workspace. +
- +
-This is true not only for workflow and activities but also for other process elements. If a role/work product/guidance is copied over from one workspace to another, then any associations it had to elements from the source workspace will no longer appear in the target workspace. However, process interfaces with elements from different workspaces will.+
  
 ===== Copy Associations ===== ===== Copy Associations =====
Line 33: Line 29:
 The steps to move any process elements are the same as described for Copy. Instead of 'Copy', tap or click on 'Move' and paste the option at the destination. Just like with 'Copy', single or multiple elements can be moved within or outside the workspace. The steps to move any process elements are the same as described for Copy. Instead of 'Copy', tap or click on 'Move' and paste the option at the destination. Just like with 'Copy', single or multiple elements can be moved within or outside the workspace.
  
-//Similar to the copy function, on moving a process element the associated elements like roles or work products from the same workspace are not moved to the target location. However, unlike copy, the process element will continue to be associated with other process elements like roles, guidance, or work products through process interfaces, along with any other process interface that was present in the source workspace. //+//The associated elements like roles or work products from the same workspace are not moved implicitly to the target location. However, unlike copy, the process element will continue to be associated with all other process elements like roles, guidance, or work products through process interfaces, along with any other process interface that was present in the source workspace. Workspace collection memberships are not considered and necessary for this use case. //
  
 If the associated process elements should continue to be locally associated and not through process interfaces at the target location, then those elements should also be moved to the target location. If the associated process elements should continue to be locally associated and not through process interfaces at the target location, then those elements should also be moved to the target location.