Differences

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

--- 710:lost_found [2024/07/30 13:43] – Lachner, Ingo
+++ 710:lost_found [2024/07/31 07:19] (current) – [How to handle elements in LOST+FOUND] Lachner, Ingo
@@ Line 1: / Line 1: @@
 ====== How to handle elements in LOST+FOUND ======
-**Root cause for LOST+FOUND**
+**Root cause for LOST+FOUND **
-An element is removed, but other objects - e.g. elements, files, user assignments - for which Stages did not receive an explicit order to delete, are dependent on that element.
+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.
-All cases listed below are variations of this core problem.
+We recommend that you contact your Method Park by UL Solutions consultant to analyse the root causes of elements in LOST+FOUND.
-====== Different variations: ======
+All cases listed below are examples of this core problem.
-. LOST + FOUND after release of a new valid version
+==== 1. LOST + FOUND after the release of a new valid version ====
-Case 1.1: A work product with a file (=project data) with a file is deleted
-Working Version:
+**Case 1.1: A work product with a linked file is deleted**
-Create a work product WP1 with a link (or upload a file, or connect to a file in a CMS)
+Example:
-Create a version V1 and set it to valid
+  * Create a work product WP1 with a link (or upload a file, or connect to a file in a CMS)
+  * Create a process version V1 and set it to valid
+  * Delete WP1 in the working version
+  * Create a process version V2 and set it to valid
-Delete WP1 in the working version
+→ LOST+FOUND folder is created for WP1 so that the link is not lost
-Create a V2 and set it to valid
+**Case 1.2: A role with a user assignment is deleted**
-LOST+FOUND folder is created for WP1 so that the link is not lost
+Example:
-Case 1.2: A role with a user assignment (=project data) is deleted
+  *  Create a role ROLE1 and assign a user
+  *  Create a process version V1 and set it to valid
+  *  Delete ROLE1 in the working version
+  *  Create a process version V2 and set it to valid
- Proceed like in Case 1.1, only in this case use a role and assign a user.
+→ LOST+FOUND folder is created for ROLE1 so that the user assignment is not lost and prevents the user from losing access rights
-→ User assignment and therefore maybe access rights would be lost if the role was deleted.
+==== 2. LOST + FOUND while using modules ====
+**Case 2.1: Imported project data/guidance files**
-This probably happens only for work products, guidance, and roles
+Example:
+  * integrate process version V1 of Case 1.1 or Case 1.2 into a new process
+  * make the update and create V2 (see Case 1.1 or Case 1.2)
+  * update integrated process to use V2
-. Modules, modules, modules
+→ LOST+FOUND folder is created in the integrated process
-Case 2.1: Imported project data/guidance files
-Integrate V1 in Case 1.1 or Case 1.2 in process, make an update with V2 → LOST+FOUND in the integrated process
-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**
-Sub-elements are locally added 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
-If you move an element from module A 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 the structure module is integrated with different versions, it might happen that 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.
-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 land in LOST+FOUND.
+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.
-:exclamation: → If you use a common elements module (for structure, tailoring, etc.) which is imported into process modules, that are in turn integrated together somewhere else, always make sure that only process modules are integrated there that include the same version of the common elements module
+Hint:
-Case 2.4.b: Common elements imported in different versions with different element identities
+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.
-Should be a rare case, but if it happens it might be difficult to detect. It is a variation of Case 2.4.
+**Case 2.4.b: Common elements imported in different versions with different element identities**
-It can happen that the elements in the common elements module get new identities.
-For example,
+This should be a rare case, but if it happens, it might be difficult to detect. It is a variation of Case 2.4.
-if they were deleted and created again with the same name
+The elements in the common elements module can receive new identities, for example:
-if they were imported by an importer that always creates new identities.
+  * If they were deleted and recreated with the same name
+  * If they were imported by an importer that always creates new identities
+  * Other reasons for new identities
+At first glance, these elements look the same because they have the same name, but due to the different identities, they are considered different objects by Stages.
-other reasons for new identities :question_mark:
+**Case 2.4.c: On-demand problems**
-At first glance, they look the same because they have the same name, but because of the different identities they are different objects for Stages
+When using common elements with on-demand import, a folder element (or another parent element) might be imported into module A.
+If it is later decided that the on-demand element is no longer needed in module A, and the folder element is deleted, issues can arise if that folder element is still needed for on-demand elements from other modules in the integrated workspace.
-Case 2.4.c: On-demand problems
+If module A was the last module imported or updated in the integrated workspace, and it is now updated again without the folder element, Stages thinks it needs to delete the folder element. However, since the folder element has sub-elements from other modules, it is moved to LOST+FOUND instead.
-If you use common elements with on-demand import, it might happen that with that on-demand import a folder element (or other parent element) is imported in module A.
-At some point maybe, it is decided that the on-demand element is no longer needed in module A, and therefore also the folder element is deleted.
-If this folder element is also needed for other on-demand elements from other modules in the integrated workspace AND if module A was the last module that was imported/updated in the integrated workspace AND is now updated again without that folder element, Stages thinks it needs to delete it but pushes it in LOST + FOUND instead, because it has sub-elements from other modules.