Skip to Content
Last modified by Erik Bakker on 2024/09/09 12:31
From version 19.2
edited by eMagiz
on 2022/06/13 14:49
Change comment: Update document after refactoring.
To version 22.1
edited by Erik Bakker
on 2022/06/13 14:51
Change comment: Deleted image "migration-path-emagiz-error-flow--clean-error-flow.png"

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -migration-path-emagiz-error-flow
1 +Error flow
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,13 +1,4 @@
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 -
1 +{{container}}{{container layoutStyle="columns"}}(((
11 11  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.
12 12  
13 13  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -23,8 +23,6 @@
23 23  
24 24  * The error flow is updated to make it more robust in handling unexpectedly large errors
25 25  
26 -
27 -
28 28  == 3. Migration Path * Error flow ==
29 29  
30 30  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.
... ... @@ -33,13 +33,13 @@
33 33  
34 34  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.
35 35  
36 -<p align="center">[[image:migration-path-emagiz-error-flow--message-tracking-error-flow.png||]]</p>
25 +[[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--message-tracking-error-flow.png]]
37 37  
38 38  === 3.2 New approach ===
39 39  
40 40  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.
41 41  
42 -<p align="center">[[image:migration-path-emagiz-error-flow--clean-error-flow.png||]]</p>
31 +[[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--clean-error-flow.png]]
43 43  
44 44  === 3.3 How to get to the new approach ===
45 45  
... ... @@ -66,14 +66,8 @@
66 66  * If changes exist, analyze them and make changes where necessary
67 67   Congratulations, you have successfully migrated the error flow to the new setup
68 68  
69 -===== Practice =====
70 -
71 71  == 4. Key takeaways ==
72 72  
73 73  * The error flow is updated to make it more robust in handling unexpectedly large errors
74 74  
75 -</div>
76 -</div>
77 -</div>
78 -
79 -{{/html}}
62 +)))((({{toc/}}))){{/container}}{{/container}}
migration-path-emagiz-error-flow--clean-error-flow.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content