Skip to Content

Changes for page Cleanup properties

Last modified by Danniar Firdausy on 2024/09/18 13:46
From version 5.1
edited by Eva Torken
on 2023/08/23 16:34
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2024/02/23 09:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.etorken
1 +XWiki.ebakker
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -In this microlearning, we will focus on cleaning up your properties that you use in a particular environment (Test, Acceptance or Production). This microlearning is specific to the 3rd Generation runtime.
3 +In this microlearning, we will focus on cleaning up the properties that you use in a particular environment (Test, Acceptance, or Production).
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -10,25 +10,29 @@
10 10  
11 11  == 2. Key concepts ==
12 12  
13 -This microlearning centers around cleaning up properties. Properties are an important mean to add variable values to flows that usually depend on the environment where the flow is running. Please refer to this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management||target="blank"]] for more information.
13 +This microlearning centers around cleaning up properties. Properties are an essential means to add variable values to flows that usually depend on the environment where the flow is running. Please refer to this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management||target="blank"]] for more information.
14 14  
15 15  == 3. Cleanup properties ==
16 16  
17 -Navigate to the Deploy and select the environment for which you want to verify unused properties. IN the release page you will find a wrench icon for each release. When pressing this icon you will get the possibility to chage your properties via the 'Change properties' button. A new screen will open in which the properties can be adapted. Afterwards a property release is created to actualise your changes.
17 +Navigate to the Deploy phase and select the environment in which you want to verify unused properties. You will see the "Create phase" release on the releases page. On this release, you can access the context menu (via the three dots icon). This will show the following options.
18 18  
19 -[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-properties-gen3.png]]
19 +[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-properties-gen3-context-menu.png]]
20 20  
21 -Things to consider:
21 +In this context menu, you have the option "Unused properties." Clicking this will open a pop-up showing all unused properties in that environment. With the help of the pop-up and the available options on the pop-up, you can select and subsequently delete properties.
22 22  
23 -* In case you have duplicated properties for your process container (to keep them the same across), you may experience that there are unused properties in case a flow is only present on 1 process container. Take care to review before pressing the delete button
23 +[[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-properties-gen3-unused-properties.png]]
24 24  
25 +{{info}}
26 +Once you have cleaned the properties, you still need to create a new release to effectuate the changes in the environment in question. Consequently, this will mean that each runtime for which you have removed at least **one** property will be redeployed.
27 +{{/info}}
28 +
25 25  == 4. Key takeaways ==
26 26  
27 -* Ensure to keep your properties manageable by reviewing this list after each production release, or during the peer review of a flow
31 +* Ensure to keep your properties manageable by reviewing this list after each production release or during the peer review of a flow
28 28  
29 29  == 5. Suggested Additional Readings ==
30 30  
31 -If you are interested in this topic and want more information on it please read the release notes provided by eMagiz
35 +If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz.
32 32  
33 33  
34 34  )))((({{toc/}}))){{/container}}{{/container}}