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 11.6
edited by Danniar Firdausy
on 2024/09/18 14:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -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.
2 +In the world of software tooling, it's crucial to understand what changes have been made to effectively evaluate their impact. This microlearning will guide you through the process of clarifying changes within the eMagiz platform, focusing on the importance of clear and detailed descriptions for auditability. By the end of this microlearning, you will know how to properly document and version your changes to maintain a clear history and facilitate better integration management.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -10,16 +10,8 @@
10 10  == 2. Key concepts ==
11 11  
12 12  This microlearning centers on making clear what you changed (auditability).
13 +* By auditability, we mean: A history trail that depicts who changed what at which moment in time containing an explanation of what has been changed
13 13  
14 -Auditability is defined as follows: A history trail that depicts who changed what at which moment in time containing an explanation of what has been changed
15 -
16 -* The key aspects are:
17 - ** The description is your way of communicating the history of the flow
18 - ** Using vague descriptions (or placing a dot as description) hurts the auditability
19 - ** For all things versioned in eMagiz it is crucial that you supply the correct description
20 - ** eMagiz provides audit trails on Architectural overviews (Design and Deploy architecture) including a description
21 - ** eMagiz provides audit trails on message definitions and transformations including a description
22 -
23 23  == 3. Making clear what you changed (auditability) ==
24 24  
25 25  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.
... ... @@ -60,23 +60,25 @@
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 ==
55 +== 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.
57 +* Ensure that all descriptions are detailed and specific to effectively communicate the history of changes.
58 +* For all versioned elements within the eMagiz platform, including data models, flows, and releases, providing precise descriptions helps in tracking modifications and understanding their impact.
59 +* Utilize the audit trails provided by eMagiz for Architectural overviews, message definitions, and transformations to keep a comprehensive history of changes. This feature is vital for maintaining transparency and accountability in your integration processes.
60 +* By maintaining clear and accurate documentation of changes, you improve the ability to assess impacts and manage integration data models more effectively, ensuring smoother operations and fewer misunderstandings.
66 66  
67 -== 5. Key takeaways ==
62 +== 5. Suggested Additional Readings ==
68 68  
69 -* The key aspects are:
70 - ** The description is your way of communicating the history of the flow
71 - ** Using vague descriptions (or placing a dot as description) hurts the auditability
72 - ** For all things versioned in eMagiz it is crucial that you supply the correct description
73 - ** eMagiz provides audit trails on Architectural overviews (Design and Deploy architecture) including a description
74 - ** eMagiz provides audit trails on message definitions and transformations including a description
64 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
75 75  
76 -== 6. Suggested Additional Readings ==
77 -
78 -If you are interested in this topic and want more information please check out the help texts provided by eMagiz.
79 -
80 -== 7. Silent demonstration video ==
81 -
82 -As this is a more theoretical microlearning we have no video for this.)))((({{toc/}}))){{/container}}{{/container}}
66 +* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-defining-a-message-format||target="blank"]]
67 +** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
68 +*** [[Promote flows to deploy (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-promote-flows-to-deploy||target="blank"]]
69 +*** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]]
70 +* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
71 +** [[Defining message structures (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining message structures.WebHome||target="blank"]]
72 +*** [[Audit eMagiz Data Models (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining message structures.intermediate-defining-your-message-structures-audit-emagiz-data-models||target="blank"]]
73 +** [[Release Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.WebHome||target="blank"]]
74 +*** [[Autoclean releases (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.intermediate-release-management-autoclean-releases||target="blank"]]
75 +* [[Making clear what you changed (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22making+clear+what+you+changed%22||target="blank"]]
76 +)))((({{toc/}}))){{/container}}{{/container}}