Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 14:37
From version 7.1
edited by Erik Bakker
on 2022/08/30 08:23
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2022/08/30 08:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,7 +41,7 @@
41 41  
42 42  ==== 3.1.1 eMagiz Data Model ====
43 43  
44 -On the eMagiz data model level in Design, you can version your eMagiz Data model. By doing this you can register per the eMagiz data model what you have changed. If you want practical help in learning how you can version your eMagiz data model please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining message structures.intermediate-defining-your-message-structures-audit-emagiz-data-models.WebHome||target="blank"]]. Doing so is crucial in telling others now (and in the future) what you have changed and why you have changed that portion of the eMagiz data model.
44 +On the eMagiz data model level in Design, you can version your eMagiz Data model. By doing this you can register per the eMagiz data model what you have changed. If you want practical help in learning how you can version your eMagiz data model please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining your message structures.intermediate-defining-your-message-structures-audit-emagiz-data-models.WebHome||target="blank"]]. Doing so is crucial in telling others now (and in the future) what you have changed and why you have changed that portion of the eMagiz data model.
45 45  
46 46  ==== 3.1.2 eMagiz Flows ====
47 47  
... ... @@ -49,7 +49,7 @@
49 49  
50 50  ==== 3.1.3 eMagiz Releases ====
51 51  
52 -On the eMagiz release level, you need to create a new version whenever you want to include new versions of flows in a release. There is one exception to this rule and that is when someone else has already created a new release that is not yet deployed or made active. In that scenario, you can both combine all changes that need to de deployed to create a more efficient deployment. With eMagiz releases, you have two ways of notifying others what the release is all about. The first one is the name of the release and the second one is the description of a release. If you want to learn how to create a release please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release.WebHome||target="blank"]]. If you want to learn more about managing releases please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.intermediate-release-management-autoclean-releases.WebHome||target="blank"]].
52 +On the eMagiz release level, you need to create a new version whenever you want to include new versions of flows in a release. There is one exception to this rule and that is when someone else has already created a new release that is not yet deployed or made active. In that scenario, you can both combine all changes that need to de deployed to create a more efficient deployment. With eMagiz releases, you have two ways of notifying others what the release is all about. The first one is the name of the release and the second one is the description of a release. If you want to learn how to create a release please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release.WebHome||target="blank"]]. If you want to learn more about managing releases please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.intermediate-release-management-managing-releases-best-practice.WebHome||target="blank"]].
53 53  
54 54  === 3.2 Versioning by eMagiz ===
55 55