Wiki source code of Actualize Properties
Last modified by Erik Bakker on 2023/07/20 13:08
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
8.1 | 2 | {{warning}} |
| 3 | Please note that this microlearning is for the new monitoring stack only. | ||
| 4 | {{/warning}} | ||
| 5 | |||
| |
10.1 | 6 | This microlearning will focus on how you can best actualize a property value in a specific environment. |
| |
1.1 | 7 | |
| |
2.1 | 8 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 9 | |
| 10 | == 1. Prerequisites == | ||
| 11 | |||
| 12 | * Basic knowledge of the eMagiz platform | ||
| 13 | * Understanding of property concept | ||
| 14 | * At least one flow for which you can change the actual and where that flow is active | ||
| 15 | |||
| 16 | == 2. Key concepts == | ||
| 17 | |||
| |
10.1 | 18 | Changing the value of any property is relatively easy. Yet, the flow does not consider the value before a new release is activated and deployed on your environment. |
| |
1.1 | 19 | |
| 20 | == 3. Actualize properties == | ||
| 21 | |||
| |
10.1 | 22 | Below are the steps to take to change the value of a property and put that into effect. |
| |
1.1 | 23 | |
| |
12.1 | 24 | * Locate the property via the access points for properties (see this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-gen3||target="blank"]] for more information) |
| |
7.1 | 25 | * Change the value of the property and press Save |
| |
9.1 | 26 | * Create a new release without making any functional changes |
| 27 | * Deploy the new release to the environment you desire | ||
| |
1.1 | 28 | |
| |
10.1 | 29 | {{warning}}Property changes now require a new release to be effectuated on your environment. {{/warning}} |
| |
1.1 | 30 | |
| |
13.1 | 31 | == 4. Key takeaways == |
| |
1.1 | 32 | |
| 33 | * Make a good plan before you change the property so that there are no unforeseen side effects | ||
| |
10.1 | 34 | * In case the value is changed several times before activating a release, only one new active release must be created before the updated property value is considered. |
| 35 | * If the value is changed several times, you need to start each new release before the updated property value is considered each time after activating a release. | ||
| |
1.1 | 36 | |
| |
13.1 | 37 | == 5. Suggested Additional Readings == |
| |
1.1 | 38 | |
| |
10.1 | 39 | If you are interested in this topic and want more information on it, please read the help text provided by eMagiz when executing these actions. |
| |
2.1 | 40 | )))((({{toc/}}))){{/container}}{{/container}} |