Skip to Content

Changes for page 212 - Failover Fiesta

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,67 +2,76 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
5 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **Announcement - Release Properties** ==
8 -As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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.
9 9  
10 -== ** Deploy Architecture - Apply To Environment improvements ** ==
11 -As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
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
14 14  
15 -== ** Breadcrumb navigation in eMagiz ** ==
16 -With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel.
15 +== **Cloud Template R13 - Double Lane** ==
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
19 19  
20 20  == **Feedback Items** ==
21 21  
22 -//__Improved layout of catalog page in Design__//
23 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations.
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.
24 24  
25 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26 -As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
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.
27 27  
28 -//__Additional help texts on Design Architecture__//
29 -We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview.
29 +//__Queue explorer milliseconds__//
30 +The queue browser now displays milliseconds in the timestamps.
30 30  
31 -//__Improved Audit Trail on several places__//
32 -In several places in the portal we have improved the audit trail to better specify who changed what at which point in time.
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.
33 33  
34 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
35 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
35 +//__Unused images__//
36 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
36 36  
38 +//__Carwash logging__//
39 +A new logging feature enabling us to make better choices in encryption standards will be released.
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.
43 +
37 37  == **Bug Fixes** ==
38 38  
39 -//__Avoid clicking on other components while deleting another__//
40 -To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
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.
41 41  
42 -//__Improved validation feedback in migrating to the next-generation architecture__//
43 -We have improved several things with regards to the validation feedback when migrating to the next-generation architecture.
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.
44 44  
45 -//__Make sure that user credentials can be viewed with view rights__//
46 -This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights.
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.
47 47  
48 -//__Refresh behavior within the deployment plan is fixed__//
49 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
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.
50 50  
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
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"]]
58 58  
67 +
59 59  == **Key takeaways** ==
60 60  
61 -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:
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:
62 62  
63 63  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 67  * Check out the release notes [here]
68 68  * Start thinking about how the license tracker can aid your development
... ... @@ -75,6 +75,6 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a GEN3-only feature.
87 +~*~* Indicates a next-generation-architecture only feature.
79 79  {{/info}})))((({{toc/}}))){{/container}}
80 80  {{/container}}