Changes for page Upgrading Build Numbers
Last modified by Erik Bakker on 2024/02/20 16:48
From version 11.1
edited by Erik Bakker
on 2022/06/10 13:00
on 2022/06/10 13:00
Change comment:
There is no comment for this version
To version 16.1
edited by Eva Torken
on 2023/06/16 11:50
on 2023/06/16 11:50
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.etorken - Content
-
... ... @@ -1,13 +1,14 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 +{{error}} 5 +Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime. 6 +{{/error}} 7 + 4 4 In this microlearning, we will focus on how you can upgrade your build numbers within eMagiz consistently and easily. Knowing how to upgrade your build numbers will ensure that you will keep your eMagiz solution as up to date as possible and therefore also as stable and secure as possible. 5 5 6 6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 7 7 8 -* Last update: May 14th, 2021 9 -* Required reading time: 5 minutes 10 - 11 11 == 1. Prerequisites == 12 12 13 13 * Basic knowledge of the eMagiz platform ... ... @@ -86,12 +86,8 @@ 86 86 87 87 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). 88 88 89 -== 4. Assignment ==90 +== 4. Key takeaways == 90 90 91 -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. 92 - 93 -== 5. Key takeaways == 94 - 95 95 * Make your life easier by keeping up to date with regards to the build numbers that eMagiz releases 96 96 * Determine the impact of the build number upgrade based on the release notes and the comparison functionality 97 97 * Communicate before executing the upgrade ... ... @@ -98,13 +98,8 @@ 98 98 * Ensure that data traffic is limited (or even better halted) during the upgrade 99 99 * Verify your work by running the deployment plan 100 100 101 -== 6. Suggested Additional Readings ==98 +== 5. Suggested Additional Readings == 102 102 103 103 If you are interested in this topic and want more information on it please read the help text provided by eMagiz. 104 104 105 -== 7. Silent demonstration video == 106 - 107 -As this is a more theoretical microlearning we have no video for this))) 108 - 109 -((({{toc/}}))){{/container}} 110 -{{/container}} 102 +((({{toc/}}))){{/container}}{{/container}}