Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version
To version 255.1
edited by Carlijn Kokkeler
on 2023/11/21 12:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,81 +1,83 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
6 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **3rd generation runtime bolstering** ==
8 +{{warning}}
9 +Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 +{{/warning}}
8 8  
9 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
12 +== **Quicker Deployment Plan** ==
10 10  
11 -//__Migration of JMS backup configuration improved__//
14 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
16 +== **Next Generation Architecture Default** ==
14 14  
15 -//__Autogenerated exits can be deployed at once__//
18 +With this release, the next generation architecture will become the default. New models will use this generation as default.
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
18 18  
19 -//__Improved the performance of deploying or activating a release__//
22 +== **Cloud Template R11 Docker - Single Lane** ==
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
24 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
22 22  
23 -== **Exportable Release Audit** ~* ==
26 +== **Cloud Template R13 Docker - Double Lane** ==
24 24  
25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
28 +This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
30 +== **Feedback Items** ==
28 28  
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
32 +//__Unused properties overview__//
33 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
34 34  
35 -== **Feedback items ** ==
35 +* Not used by any runtime that is in the Create phase release.
36 +* Not required by a flow that is in the Create phase release.
37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
36 36  
37 -We have also solved other feedback items besides the flow designer's critical updates.
39 +//__Send build requests asynchronously__//
40 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
38 38  
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
42 +//__Queue explorer milliseconds__//
43 +The queue browser now displays milliseconds in the timestamps.
41 41  
42 -//__Improved naming convention on Store related pages__//
43 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
45 +//__Cancel and next buttons order__//
46 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
44 44  
45 -//__Press "Enter" to search on multiple pages__//
46 -In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
48 +//__Unused images__//
49 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
47 47  
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
51 +//__Carwash logging__//
52 +A new logging feature enabling us to make better choices in encryption standards will be released.
62 62  
54 +//__Static alerts queue consumers__//
55 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
56 +
57 +== **Bug Fixes** ==
58 +
59 +//__Flow Designer connection line__//
60 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
61 +
62 +//__Portal for migrated models__//
63 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
64 +
65 +//__Error channel inbounds__//
66 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
67 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
66 66  
67 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
72 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
71 71  
72 72  == **Key takeaways** ==
73 73  
74 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
75 75  
76 76  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  * If you have feedback or ideas for us, talk to the Platypus
78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 79  * Clear your browser cache (Ctrl + Shift + Del)
80 80  * Check out the release notes [here]
81 81  * Start thinking about how the license tracker can aid your development
... ... @@ -88,6 +88,12 @@
88 88  {{info}}
89 89  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90 90  
91 -~*~* Indicates a GEN3-only feature.
92 -{{/info}})))((({{toc/}}))){{/container}}
93 +~*~* Indicates a next-generation-architecture only feature.
94 +{{/info}}
95 +)))
96 +
97 +(((
98 +{{toc/}}
99 +)))
93 93  {{/container}}
101 +{{/container}}