Skip to Content

Changes for page Cleanup a running flow

Last modified by Carlijn Kokkeler on 2024/08/29 10:57
From version 2.2
edited by Erik Bakker
on 2022/06/13 09:55
Change comment: Update document after refactoring.
To version 7.1
edited by Carlijn Kokkeler
on 2023/09/22 15:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -advanced-lifecycle-management-cleanup-running-flow
1 +Cleanup a running flow
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,19 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -= Cleanup a running flow =
3 -
4 4  In this microlearning, we will focus on the part of the lifecycle management where you need to clean up a flow that is active on a runtime at the moment when the integration needs to be removed. It involves complexity in a sense that flow needs to be removed from the Deploy phase. Before it can be removed from the Create phase and further.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 -* Last update: August 27th, 2021
9 -* Required reading time: 5 minutes
10 -
11 11  == 1. Prerequisites ==
12 12  * Advanced knowledge of the eMagiz platform
13 --
14 14  
15 15  == 2. Key concepts ==
16 -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.
17 17  
18 -
19 -
20 20  == 3. Steps to remove a flow from Deploy ==
21 21  
14 +{{error}}
15 +Note that step 3.1 and step 3.2 will become obsolete when migrating to the 3rd generation runtime.
16 +{{/error}}
22 22  
23 23  === 3.1 Remove from runtimes ===
24 24  
... ... @@ -46,26 +46,19 @@
46 46  
47 47  It usually means that it will take a certain grace period before a flow is actually out of Deploy.
48 48  
44 +== 4. Key takeaways ==
49 49  
50 -
51 -
52 -== 4. Assignment ==
53 -
54 -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.
55 -
56 -== 5. Key takeaways ==
57 -
58 58  * A flow needs to be removed from all releases before it can be removed from Create - see specific micro-learning for that purpose
59 59  * Don't forget to clean the Manage phase with Alert triggers, and the properties from Deploy
60 60  
61 61  
62 62  
63 -== 6. Suggested Additional Readings ==
51 +== 5. Suggested Additional Readings ==
64 64  
65 65  If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
66 66  
67 -== 7. Silent demonstration video ==
55 +== 6. Silent demonstration video ==
68 68  
69 -There is no specific video * the steps above include sufficient information for now.
57 +There is no specific video - the steps above include sufficient information for now.
70 70  
71 71  )))((({{toc/}}))){{/container}}{{/container}}