Wiki source code of Legacy flow components
Version 2.1 by Erik Bakker on 2022/06/13 15:23
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | = Legacy flow components = | ||
| 3 | |||
| 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 | |||
| 6 | Should you have any questions, please get in touch with academy@emagiz.com. | ||
| 7 | |||
| 8 | == 1. Prerequisites == | ||
| 9 | |||
| 10 | * Basic knowledge of the eMagiz platform | ||
| 11 | * Advanced understanding of the components used within the models you control and monitor | ||
| 12 | |||
| 13 | == 2. Key concepts == | ||
| 14 | |||
| 15 | * This migration path defines all flow designer components that will become (or are) obsolete shortly | ||
| 16 | |||
| 17 | == 3. Legacy flow components == | ||
| 18 | |||
| 19 | 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. | ||
| 20 | |||
| 21 | * HornetQ componenten -> in-vm connection | ||
| 22 | * HTTP parameter map to XML transformer | ||
| 23 | * Image transformer | ||
| 24 | * ISO8583 componenten | ||
| 25 | * Mendix FileDocument WS request transformer | ||
| 26 | * ThClient componenten | ||
| 27 | * Sonic en WebSphere componenten | ||
| 28 | |||
| 29 | ===== Practice ===== | ||
| 30 | |||
| 31 | == 4. Key takeaways == | ||
| 32 | |||
| 33 | * This migration path defines all flow designer components that will become (or are) obsolete shortly | ||
| 34 | |||
| 35 | )))((({{toc/}}))){{/container}}{{/container}} |