Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 14:37
From version 8.1
edited by Erik Bakker
on 2023/01/23 09:08
Change comment: There is no comment for this version
To version 9.1
edited by Eva Torken
on 2023/08/23 13:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -60,12 +60,8 @@
60 60  
61 61  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.
62 62  
63 -== 4. Assignment ==
63 +== 4. Key takeaways ==
64 64  
65 -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.
66 -
67 -== 5. Key takeaways ==
68 -
69 69  * The key aspects are:
70 70   ** The description is your way of communicating the history of the flow
71 71   ** Using vague descriptions (or placing a dot as description) hurts the auditability
... ... @@ -73,10 +73,8 @@
73 73   ** eMagiz provides audit trails on Architectural overviews (Design and Deploy architecture) including a description
74 74   ** eMagiz provides audit trails on message definitions and transformations including a description
75 75  
76 -== 6. Suggested Additional Readings ==
72 +== 5. Suggested Additional Readings ==
77 77  
78 78  If you are interested in this topic and want more information please check out the help texts provided by eMagiz.
79 79  
80 -== 7. Silent demonstration video ==
81 -
82 -As this is a more theoretical microlearning we have no video for this.)))((({{toc/}}))){{/container}}{{/container}}
76 +)))((({{toc/}}))){{/container}}{{/container}}