Wiki source code of Error flow
Version 20.1 by Erik Bakker on 2022/06/13 14:50
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
20.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
1.1 | 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 | |||
| 4 | Should you have any questions, please get in touch with academy@emagiz.com. | ||
| 5 | |||
| 6 | * Last update: March 1st, 2022 | ||
| 7 | * Required reading time: 4 minutes | ||
| 8 | |||
| 9 | == 1. Prerequisites == | ||
| 10 | |||
| 11 | * Basic knowledge of the eMagiz platform | ||
| 12 | |||
| 13 | == 2. Key concepts == | ||
| 14 | |||
| 15 | * The error flow is updated to make it more robust in handling unexpectedly large errors | ||
| 16 | |||
| 17 | == 3. Migration Path * Error flow == | ||
| 18 | |||
| 19 | 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. | ||
| 20 | |||
| 21 | === 3.1 Legacy approach === | ||
| 22 | |||
| 23 | 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. | ||
| 24 | |||
| |
20.1 | 25 | [[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--message-tracking-error-flow.png]] |
| |
1.1 | 26 | |
| 27 | === 3.2 New approach === | ||
| 28 | |||
| 29 | 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. | ||
| 30 | |||
| |
20.1 | 31 | [[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--clean-error-flow.png]] |
| |
1.1 | 32 | |
| 33 | === 3.3 How to get to the new approach === | ||
| 34 | |||
| 35 | Migrating from the old to the new error flow takes several steps to make it work correctly. Below you will find all these steps. Follow them carefully to achieve the desired result. | ||
| 36 | |||
| 37 | 1. Determine if you made any custom changes to the error handling | ||
| 38 | |||
| 39 | * If yes, continue with step 2 | ||
| 40 | * If not, continue with step 4 | ||
| 41 | |||
| 42 | 2. Determine if these changes are still justified | ||
| 43 | |||
| 44 | * If not, continue with step 4 | ||
| 45 | * If yes, continue with step 3 | ||
| 46 | |||
| 47 | 3. Write down all manual changes you still need | ||
| 48 | 4. Navigate to Create | ||
| 49 | 5. Right-click on the Error process and press Reset flow | ||
| 50 | 6. Add the manual changes back to the flow (if there are any manual changes) | ||
| 51 | 7. Test the flow | ||
| 52 | 8. Verify your results | ||
| 53 | |||
| 54 | * If the result is the same, you are finished | ||
| 55 | * If changes exist, analyze them and make changes where necessary | ||
| 56 | Congratulations, you have successfully migrated the error flow to the new setup | ||
| 57 | |||
| 58 | ===== Practice ===== | ||
| 59 | |||
| 60 | == 4. Key takeaways == | ||
| 61 | |||
| 62 | * The error flow is updated to make it more robust in handling unexpectedly large errors | ||
| 63 | |||
| |
20.1 | 64 | )))((({{toc/}}))){{/container}}{{/container}} |