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
710:lost_found [2024/07/30 15:02] – Lachner, Ingo710:lost_found [2024/07/31 07:19] (current) – [How to handle elements in LOST+FOUND] Lachner, Ingo
Line 3: Line 3:
 **Root cause for LOST+FOUND **  **Root cause for LOST+FOUND ** 
  
-If an element is removed, but other objects—such as elements, files, or user assignments—depend on that element and Stages did not receive an explicit order to delete them, those dependent objects are moved to LOST+FOUND to prevent them from being deleted.+If an process element is removed, but other objects—such as process elements, files, or user assignments—depend on that element and Stages did not receive an explicit order to delete them, those dependent objects are moved to LOST+FOUND to prevent them from being deleted. 
 + 
 +We recommend that you contact your Method Park by UL Solutions consultant to analyse the root causes of elements in LOST+FOUND.
  
 All cases listed below are examples of this core problem. All cases listed below are examples of this core problem.
Line 14: Line 16:
  
   * Create a work product WP1 with a link (or upload a file, or connect to a file in a CMS)   * Create a work product WP1 with a link (or upload a file, or connect to a file in a CMS)
-  * Create a version V1 and set it to valid+  * Create a process version V1 and set it to valid
   * Delete WP1 in the working version   * Delete WP1 in the working version
-  * Create a V2 and set it to valid+  * Create a process version V2 and set it to valid
  
 → LOST+FOUND folder is created for WP1 so that the link is not lost → LOST+FOUND folder is created for WP1 so that the link is not lost
Line 24: Line 26:
 Example: Example:
  
- * Create a role ROLE1 and assign a user +  *  Create a role ROLE1 and assign a user 
- * Create a version V1 and set it to valid +  *  Create a process version V1 and set it to valid 
- * Delete ROLE1 in the working version +  *  Delete ROLE1 in the working version 
- * Create a V2 and set it to valid+  *  Create a process version V2 and set it to valid
  
-→ LOST+FOUND folder is created for ROLE1 so that the user assignment is not lost and prevent the user from losing access rights+→ LOST+FOUND folder is created for ROLE1 so that the user assignment is not lost and prevents the user from losing access rights
  
 ==== 2. LOST + FOUND while using modules ==== ==== 2. LOST + FOUND while using modules ====
Line 45: Line 47:
 **Case 2.2: Local project data /guidance files** **Case 2.2: Local project data /guidance files**
  
-Project data is added locally in the integrated process for elements imported with a module. If those module elements are deleted with an update of the module or the module is removed completely  → LOST + FOUND+Project data is added locally to the integrated process for elements imported with a module. If those module elements are deleted during a module update or if the module is removed completely, the elements are moved to LOST+FOUND.
  
 **Case 2.3: Local sub-elements** **Case 2.3: Local sub-elements**
  
-If sub-elements are added locally in the integrated process for elements imported with a module. If those module elements are deleted with an update of the module or the module is removed completely  → LOST + FOUND+If sub-elements are added locally to elements imported with a module in the integrated process, and those module elements are later deleted during a module update or if the module is removed completely, the sub-elements are moved to LOST+FOUND.
  
 Case 2.3b: Elements are moved to another location which is then deleted with a module update/removal Case 2.3b: Elements are moved to another location which is then deleted with a module update/removal
  
-If an element from module A is moved under an element from module B and that element is deleted because of a module update/removal → LOST + FOUND+If an element from module A is moved under an element from module B and that element from module B is deleted due to a module update or removal, the element from module A is moved to LOST+FOUND.
  
 **Case 2.4a: Using a “structural module” in different versions** **Case 2.4a: Using a “structural module” in different versions**
  
-If a structural module is integrated with different versions, in the version that is imported last, some elements are missing.+If a structural module is integrated with different versions, the version imported last may have some missing elements. 
 + 
 +For example, V2 includes an element called FolderXYZ, which didn't exist in V1 but is used in Process 2. If Process 1 is updated or imported after Process 2, FolderXYZ will be moved to LOST+FOUND.
  
-E.g. V2 includes an element FolderXYZ, that didn’t exist yet in V1 but is used in Process 2. If Process 1 is updated/imported after Process 2, FolderXYZ will moved to LOST+FOUND.+Hint:  
  
-Hint:  +When using a common elements module for structure, tailoring, etc., and importing it into process modules that are then integrated elsewhere, always ensure that the process modules being integrated use the same version of the common elements module.
-When using a common elements module for structure, tailoring, etc., and importing it into process modules that are then integrated elsewhere, always ensure that only process modules with the same version of the common elements module are integrated together.+
  
 **Case 2.4.b: Common elements imported in different versions with different element identities** **Case 2.4.b: Common elements imported in different versions with different element identities**