Changes for page Cleanup a running flow
Last modified by Carlijn Kokkeler on 2024/08/29 10:57
From version 5.1
edited by Erik Bakker
on 2022/10/03 12:55
on 2022/10/03 12:55
Change comment:
There is no comment for this version
To version 6.1
edited by Carlijn Kokkeler
on 2023/09/19 14:38
on 2023/09/19 14:38
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -38,25 +38,18 @@ 38 38 39 39 It usually means that it will take a certain grace period before a flow is actually out of Deploy. 40 40 41 +== 4. Key takeaways == 41 41 42 - 43 - 44 -== 4. Assignment == 45 - 46 -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. 47 - 48 -== 5. Key takeaways == 49 - 50 50 * A flow needs to be removed from all releases before it can be removed from Create - see specific micro-learning for that purpose 51 51 * Don't forget to clean the Manage phase with Alert triggers, and the properties from Deploy 52 52 53 53 54 54 55 -== 6. Suggested Additional Readings ==48 +== 5. Suggested Additional Readings == 56 56 57 57 If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz 58 58 59 -== 7. Silent demonstration video ==52 +== 6. Silent demonstration video == 60 60 61 61 There is no specific video - the steps above include sufficient information for now. 62 62