Changes for page 201 - Be Informed

Last modified by Carlijn Kokkeler on 2024/04/18 13:13

From version 100.1
edited by Erik Bakker
on 2023/04/13 08:56
Change comment: There is no comment for this version
To version 101.1
edited by Erik Bakker
on 2023/04/13 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,8 +6,16 @@
6 6  
7 7  == **Release properties** ==**
8 8  
9 -With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]]
9 +With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
10 10  
11 +As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
12 +
13 +{{info}}The following considerations need to be taken into account when using this functionality:
14 +* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
15 +* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
16 +* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
17 +*{{/info}}
18 +
11 11  == **API improvements** ==
12 12  
13 13  //__Improved auto-generated error handling__//