Skip to Content

Changes for page Legacy flow components

Last modified by Erik Bakker on 2024/09/09 12:49
From version 4.1
edited by Erik Bakker
on 2023/01/23 13:20
Change comment: There is no comment for this version
To version 1.1
edited by eMagiz
on 2022/06/13 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Legacy flow components
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Content
... ... @@ -1,7 +1,20 @@
1 -{{container}}{{container layoutStyle="columns"}}(((Below you will find a list of flow components deemed legacy by eMagiz. For example, suppose you are using any of the components listed below. In that case, your partner manager will contact you about valid alternatives or a migration path to remove these components from your flows.
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
2 2  
5 +<div class="doc">
6 +
7 +
8 +
9 += Migration Path * Legacy flow components =
10 +
11 +Below you will find a list of flow components deemed legacy by eMagiz. For example, suppose you are using any of the components listed below. In that case, your partner manager will contact you about valid alternatives or a migration path to remove these components from your flows.
12 +
3 3  Should you have any questions, please get in touch with academy@emagiz.com.
4 4  
15 +* Last update: March 1st, 2022
16 +* Required reading time: 3 minutes
17 +
5 5  == 1. Prerequisites ==
6 6  
7 7  * Basic knowledge of the eMagiz platform
... ... @@ -11,8 +11,10 @@
11 11  
12 12  * This migration path defines all flow designer components that will become (or are) obsolete shortly
13 13  
14 -== 3. Legacy flow components ==
15 15  
28 +
29 +== 3. Migration Path * Legacy flow components ==
30 +
16 16  Below you will find a list of flow components deemed legacy by eMagiz. For example, suppose you are using any of the components listed below. In that case, your partner manager will contact you about valid alternatives or a migration path to remove these components from your flows.
17 17  
18 18  * HornetQ componenten -> in-vm connection
... ... @@ -23,8 +23,14 @@
23 23  * ThClient componenten
24 24  * Sonic en WebSphere componenten
25 25  
41 +===== Practice =====
42 +
26 26  == 4. Key takeaways ==
27 27  
28 28  * This migration path defines all flow designer components that will become (or are) obsolete shortly
29 29  
30 -)))((({{toc/}}))){{/container}}{{/container}}
47 +</div>
48 +</div>
49 +</div>
50 +
51 +{{/html}}