Changes for page Legacy flow components

Last modified by Erik Bakker on 2024/09/09 12:49

From version 1.2
edited by eMagiz
on 2022/06/13 15:22
Change comment: Update document after refactoring.
To version 2.1
edited by Erik Bakker
on 2022/06/13 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -migration-path-legacy-components
1 +Legacy flow components
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,20 +1,10 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
1 +{{container}}{{container layoutStyle="columns"}}(((
2 += Legacy flow components =
4 4  
5 -<div class="doc">
6 -
7 -
8 -
9 -= Migration Path * Legacy flow components =
10 -
11 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 12  
13 13  Should you have any questions, please get in touch with academy@emagiz.com.
14 14  
15 -* Last update: March 1st, 2022
16 -* Required reading time: 3 minutes
17 -
18 18  == 1. Prerequisites ==
19 19  
20 20  * Basic knowledge of the eMagiz platform
... ... @@ -24,10 +24,8 @@
24 24  
25 25  * This migration path defines all flow designer components that will become (or are) obsolete shortly
26 26  
17 +== 3. Legacy flow components ==
27 27  
28 -
29 -== 3. Migration Path * Legacy flow components ==
30 -
31 31  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.
32 32  
33 33  * HornetQ componenten -> in-vm connection
... ... @@ -44,8 +44,4 @@
44 44  
45 45  * This migration path defines all flow designer components that will become (or are) obsolete shortly
46 46  
47 -</div>
48 -</div>
49 -</div>
50 -
51 -{{/html}}
35 +)))((({{toc/}}))){{/container}}{{/container}}