Changes for page Apply to environment

Last modified by Danniar Firdausy on 2024/09/17 12:39

From version 6.1
edited by Erik Bakker
on 2022/08/28 14:50
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/08/04 13:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,22 +55,21 @@
55 55  
56 56  So, in short, when you execute one (or more) actions on Deploy Architecture that have an indirect effect, you need to press Apply to Environment to actualize the changes within the eMagiz Cloud. Note that each move, whether it is direct or indirect, will cause a reaction and subsequent change within the eMagiz Cloud. So be cautious about changing things too many times over. Make sure you are especially careful when using custom folders on runtime level, as they could be deleted and recreated in cases where the machine is recreated. To safeguard yourself against this, place the folder either inside the data folder or directly on efs. Furthermore, we advise stopping the processes that have such custom folders before executing the change. This is especially relevant in the Production environment.
57 57  
58 -== 4. Assignment ==
58 +=== 3.1 Change log ===
59 59  
60 -There is no assignment for this microlearning.
60 +To inform you which changes will exactly be executed once you press "Apply to environment" we will show a pop-up listing all the **user** level changes that are pending and will be executed once the user presses "Apply changes".
61 61  
62 -== 5. Key takeaways ==
62 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
63 63  
64 -* By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
65 - * Flows return in original state
64 +== 4. Key takeaways ==
66 66  
67 -== 6. Suggested Additional Readings ==
66 +* Apply to environment actualizes all changes with an indirect effect
67 +* It gives you the option to change multiple things at once before applying the bulk change. This is to reduce downtime
68 +* It ensures that the eMagiz Cloud is only affected when a user want to affect it
68 68  
69 -There are no suggested additional readings on this topic
70 +== 5. Suggested Additional Readings ==
70 70  
71 -== 7. Silent demonstration video ==
72 +There are no suggested additional readings on this topic)))
72 72  
73 -There is no demonstration video of this functionality.)))
74 -
75 75  ((({{toc/}}))){{/container}}
76 76  {{/container}}