Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:23
From version 14.1
edited by Erik Bakker
on 2023/09/26 12:16
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/10/28 14:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,4 @@
1 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 6  In this microlearning, we will focus on the helping you to assess the impact of upgrading to new buildnumbers.
7 7  
8 8  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
... ... @@ -40,14 +40,18 @@
40 40  
41 41  === 3.3 Functional changes ===
42 42  
43 -Before an environment is updated to the flows with the latest releases, it is adviced to first check which flows have functional changes. These flows need to be tested and put into production first so that you can isolate issues in case they occur. Once these flows are tested and live, only then move the flows with the new buildnumbers from test to production.
39 +Before an environment is updates to the flows with the latest releases, it is adviced to first check which flows have functional changes. These flows need to be tested and put into production first so that you can isolate issues in case they occur. Once these flows are tested and live, only then move the flows with the new buildnumbers from test to production.
44 44  
45 45  === 3.4 Approach ===
46 46  
47 47  It is usually best to update the test and acceptance environment first and leave that running for a certain grace period. So that in case potential issues can be fixed still.
48 48  
49 -== 4. Key takeaways ==
45 +== 4. Assignment ==
50 50  
47 +Take a look at the release notes in the eMagiz Portal to ensure you know where to look.
48 +
49 +== 5. Key takeaways ==
50 +
51 51  * Keep as close to the latest buildnumber as possible for the entire environment
52 52  * The best option is to have the entire environment run on the same buildnumber
53 53  * A mix of buildnumbers in a runtime is not a good plan - conflicting behaviors may occur.
... ... @@ -54,6 +54,10 @@
54 54  * Read the release notes for builnumbers carefully to assess the impact - in case the impact is minimal proceed with the upgrade
55 55  * Make the buildnumber upgrades planable so the release schedule takes these actions into account.
56 56  
57 -== 5. Suggested Additional Readings ==
57 +== 6. Suggested Additional Readings ==
58 58  
59 -If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz)))((({{toc/}}))){{/container}}{{/container}}
59 +If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
60 +
61 +== 7. Silent demonstration video ==
62 +
63 +There is no video available as this is more a theoretical microlearning.)))((({{toc/}}))){{/container}}{{/container}}