Skip to Content
Last modified by Erik Bakker on 2024/09/09 12:31
From version 24.1
edited by Erik Bakker
on 2023/01/23 13:17
Change comment: There is no comment for this version
To version 18.1
edited by eMagiz
on 2022/06/13 09:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Error flow
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Content
... ... @@ -1,8 +1,20 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
4 +
5 +<div class="doc">
6 +
7 +
8 +
9 += Migration Path * Error flow =
10 +
2 2  The error flow is part of the default in any eMagiz project. This flow handles all errors that are thrown by (a)synchronous flows within your project and passes them through to the iPaaS, so they show up under Manage -> Error Messages. Recently we have made some changes to make the error flow work even more optimal.
3 3  
4 -Should you have any questions, please get in touch with academy@emagiz.com.=
13 +Should you have any questions, please get in touch with academy@emagiz.com.
5 5  
15 +* Last update: March 1st, 2022
16 +* Required reading time: 4 minutes
17 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Basic knowledge of the eMagiz platform
... ... @@ -11,6 +11,8 @@
11 11  
12 12  * The error flow is updated to make it more robust in handling unexpectedly large errors
13 13  
26 +
27 +
14 14  == 3. Migration Path * Error flow ==
15 15  
16 16  The error flow is part of the default in any eMagiz project. This flow handles all errors that are thrown by (a)synchronous flows within your project and passes them through to the iPaaS, so they show up under Manage -> Error Messages. Recently we have made some changes to make the error flow work even more optimal.
... ... @@ -19,13 +19,13 @@
19 19  
20 20  In the legacy situation, the flow would determine whether or not message tracking was enabled for each message. Based on that, the error handling responded in a slightly different manner.
21 21  
22 -[[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--message-tracking-error-flow.png]]
36 +<p align="center">[[image:migration-path-emagiz-error-flow--message-tracking-error-flow.png||]]</p>
23 23  
24 24  === 3.2 New approach ===
25 25  
26 26  In the new situation, the flow treats all messages the same and removes all headers to reduce the chance the error message will cause problems downstream for the iPaaS or the portal.
27 27  
28 -[[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--clean-error-flow.png]]
42 +<p align="center">[[image:migration-path-emagiz-error-flow--clean-error-flow.png||]]</p>
29 29  
30 30  === 3.3 How to get to the new approach ===
31 31  
... ... @@ -52,8 +52,14 @@
52 52  * If changes exist, analyze them and make changes where necessary
53 53   Congratulations, you have successfully migrated the error flow to the new setup
54 54  
69 +===== Practice =====
70 +
55 55  == 4. Key takeaways ==
56 56  
57 57  * The error flow is updated to make it more robust in handling unexpectedly large errors
58 58  
59 -)))((({{toc/}}))){{/container}}{{/container}}
75 +</div>
76 +</div>
77 +</div>
78 +
79 +{{/html}}
migration-path-emagiz-error-flow--clean-error-flow.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.marijn
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content
migration-path-emagiz-error-flow--message-tracking-error-flow.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.marijn
Size
... ... @@ -1,0 +1,1 @@
1 +15.9 KB
Content