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 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
Content
... ... @@ -1,5 +1,8 @@
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 +{{container}}{{container layoutStyle="columns"}}(((
2 += Legacy flow components =
2 2  
4 +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.
5 +
3 3  Should you have any questions, please get in touch with academy@emagiz.com.
4 4  
5 5  == 1. Prerequisites ==
... ... @@ -23,6 +23,8 @@
23 23  * ThClient componenten
24 24  * Sonic en WebSphere componenten
25 25  
29 +===== Practice =====
30 +
26 26  == 4. Key takeaways ==
27 27  
28 28  * This migration path defines all flow designer components that will become (or are) obsolete shortly