Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 10.1
edited by Erik Bakker
on 2022/04/21 14:38
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/04/21 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,9 +35,10 @@
35 35  In this microlearning, we will learn what you should consider determining the impact of business logic within your integration solution. An eMagiz model is most useful when exchanging data between systems while taking care of data and protocol transformations. For example, an eMagiz model is generally less suited for incorporating business logic as these rules cannot be defined dynamically and are relatively complex. Filling your eMagiz model with a lot of business logic opens you up for a continuous discussion about data and interpretations of business rules. As that is not the core goal of an eMagiz model, you should always ask yourself what the most suitable place is to incorporate pieces of logic.
36 36  
37 37  
38 -(% style="text-align:center" %)
39 -[[image:advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png||alt="Figure one"]]
38 +(% class="wikigeneratedid" %)
39 +[[Caption>>image:advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png||alt="Figure one" id="Iadvanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png"]]
40 40  
41 +
41 41  The most exciting point when talking about business logic is:
42 42  
43 43  * Where to draw the line?