Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 3.1
edited by eMagiz
on 2022/06/10 13:12
Change comment: There is no comment for this version
To version 2.1
edited by Erik Bakker
on 2022/06/10 08:37
Change comment: Imported from XAR

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Considering Dependencies between integrations
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,4 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Considering Dependencies between integrations =
3 +
2 2  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.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].