Skip to Content

Changes for page Upgrading Build Numbers

Last modified by Erik Bakker on 2024/02/20 16:48
From version 15.1
edited by Eva Torken
on 2023/06/16 11:49
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/12/29 14:43
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
... ... @@ -87,8 +87,12 @@
87 87  
88 88  When you are finished with all runtimes navigate back to the Releases overview in Deploy and press the Deploy icon to activate your deployment plan. This is a great way to ensure that you did not accidentally miss one or more flows and will automatically ensure that the eMagiz alerting is activated again (assuming you make use of the best practices of eMagiz).
89 89  
90 -== 4. Key takeaways ==
90 +== 4. Assignment ==
91 91  
92 +Read up on the release notes of the build numbers and determine for the projects in which you operate what the status is of your eMagiz solution on the eMagiz platform.
93 +
94 +== 5. Key takeaways ==
95 +
92 92  * Make your life easier by keeping up to date with regards to the build numbers that eMagiz releases
93 93  * Determine the impact of the build number upgrade based on the release notes and the comparison functionality
94 94  * Communicate before executing the upgrade
... ... @@ -95,9 +95,13 @@
95 95  * Ensure that data traffic is limited (or even better halted) during the upgrade
96 96  * Verify your work by running the deployment plan
97 97  
98 -== 5. Suggested Additional Readings ==
102 +== 6. Suggested Additional Readings ==
99 99  
100 100  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
101 101  
106 +== 7. Silent demonstration video ==
107 +
108 +As this is a more theoretical microlearning we have no video for this)))
109 +
102 102  ((({{toc/}}))){{/container}}
103 103  {{/container}}