Changes for page Actualize properties

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,6 +1,10 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In this microlearning, we will focus on the situation where an existing property needs a change of its value and how to put this value into effect in your environment.
	2	+{{error}}
	3	+Note that the functionality mentioned in this microlearning will become obsolete when migrating to the new generation runtime.
	4	+{{/error}}
3	3
	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	+
4	4	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
6	6	== 1. Prerequisites ==
...	...	@@ -11,21 +11,22 @@
11	11
12	12	== 2. Key concepts ==
13	13
14		-Changing the value of any property is rather easy, yet the value is not taken into account by the flow before that flow is restarted properly due to the nature in which eMagiz is using Java.
	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.
15	15
16	16	== 3. Actualize properties ==
17	17
18		-Below are the steps to take to change the value of a property and putting that into effect.
	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.
19	19
20		-* 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||target="blank"]] for more information)
21		-* Change the value of the property and press Save
22		-* Locate the Runtime dashboard and find the flow for which the property has changed
23		-* Ensure the properly stop and start the flow
	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.
24	24
25		-**Considerations**
	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}}
26	26
27		-* 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.
	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"]].
28	28
	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	+
29	29	== 4. Key takeaways ==
30	30
31	31	* Make a good plan before you change the property so that there are no unforeseen side effects