Wiki source code of Adding notes to your Design transformation
Last modified by Danniar Firdausy on 2024/09/16 14:08
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
16.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}} | ||
| |
19.5 | 3 | (((In this microlearning, we will explore how to document your transformations during the Design phase. Many transformations take place through discussions with business owners or by reviewing business documentation. Thus, keeping track of decisions with notes is essential for effective documentation. |
| |
1.1 | 4 | |
| |
17.1 | 5 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 6 | |
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Novice knowledge of the eMagiz platform including transformations | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| 13 | There are no specific concepts to consider for now that require additional explanation | ||
| 14 | |||
| 15 | == 3. Adding a note to a transformation == | ||
| 16 | |||
| |
19.3 | 17 | Navigate in the Design phase to the specific message mapping, topic mapping, request or response mapping. In the edit mode, you can right click on the specific target atrribute and press Add notes. This option is only available on the target attributes as that is the most logical to describe the transformation. |
| |
1.1 | 18 | |
| |
16.1 | 19 | [[image:Main.Images.Microlearning.WebHome@intermediate-design-transformations-adding-notes_1.png]] |
| |
1.1 | 20 | |
| |
19.1 | 21 | == 4. Key takeaways == |
| |
1.1 | 22 | |
| |
19.5 | 23 | * Documenting transformation decisions with notes in the Design phase is crucial for maintaining clear and accurate records. |
| 24 | * Thorough and detailed notes help ensure that transformations are well-documented and understood. | ||
| 25 | * Adding notes in the Design phase will facilitate smoother transitions and more effective work in the Create phase. | ||
| |
1.1 | 26 | |
| |
19.1 | 27 | == 5. Suggested Additional Readings == |
| |
1.1 | 28 | |
| |
19.2 | 29 | 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: |
| |
1.1 | 30 | |
| |
19.4 | 31 | * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] |
| 32 | ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] | ||
| 33 | *** [[Creating a message definition (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-creating-a-message-definition||target="blank"]] | ||
| 34 | *** [[What is a message mapping (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-what-is-a-message-mapping||target="blank"]] | ||
| |
19.2 | 35 | * [[Add Note (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=%22add+note%22||target="blank"]] |
| 36 | |||
| |
19.1 | 37 | ))) |
| |
1.1 | 38 | |
| |
16.1 | 39 | ((({{toc/}}))){{/container}} |
| 40 | {{/container}} |