Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 65.1
edited by Erik Bakker
on 2023/04/13 08:46
Change comment: There is no comment for this version
To version 67.1
edited by Erik Bakker
on 2023/04/13 14:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,6 +2,22 @@
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
4 4  
5 +=====New features=====
6 +
7 +We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
8 +
9 +When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties.
10 +
11 +These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered. If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
12 +
13 +A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
14 +
15 +{{info}}Important to note is that
16 +* 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.
17 +* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
18 +* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
19 +* 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}}
20 +
5 5  =====Minor changes=====
6 6  
7 7  * General - Control Tower: Changed several generic triggers for more predictable behavior.