Skip to Content

Changes for page Cleanup a running flow

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Cleanup a running flow
1 +advanced-lifecycle-management-cleanup-running-flow
Content
... ... @@ -1,14 +1,22 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Cleanup a running flow =
3 +
2 2  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.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: August 27th, 2021
9 +* Required reading time: 5 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  * Advanced knowledge of the eMagiz platform
13 +-
8 8  
9 9  == 2. Key concepts ==
10 10  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.
11 11  
18 +
19 +
12 12  == 3. Steps to remove a flow from Deploy ==
13 13  
14 14  
... ... @@ -58,6 +58,6 @@
58 58  
59 59  == 7. Silent demonstration video ==
60 60  
61 -There is no specific video - the steps above include sufficient information for now.
69 +There is no specific video * the steps above include sufficient information for now.
62 62  
63 63  )))((({{toc/}}))){{/container}}{{/container}}