Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 14:37
From version 1.1
edited by eMagiz
on 2022/05/17 09:09
Change comment: There is no comment for this version
To version 2.1
edited by Erik Bakker
on 2022/06/10 08:38
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,16 +1,9 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -
5 -<div class="doc">
6 -
7 -
8 -
1 +{{container}}{{container layoutStyle="columns"}}(((
9 9  = Making clear what you changed (auditability) =
10 10  
11 11  As you can imagine, there is a need to know what has changed when working with software tooling. By knowing you can assess the impact of your planned changes within the context of the integration data model. In this microlearning, we will look at what you can do to clarify what you changed within the eMagiz platform.
12 12  
13 -Should you have any questions, please contact academy@emagiz.com.
6 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14 14  
15 15  * Last update: August 4th, 2021
16 16  * Required reading time: 6 minutes
... ... @@ -74,8 +74,8 @@
74 74  
75 75  In all cases, you will find a History button on the page in question that will guide you to the history (audit trail) of what has changed by whom at which point in time.
76 76  
77 -===== Practice =====
78 78  
71 +
79 79  == 4. Assignment ==
80 80  
81 81  Check out the history of (one of) your eMagiz data models, one of your flows, and your releases to see if you can determine how they have changed over time.
... ... @@ -99,9 +99,4 @@
99 99  
100 100  As this is a more theoretical microlearning we have no video for this.
101 101  
102 -</div>
103 -
104 -</div>
105 -</div>
106 -
107 -{{/html}}
95 +)))((({{toc/}}))){{/container}}{{/container}}