Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 4.1
edited by eMagiz
on 2022/06/10 13:12
Change comment: There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2022/09/01 09:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -3,9 +3,6 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: October 19th, 2021
7 -* Required reading time: 4 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
... ... @@ -20,8 +20,6 @@
20 20  * Are there dependencies?
21 21  * Will the failure of integration block another?
22 22  
23 -
24 -
25 25  == 3. Considering Dependencies between integrations ==
26 26  
27 27  In this microlearning, we will learn what you should consider when looking at dependencies between integrations. An integration solution can consist of loads of different integrations, and several of those integrations can depend on each other. For example, when looking at an Order 2 Cash process in which an order travels from system A to B, and as a result, various messages are returned in sequence (i.e., conformation, shipment, invoice). Logic dictates that, for example, when the order never arrives, the other integrations will also not receive any data. Therefore it is relevant to consider these dependencies while performing a risk assessment.