Skip to Content

Changes for page 195 - Easter Party

Last modified by Carlijn Kokkeler on 2024/04/18 13:17
From version 103.1
edited by Erik Bakker
on 2023/04/13 14:29
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
... ... @@ -10,16 +10,11 @@
10 10  
11 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 12  
13 -{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
14 -
15 15  {{info}}The following considerations need to be taken into account when using this functionality:
16 16  * This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
17 17  * This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
18 18  * In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
19 -* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
20 -* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
21 -* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
22 -* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
17 +*{{/info}}
23 23  
24 24  == **API improvements** ==
25 25