Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
Change comment: There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2022/11/21 13:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,76 +2,85 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done .....
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **Next Generation Architecture Default** ==
8 -With this release, the next generation architecture will become the default. New models will use this generation as default.
7 +== **3rd generation runtime bolstering** ==
9 9  
10 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
11 11  
12 -== **Cloud Template R11 - Single Lane** ==
13 -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
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
14 14  
15 -== **Cloud Template R13 - Double Lane** ==
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
16 16  
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
17 17  
18 -== **Feedback Items** ==
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
19 19  
20 -//__Unused properties overview__//
21 -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:
22 -* Not used by any runtime that is in the Create phase release.
23 -* Not required by a flow that is in the Create phase release.
24 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
25 25  
26 -//__Send build requests asynchronously__//
27 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
28 28  
29 -//__Queue explorer milliseconds__//
30 -The queue browser now displays milliseconds in the timestamps.
29 +== **Exportable Release Audit** ~* ==
31 31  
32 -//__Cancel and next buttons order__//
33 -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.
31 +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.
34 34  
35 -//__Unused images__//
36 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
37 37  
38 -//__Carwash logging__//
39 -A new logging feature enabling us to make better choices in encryption standards will be released.
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Changes made on definition and transformation level are **not** restored
37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 + * 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
39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40 40  
41 -//__Static alerts queue consumers__//
42 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
41 +== **Feedback items ** ==
43 43  
44 -== **Bug Fixes** ==
43 +We have also solved other feedback items besides the flow designer's critical updates.
45 45  
46 -//__Images rebuild__//
47 -We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
45 +//__Data Sink Refactor__//
46 +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 you separately.
48 48  
49 -//__Flow Designer connection line__//
50 -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.
48 +//__Improved naming convention on Store related pages__//
49 +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.
51 51  
52 -//__Portal for migrated models__//
53 -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.
51 +//__Press "Enter" to search on multiple pages__//
52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
54 54  
55 -//__Error channel inbounds__//
56 -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.
54 +* Deploy → Deployment Plan
55 +* Deploy → Properties → History
56 +* Deploy → User Management → Roles
57 +* Manage → Error Messages → Error Messages
58 +* Manage → Error Messages → Flows with Error Messages
59 +* Manage → Error Messages → Exceptions of Error Messages
60 +* Manage → Log Entries
61 +* Manage → Alerts
62 +* Manage → Triggers
63 +* Manage → Tags – Cant find (only Gen2)
64 +* Manage → Notifications
65 +* Manage → Notification Settings
66 +* Manage → Data Usage → History
67 +* Manage → Code mappings → All tabs
57 57  
58 58  == **Fancy Forum Answers** ==
59 59  
60 60  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:
61 61  
62 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
63 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
64 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
65 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
66 66  
67 -
68 68  == **Key takeaways** ==
69 69  
70 -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:
79 +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:
71 71  
72 72  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  * If you have feedback or ideas for us, talk to the Platypus
74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 75  * Clear your browser cache (Ctrl + Shift + Del)
76 76  * Check out the release notes [here]
77 77  * Start thinking about how the license tracker can aid your development
... ... @@ -84,6 +84,6 @@
84 84  {{info}}
85 85  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  
87 -~*~* Indicates a next-generation-architecture only feature.
96 +~*~* Indicates a GEN3-only feature.
88 88  {{/info}})))((({{toc/}}))){{/container}}
89 89  {{/container}}