Skip to Content

Changes for page Cleanup a running flow

Last modified by Carlijn Kokkeler on 2024/08/29 10:57
From version 3.1
edited by Erik Bakker
on 2022/06/13 09:56
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2024/02/23 08:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,29 +3,22 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: August 27th, 2021
7 -* Required reading time: 5 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  * Advanced knowledge of the eMagiz platform
11 --
12 12  
13 13  == 2. Key concepts ==
14 -The most important for this micro-learning to understand is that a flow needs be removed from the Deploy phase before it can be removed from the integration model that is in Capture, Design and Create. Removing a flow from the model before removing it from Deploy results in "ghost" flows that result in unexpected behavior in the Deploy phases.
10 +The most important for this microlearning to understand is that a flow needs be removed from the Deploy phase before it can be removed from the integration model that is in Capture, Design and Create. Removing a flow from the model before removing it from Deploy results in "ghost" flows that result in unexpected behavior in the Deploy phases.
15 15  
16 -
17 -
18 18  == 3. Steps to remove a flow from Deploy ==
19 19  
14 +=== 3.1 Remove from all releases ===
20 20  
21 -=== 3.1 Remove from runtimes ===
16 +1. Remove the flow from the active release by creating a new release and deselecting the integration.
17 +2. Once deselected make sure that the new release is deployed on all your environments.
18 +3. Remove all old releases that still have a reference to the flow.
22 22  
23 -1. Stop the flow from the runtime where its active. Remove on all runtimes where it is active
24 -2. Uninstall the flow from the runtime(s) where it was active
25 -3. Update the Container assignment to remove the flow from the Containers
26 -
27 27  === 3.2 Remove unused Properties ===
28 -Ensure to remove the associated properties from each TAP environment specific to this flow. Refer to the micro-learning that explains that process.
21 +Ensure to remove the associated properties from each TAP environment specific to this flow. Refer to the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Lifecycle Management.intermediate-lifecycle-management-cleanup-properties-gen3.WebHome||target="blank"]] that explains that process.
29 29  
30 30  === 3.3 Remove alerting triggers ===
31 31  
... ... @@ -44,26 +44,15 @@
44 44  
45 45  It usually means that it will take a certain grace period before a flow is actually out of Deploy.
46 46  
40 +== 4. Key takeaways ==
47 47  
48 -
49 -
50 -== 4. Assignment ==
51 -
52 -Determine whether you can clean up a deployed flow within your project. If so, execute the cleanup from Deploy as displayed above. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
53 -
54 -== 5. Key takeaways ==
55 -
56 56  * A flow needs to be removed from all releases before it can be removed from Create - see specific micro-learning for that purpose
57 57  * Don't forget to clean the Manage phase with Alert triggers, and the properties from Deploy
58 58  
59 59  
60 60  
61 -== 6. Suggested Additional Readings ==
47 +== 5. Suggested Additional Readings ==
62 62  
63 63  If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
64 64  
65 -== 7. Silent demonstration video ==
66 -
67 -There is no specific video * the steps above include sufficient information for now.
68 -
69 69  )))((({{toc/}}))){{/container}}{{/container}}