Wiki source code of crashcourse-platform-deploy-actualize-properties-new
Version 10.1 by Erik Bakker on 2023/07/20 12:56
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{container}}{{container layoutStyle="columns"}}((( | ||
2 | {{error}} | ||
3 | Note that the functionality mentioned in this microlearning will become obsolete when migrating to the new generation runtime. | ||
4 | {{/error}} | ||
5 | |||
6 | In a previous microlearning we discussed how to manage your properties in an environment. In this microlearning, we will focus on applying these changes to the environment. | ||
7 | |||
8 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
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 | |||
18 | Depending on whether you only want to change a property value or whether that property change is linked to a functional flow change the approach of applying the changes to the environment changes. | ||
19 | |||
20 | == 3. Actualize properties == | ||
21 | |||
22 | === 3.1 Without a flow change === | ||
23 | Once you are satisfied with your configuration of properties you create a new release. This can be done via the "New release" button or via the wrench icon on the currently active release. Once satisfied you can activate the release. | ||
24 | |||
25 | Once the release is activated you need to navigate to the Runtime Dashboard to find the runtime(s) on which the flow(s) that use the changed property are running. For each of them you need to stop the flow and once stopped start the flow again to make sure that the new property value is actualized. | ||
26 | |||
27 | {{warning}}Starting and stopping flows can be done in direct sequence, unless you change the property of that particular flow multiple times within 2 minutes. eMagiz needs in that case 2 minutes to store the property value properly.{{/warning}} | ||
28 | |||
29 | === 3.2 With a flow change === | ||
30 | Once you are satisfied with your configuration of properties you create a new release. This can be done via the "New release" button. For more information on creating a release, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]]. | ||
31 | |||
32 | Once you have created your new release you can use the deployment plan steps to activate the changes on both flow and property level. More information on how to do this can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan||target="blank"]]. | ||
33 | |||
34 | == 4. Key takeaways == | ||
35 | |||
36 | * Make a good plan before you change the property so that there are no unforeseen side effects | ||
37 | * In case the value is changed several times, the flow will need 2 minutes of breathing time before the updated property value is taken into account. | ||
38 | |||
39 | == 5. Suggested Additional Readings == | ||
40 | |||
41 | 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. | ||
42 | )))((({{toc/}}))){{/container}}{{/container}} |